Lockdown only works after restarting indicator-session
Bug #520979 reported by
Cody Russell
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Session Menu |
Triaged
|
Low
|
Unassigned | ||
indicator-session (Ubuntu) |
Triaged
|
Low
|
Unassigned |
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:/
Changed in indicator-session (Ubuntu): | |
importance: | Undecided → Low |
status: | New → Triaged |
Changed in indicator-session: | |
status: | New → Triaged |
importance: | Undecided → Low |
To post a comment you must log in.
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.