Hello Tomas.
What you describe/understand as "magic" about F7/F8 is simple (I don't
know if it's a but or a feature) :
1/ once you're logged with lightdm, and you have your X session, only
ONE Xorg server is running :
user@system:~$ ps a | grep Xorg
675 tty7 Ssl+ 0:37 /usr/lib/xorg/Xorg :0 -seat seat0 -auth
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
2/ after direct or undirect (suspend to RAM) session locking, there are
2 Xorg servers running :
user@system:~$ ps a | grep Xorg
675 tty7 Ssl+ 0:32 /usr/lib/xorg/Xorg :0 -seat seat0 -auth
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
2788 tty8 Ssl+ 0:00 /usr/lib/xorg/Xorg :1 -seat seat0 -auth
/var/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch
On the 1st Xorg server, your normal session, "covered" by the screen
lock announcement.
On the 2nd Xorg server, the login window.
3/ once logged again, your have again one Xorg server, with your normal
session ("uncovered" by the announcement).
user@system:~$ ps a | grep Xorg
675 tty7 Ssl+ 0:37 /usr/lib/xorg/Xorg :0 -seat seat0 -auth
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
On my own system, I'm still observing a strange behavior (with
light-locker 1.8.0-3) :
* if I close the lid, the system suspends to RAM, and when I reopen, I
get the login window, and once logged, the normal session.
* but if I ask for the Suspend-to-RAM through the Xfce logout window
(choice between logout, reboot, shutdown, S-to-RAM or S-to-Disk), then
after awakening, I can generally see briefly the logout window (over
normal session), then black screen (and it looks even that the screen is
switched off), and then I have to switch to VT8 to get the login
window... (and often I have to press Ctrl-Alt-F8 or F7 several times
before seeing anything).
Yours,
Philippe.
Following in another e-mail : some extracts of my /var/log/syslog.
Le 29/01/2019 à 09:30, Tomas Pospisek a écrit :
Package: light-locker
Version: 1.8.0-3
Followup-For: Bug #846278
After upgrading from Debian 'stretch' to 'buster' I am seeing similar
behavior as the other reporters here:
* when I close the lid, the system suspends to RAM.
* when I reopen, I get a black screen
* clicking around, moving the mouse, pressing shift, space or any key
doesn't have any effect
* then I switch to CTRL-ALT-F1, a text terminal appears
* I switch back to CTRL-ALT-F7, now the lock screen appears, with the
text "you will be redirected shortly" (in german, so I'm not sure
about the exact english wording).
* again clicking around, pressing keys, but the lock screen remains in
"you will be redirected shortly"
* then I press CTRL-ALT-F8 (yes F8!!) and I see the lightdm graphical
login screen (I suppose it's lightdm that is responsible for the
login screen)
* once logged in I can switch to CTRL-ALT-F1 to the text terminal and
back to CTRL-ALT-F7 (yes F7!!) and my normal desktop appears
* I had very spurious problems with the lock screen (say once in three
months) under Debian stretch
* however under 'buster' the problem is 100% repeatable
* I have tried with both light-locker 1.8.0-3 and 1.8.0-2
* after uninstalling light-locker, everything "just works" that is,
after resume I am presented the lightdm login screen
Some findings:
* so, for some reason, the lock screen seems to be appearing on F7 and
the desktop on F8. Once I am logged in, the desktop seems to be
magically switching over to F7.
* the lock screen is serving no purpose as far as I can see and it
actually breaks the users' system. Logging back in is not possible
without that weird workaround/hack above.
Given the above (I can't see the use for light-locker, given that
lightdm presents a login screen anyway) I suggest to drop
the package from Debian. And/or remove it from the Suggests of
xfce4-session and lxqt-session, because at least here it effectively
breaks xfce4-session and lxqt-session.
It'd be useful to know on how many "buster" systems light-locker
works vs. how many it breaks.
*t
PS: I'll add a Cc: Debian Xfce Maintainers,
LXQt Packaging Team for the
xfce4-session and lxqt-session packages later.
