intrigeri: > sajolida wrote (07 Dec 2015 18:22:46 GMT) : >> - gnome-screensaver is already installed by default. I'm not sure >> that's expected, so intrigeri should probably have a look. > > The gnome-session-flashback package (needed by our Greeter), depends > on gnome-screensaver. > >> - There's no need to run Benjamin's dconf command to be able to lock >> the screen with Win+L. > > Cool. > > Note, however, that it has nothing to do with gnome-screensaver: GNOME > Shell handles screen locking itself. So, in what follows, I'll > implicitly replace "gnome-screensaver" with "GNOME Shell's screen > locking functionality", which is what you meant I guess :)
Probably :) >> Is it safe to lock the screen this way in Tails? > > Given my results on #9408, it seems that it is. Before assessing this > I'd like to go through #5684, its subtasks and blueprint to make sure > we didn't forget anything, though. I guess it's on my plate as > a side-effect of porting to Jessie ⇒ I'll do it and report back here. I'll have a look as well since I'm the one who volunteered for the "screen locker" on our roadmap for 2017. From the subtasks I think: - #5878 "Add a lock screen action to the shutdown button" should be closed as we don't have the shutdown button anymore in Jessie. - #6017: "Ensure that the emergency shutdown works while the screen is locked". I tested that and it works on Tails Jessie. Do we need anything else? Automated tests? From the blueprint: - The "How to activate it?" section should be updated to Jessie. - Automatically after X minutes of idle: This is not the case in Tails Jessie. The screen is only blanked. Shall we discuss this further? - When closing the lid: This doesn't work. Shall I create a ticket? - The "Which password to use?" is still relevant and I propose to create a ticket for that under #5684, unless you prefer creating another ticket for "Screen locking without administration password" as this might take more time to get implemented. Shall I also create a ticket to write automated tests for all this? > And then it would be awesome if someone reintroduced the code we > removed in #8316 (display a Lock Screen button in the Shell's > top-right menu), after making it conditional to having an admin > password set. Shall I create a ticket for that too? >> My second question: > >> If gnome-screensaver remains in Tails Jessie, do we want to document >> this (with all the due warnings for people without an administration >> password) or do we think it will encourage people to set up an >> administration password when they don't need to and we don't want to do >> that? > > I think it would be great to document it, but not a blocker for 2.0 as > long as the only UI is a keyboard shortcut. Agreed. >> And the third one: > >> If gnome-screensaver remains in Tails Jessie, are we OK with the current >> UX for people with no password (blanking the screen but not locking it)? > > I'd rather disable it but I can live with it. See earlier discussion > on this topic: https://labs.riseup.net/code/issues/10403#note-3 Meta: it's often hard for me to extract information from tickets like these and be sure that I sorted out correctly the relevant information from all the rest that I don't understand. I understand from this one that the automatic screen blanking (and not locking) is activated in Tails Jessie by default. This conflicts with the current blueprint goals "activate automatically after X minutes of idle". _______________________________________________ Tails-dev mailing list [email protected] https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to [email protected].
