Lock screen
- Vous devez vous identifier ou créer un compte pour écrire des commentaires
I am a translator!
On Aramo, my screen is locked after some inactivity. Sometimes (it just happened, I already saw that but can't remember when), after typing my password to unlock, instead of my session, I have a locker and a message "This session is locked" and under that "You will be redirected automatically to the unlock windo in a few seconds" and then nothing happens (I translate from French, wording might not be that in English). I switched to a terminal and logged in, then "ps -ef |grep lock", there is a light-locker process, killing that process solves the problem.
Any idea why this is happening?
Not really, but maybe GDM (the package, named "gdm3", is in Trisquel's repository) would not suffer from that problem.
Neithter gdm nor light-locker is installed on my Aramo system.
The MATE screen saver and locker mate-screensaver is installed by default, I never had that problem.
I am a translator!
light-locker is marked installed automatically on my system.
$ aptitude why light-locker i lxde Depends lxde-core i A lxde-core Depends lxde-session i A openbox-lxde-session Provides lxde-session i A openbox-lxde-session Depends lxsession i A lxsession Depends lxsession-logout i A lxsession-logout Depends lxlock | xdg-utils i A lxlock Depends light-locker | xscreensaver | gnome-screensaver | i3lock | suckless-tools | slim $
I use MATE and fvwm (not openbox), I don't start lxsession-logout. If lightdm does something with light-locker no matter the type of session, this is not so good, but I really see that happening infrequently so maybe it is more a bug than a wrong design.
Was that done on top of a Trisquel Mini install?
lxsession and lxlock are possibly conflicting. I would try uninstalling whatever I am not using, and run autoremove.
- Vous devez vous identifier ou créer un compte pour écrire des commentaires