I'd like to see the option to lock the session after auto-login. This makes it possible to start the system and load the default session without requiring any action from the user. But the session is stil safe because it requires a password before it can be used. KDM supports this functionality, and I'd like to use it with LightDM as well.
Just so I understand, what's the use case? Just for speed when you do get round to logging in?
Basically it's about speed, yes. My PC is a single-user system. Right now the boot process is interrupted while it's waiting for a username and password. What I have to do is wait for the OS to boot, enter my username and password, wait for the session to load (I've got a bunch of applications to auto-start so it takes a little while), then I can start using it. What I used to do with KDM was turn my PC on, leave the room to do something else while it boots, enter password and have a fully loaded session right away. The current auto-login is not really an option since it leaves an unlocked session, where everyone can read whatever happens to pop up on the screen, or even touch it.
Relevant snippit from KDM if (td->autoLock && cursource == PWSRC_AUTOLOGIN) env = setEnv(env, "DESKTOP_LOCKED", "true"); We can't really set envs from the greeter (it would go against the point of the design if we could) so the next question is how can we do it? Also I want to research how common this option is used before I start implementing all the (random cruft) that KDM had.
Work around for now: Save this to ~/.xprofile DESKTOP_LOCKED=true export DESKTOP_LOCKED xprop -root -f -set DESKTOP_LOCKED true then set LightDM to auto-login. I'm not adding it to the GUI with the current hack. I would consider doing it as a pre-session hook script, if that works.
That seems to be working, thanks :)
I added the LightDM Launchpad feature request in the URL field. As a data point: I enable this option on all my and my families machines for the same reason Geert Lamers does. Especially on older machines it is quite helpful, people can just walk away while their machine boots up, fetch a coffee and come back to a properly locked but fully started session.
Tried the workaround and the environment variable was enough for me, xprop not required.
There's one difference in behaviour: The KDM solution locked the session only on auto-login, the xprofile variant also when you log out and in again. I can live with that but its a bit awkward.
Looks like this was implemented in lightdm itself via the autologin-in-background setting, cf. http://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1162511 http://bazaar.launchpad.net/~lightdm-team/lightdm/trunk/revision/1662
We no longer use lightDM, having moved to SDDM several years ago. As such, this bug report is no longer applicable. Bugs reports for the new SDDM-based login screen should be filed to one of two places: 1. Visual/UI bugs with the login screen UI itself, or feature requests: plasmashell | Theme - Breeze 2. Bugs with the login/user switching process: https://github.com/sddm/sddm/issues