I think I have a handle on what is occurring here. 1. The idle timeout occurs (in X?) and is detected by GNOME Session. This causes the "status" on org.gnome.SessionManager /org/gnome/SessionManager/Presence to change from 0 (active) to 3 (idle). 2. This is detected in GNOME Screensaver and triggers the screensaver to activate 3. GNOME Screensaver fades out the screen and shows a lock dialog 4. GNOME ScreenSaver exports it is active on D-Bus and emits ActiveChanged 5. GNOME Settings Daemon (power module) picks this up and does the screen blank.
I *think* what is happening is because we intercept step 3 to show GNOME screensaver showing if we are using the Unity lock screen then the ActiveChanged signal is not being generated and picked up by GNOME Settings Daemon. Notes: You can set the idle timeout to 1s for testing with the following command: $ gsettings set org.gnome.desktop.session idle-delay 1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1292041 Title: Lockscreen doesn't turn off the screen Status in OEM Priority Project: New Status in OEM Priority Project trusty series: New Status in “gnome-screensaver” package in Ubuntu: Confirmed Bug description: The new Unity lock screen doesn't turn off the monitor screen. I can wait as long as 10 minutes after activating the lock screen and the monitor still doesn't trun off. Then when I unlock the screen and don't use mouse or keyboard monitor will turn off (it's about 5 seconds after unlocking). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1292041/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
