Feature #5684: Screen locker
Document screen locker
It's now possible to lock the screen in Tails 2.0 from the keyboard shortcut Super+L. But not yet from the system menu, see #5878.
We should document this. The first step would be to draft a plan. From the top of my head:
- Where would this go?
- Shall we document the limitation (no UI)?
- Is there any other way to lock the screen than the keyboard shortcut?
- Do we want to mention the security limitations of screen locking?
team: sajolida, spriver
#5 Updated by intrigeri almost 4 years ago
Good. Super-L is working. But what it's not doing is actually locking the screen. It just goes into a full screen window that I can just scroll out of the way. How do you actually lock the screen?
You need to set an administration password in the Greeter.
Sorry for the n00b sounding questions.
This is exactly why we have a ticket titled "Document screen locking in Tails Jessie"..
#13 Updated by sajolida over 3 years ago
Thanks for the offer. This didn't go in 2.6 and will have to wait until 2.8 (2016-12-13) so we have plenty of time :)
If you want to work on this, I recommend:
- Get an ISO image that has this feature implemented. Maybe from http://nightly.tails.boum.org/build_Tails_ISO_feature-5684-screen-locker/lastSuccessful/archive/.
- Test all of its aspects and take notes (and screenshots) about:
- The interactions involved.
- If other things have changed as a consequence of this feature.
- Come up with a list of everything that needs to be said or explained about this feature.
- See where all this could fit in our documentation.
- Share this draft plan with us.
Then I'll be happy to review it and once we agree on a plan, you can start writing the actual stuff. The preparatory work is the most important part and also the easy, technically speaking, because it doesn't involve learning ikiwiki, building the website, dealing with Git, etc.
I like this article which talks about a similar process: http://idratherbewriting.com/2015/01/29/writing-is-like-sorting-laundry-practical-advice-for-tackling-documentation-projects/.
#16 Updated by sajolida about 3 years ago
sajolida, do you think it would still be an improvement to
potentially ship the screen locker without user documentation?
Yes. Undocumented improvements are still improvements. The problem
rather lies on whether we are fine with building up a technical writing
debts by adding undocumented features (though we haven't been that bad
in the past about slight delays).
I'm mostly asking because I'm wondering if I should block the merge on
If I understand correctly, the screen locker is planned to be in 2.10
(freeze beginning of January), so we still have plenty of time to
document this. Last time I tried (for 2.6) it ended up being unclear to
me whether the feature was 100% ready and I think I waisted some time on
testing and trying to understand something that wasn't.
So please tell me when it's 100% ready, where I can test it, and I'll be
happy to document it in the for 2.10.
#25 Updated by anonym about 2 years ago
- Assignee changed from spriver to sajolida
- Target version changed from 2017 to Tails_3.6
It seems we'll have the screen locker feature in the next major release, Tails 3.6 on 2018-03-13, so the user docs must be ready for translation by the time bertagaz prepares the RC. There's no date set for that yet, but we know it will be ~two weeks before that, so let's say 2018-03-01 (or possibly a few days before that).
Per a private discussion, spriver will try to write the docs until 2018-02-01 and then a backup takes over if needed (with a full month to go). sajolida, can that backup be you? Otherwise, can you find one?
#27 Updated by anonym almost 2 years ago
In other words, these docs should go into Tails 3.6~rc1 (i.e. merge before 2018-03-01 noon CET). Does this sound possible?
If not, IMHO, the code can be merged without the docs. This feature is pretty self-explanatory and harmless, so the lack of docs does not feel like a strict blocker.
#29 Updated by bertagaz almost 2 years ago
I want to wait until the code is "Fix committed" before writing the documentation. Right now it's still "Ready for QA". Otherwise, yes, I plan to do that before RC1.
It is now. Is it too late to start documenting this feature? OTOH it's quite intuitive:
- if people have not set an administrator password, there's only a new icon in the main menu (with the shutdown, reboot, settings, bla ones).
- if they click on that icon, they are asked for an unlocking password, and can refuse (yeah!)
- if they have set an admin password, they'll get their screen locked automatically after some inactivity, and if so will just have to type this password.
#31 Updated by sajolida almost 2 years ago
- Tracker changed from Bug to Feature
- Status changed from In Progress to Confirmed
- Assignee changed from sajolida to cbrownstein
- QA Check set to Ready for QA
- Feature Branch set to doc/10970-screen-locker
Cody: Do you want to have a look? This is an upcoming feature from 3.6 so the work is based on the
My screenshot takes into account that #15369 will be merged as such. If it's not I'll make another one :)
#36 Updated by cbrownstein almost 2 years ago
My branch is based on testing.
#37 Updated by sajolida almost 2 years ago
- Assignee changed from sajolida to bertagaz
- QA Check changed from Dev Needed to Ready for QA