i think this would be by design, you shouldn't be opening a connection to dbus without a timeout, and you shouldn't be waiting for a reply without timeout. how does dbus scripts handle this? if it doesn't take a parameter, you will need to use dbus directly for any unreliable work.