desktop-packages team mailing list archive

[Paulius Vitkus <1388759@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

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.

** Affects: unity-settings-daemon (Ubuntu)
     Importance: Undecided
         Status: New

** Description changed:

- 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.
+ 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 noreplay flag helps to execute UnInhibit instantly from applications side but next call to Inhibit still delays.
+ 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.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1388759

Title:
  powersaving/screensaver UnInhibit method times out over DBus

Status in “unity-settings-daemon” package in Ubuntu:
  New

Bug 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 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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1388759/+subscriptions