Re: trunk r116499: Improve dbus error handling; detect bus failure

[Michael Albinus]

Michael Albinus <address@hidden> writes:

> --8<---------------cut here---------------start------------->8---
> Debugger entered--Lisp error: (dbus-error "call timed out")
>   signal(dbus-error ("call timed out"))
>   byte-code(...)
>   dbus-list-names(:session)
>   dbus-register-method(:session "a.b" "/a/b" "a.b" "c" ignore)
>   eval((dbus-register-method :session "a.b" "/a/b" "a.b" "c" (quote ignore)) 
> nil)
>   eval-last-sexp-1(nil)
>   eval-last-sexp(nil)
>   call-interactively(eval-last-sexp nil nil)
>   command-execute(eval-last-sexp)
> --8<---------------cut here---------------end--------------->8---
>
> *Messages* contains the traces.

PS: The *Messages* buffer shows, that the result for dbus-list-names(:session)
has arrived. Maybe your new mechanism has kicked off the result from
`dbus-return-values-table', or it could not be read due to the changed layout.

Best regards, Michael.