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).
** Also affects: unity-settings-daemon (Ubuntu)
Importance: Undecided
Status: New
** Changed in: unity-settings-daemon (Ubuntu)
Status: New => Triaged
** Changed in: unity-settings-daemon (Ubuntu Trusty)
Status: New => Triaged
** Changed in: unity-settings-daemon (Ubuntu Utopic)
Status: New => Triaged
** Changed in: unity-settings-daemon (Ubuntu Vivid)
Status: New => Triaged
** Changed in: unity (Ubuntu Trusty)
Status: New => Won't Fix
** Changed in: unity (Ubuntu Utopic)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1438870
Title:
Lock screen doesn't emit ActiveChanged signal
To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1438870/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
