| 2014-11-03 10:06:05 |
Paulius Vitkus |
description |
I use Inhibit/UnInhibit methods over dbus (name: 'org.freedesktop.ScreenSaver', path: '/ScreenSaver', interface: 'org.freedesktop.ScreenSaver') to control computers power saving. In Trusty (14.04) everything works fine. In Utopic (14.10) I noticed that UnInhibit delays its replay for about 25 seconds.
Tested using python-dbus and GDBus from python-gi. When calling this method synchronously with default timeout I get an error (NoReply). This kind of behavior can brake many applications dependent on this functionality.
Increasing timeout over 25 seconds seems to help but it is a long time for application to freeze. Calling method with noreplay flag helps to execute UnInhibit instantly from applications side but next call to Inhibit still delays. |
I use Inhibit/UnInhibit methods over dbus (name: 'org.freedesktop.ScreenSaver', path: '/ScreenSaver', interface: 'org.freedesktop.ScreenSaver') to control computers power saving. In Trusty (14.04) everything works fine. In Utopic (14.10) I noticed that UnInhibit delays its reply for about 25 seconds.
Tested using python-dbus and GDBus from python-gi. When calling this method synchronously with default timeout I get an error (NoReply). This kind of behavior can brake many applications dependent on this functionality.
Increasing timeout over 25 seconds seems to help but it is a long time for application to freeze. Calling method with noreply flag helps to execute UnInhibit instantly from applications side but next call to Inhibit still delays. |
|
