Unity

  1. Bug #1438870
  2. Comment #3

Comment 3 for bug 1438870

Revision history for this message
Marco Trevisan (Treviño) (3v1n0) wrote :

Mh, I think we should fix the problem in unity-settings-daemon, by connecting at the com.canonical.Unity.Session.Locked signal instead.

Since in unity the screensaver != lockscreen, and we emit the org.gnome.ScreenSaver.ActiveChanged only when the screensaver is shown (and this generally happens after that the lockscreen has been configured).