Dbus timeout issue

David Zeuthen zeuthen at gmail.com
Sat Aug 6 08:34:41 PDT 2011


On Sat, Aug 6, 2011 at 6:21 AM, Jacopo De Simoi <wilderkde at gmail.com> wrote:
> After some discussion with Thiago (of {Qt,}DBus fame) he suggested that in the udisks api
> the call + reply should be substituted (or better, integrated) with a call + emit signal, since there should never be
> a call + reply if it is known that the call might take more than 1 second.

No, there is no need to make the API worse by doing this (why is it
worse? Because then you can't easily use the API from
gdbus(1)/dbus-send(1) or d-feet). And, btw, what you are asking for is
already there via the Job* properties on the Device interface.

Anyway, in this case, just set the D-Bus timeout in your call to
infinite and things will work fine. For example, if you are using
libdbus, it's the timeout_milliseconds parameter in
dbus_connection_send_with_reply(), see


If you are using some other D-Bus library than libdbus it should have
support for something similar.


More information about the devkit-devel mailing list