Tails

#1 Updated by Tails 2013-07-18 10:39:27

• Parent task set to Feature #5684

#2 Updated by intrigeri 2013-07-19 02:49:12

• Priority changed from Normal to Elevated

#3 Updated by BitingBird 2014-06-09 10:10:47

• 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 2014-12-20 12:40:55

• 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 2014-12-20 12:41:15

• blocked by Feature #8383: Research technical possibilities to implement a password prompt for screen locking added

#6 Updated by BitingBird 2015-08-25 14:02:18

• blocks deleted (Feature #8383: Research technical possibilities to implement a password prompt for screen locking)

#7 Updated by BitingBird 2015-08-25 14:02:29

• is duplicate of Feature #8383: Research technical possibilities to implement a password prompt for screen locking added

#8 Updated by BitingBird 2015-08-25 14:03:07

• has duplicate deleted (Feature #8383: Research technical possibilities to implement a password prompt for screen locking)

#9 Updated by BitingBird 2015-08-25 14:30:07

• Target version set to 2017

Same milestone as parent ticket

#10 Updated by intrigeri 2015-08-26 01:27:58

• blocked by Feature #8383: Research technical possibilities to implement a password prompt for screen locking added

#11 Updated by intrigeri 2016-01-03 18:17:50

• 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 2016-01-03 18:20:24

• Description updated

#13 Updated by intrigeri 2016-01-03 18:20:49

• Description updated

#14 Updated by intrigeri 2016-08-27 10:48:08

• Target version deleted (2017)

#16 Updated by sajolida 2016-09-04 02:00:28

• 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).

#18 Updated by intrigeri 2016-09-09 14:47:39

• 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 2016-11-25 13:25:13

• 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 2016-11-28 17:21:27

• Feature Branch set to segfault:feature/5684-screen-locker

#21 Updated by anonym 2016-11-28 18:47:51

• 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 2016-11-28 18:51:13

• Status changed from In Progress to Resolved
• Assignee deleted (segfault)

… or let’s actually close sub-tickets when they are done.