This appears to still be the case, four years later. :/ Since indicator-session's using org.gnome.SessionManager, we should probably support this by listening to its InhibitedActions property; that would also simplify some of our other code.
-- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/520979 Title: Lockdown only works after restarting indicator-session Status in The Session Menu: Triaged Status in “indicator-session” package in Ubuntu: Triaged Bug description: Binary package hint: indicator-session After adding support for lockdown [1], the user still needs to logout/login before it becomes active. It should happen instantly. [1]. https://bugs.launchpad.net/ubuntu/+source/indicator- session/+bug/504360 To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/520979/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
