Feature #5878
Add a lock screen action to the system menu
100%
Description
Was implemented in feature/jessie, and then reverted in 4d2a7b565410d007c4713936a6904494fb991cab since we decided at the December 2014 meeting that the bigger problem was more complicated (Feature #8383).
Subtasks
Feature #11256: Replace "Debian Live user" with a more descriptive full user name | Resolved | 100 |
Related issues
Blocked by Tails - |
Resolved | 2014-12-03 |
History
#1 Updated by Tails about 12 years ago
- Parent task set to
Feature #5684
#2 Updated by intrigeri about 12 years ago
- Priority changed from Normal to Elevated
#3 Updated by BitingBird about 11 years ago
- Subject changed from add a lock screen action to the shutdown button to Add a lock screen action to the shutdown button
- Starter set to No
#4 Updated by intrigeri about 10 years ago
- Status changed from Confirmed to In Progress
- % Done changed from 0 to 50
Was implemented in feature/jessie, and then reverted in commit:4d2a7b565410d007c4713936a6904494fb991cab since the bigger problem is more complicated (Feature #8383).
#5 Updated by intrigeri about 10 years ago
- blocked by
Feature #8383: Research technical possibilities to implement a password prompt for screen locking added
#6 Updated by BitingBird about 10 years ago
- blocks deleted (
)Feature #8383: Research technical possibilities to implement a password prompt for screen locking
#7 Updated by BitingBird about 10 years ago
- is duplicate of
Feature #8383: Research technical possibilities to implement a password prompt for screen locking added
#8 Updated by BitingBird about 10 years ago
- has duplicate deleted (
)Feature #8383: Research technical possibilities to implement a password prompt for screen locking
#9 Updated by BitingBird about 10 years ago
- Target version set to 2017
Same milestone as parent ticket
#10 Updated by intrigeri about 10 years ago
- blocked by
Feature #8383: Research technical possibilities to implement a password prompt for screen locking added
#11 Updated by intrigeri about 9 years ago
- Subject changed from Add a lock screen action to the shutdown button to Add a lock screen action to the system menu
(In GNOME Shell our interface to shutdown and reboot is in the “system menu”, on the top-right of the screen; that’s where the button to lock the screen lives in a normal GNOME Shell, so presumably it’s also where our own locking button should live.)
#12 Updated by intrigeri about 9 years ago
- Description updated
#13 Updated by intrigeri about 9 years ago
- Description updated
#14 Updated by intrigeri about 9 years ago
- Target version deleted (
2017)
#15 Updated by segfault about 9 years ago
This was handled and reviewed on the parent ticket, Feature #5684, see https://labs.riseup.net/code/issues/5684#note-50 and following.
#16 Updated by sajolida about 9 years ago
- Assignee set to anonym
- Target version set to Tails_2.6
- QA Check set to Ready for QA
anonym: I’m sorry to bring up this issue once more but I don’t see the screen locker in the system menu in 2.6~rc1 nor mentioned in the Changelog. So I understand that this won’t be in 2.6. It’s probably because the ticket was not marked for 2.6.
If my understanding is correct we should move this ticket to 2.8 as well as Feature #11256, Feature #6017, Feature #10970 (or only the parent ticket but I still want Feature #10970 to be marked explicity to see it better myself).
#17 Updated by sajolida about 9 years ago
Marking this for 2.6 until the status of the whole feature is clarified, see Feature #5878#note-16.
#18 Updated by intrigeri about 9 years ago
- Target version changed from Tails_2.6 to Tails_2.9.1
(See Feature #5684#note-54 and Feature #5684#note-55.)
#19 Updated by anonym about 8 years ago
- Target version changed from Tails_2.9.1 to Tails 2.10
Bumping this feature to the new next major release (given 2.8 was cancelled).
#20 Updated by anonym about 8 years ago
- Feature Branch set to segfault:feature/5684-screen-locker
#21 Updated by anonym about 8 years ago
- Assignee changed from anonym to segfault
- QA Check deleted (
Ready for QA)
Let’s use the parent ticket for the review process.
#22 Updated by anonym about 8 years ago
- Status changed from In Progress to Resolved
- Assignee deleted (
segfault)
… or let’s actually close sub-tickets when they are done.