X-Debbugs-Cc: 846...@bugs.debian.org Hi,
I haven't commented on this bug before, so let me first describe the symptoms I'm seeing. They are reminiscent of both #846278 and #858445. I use stretch (upgraded from jessie). I run multiple graphical sessions in separate tty's. I run 'startx' from console on each vt; I don't lightdm at all (not even on the default tty7) because of #865121 (a tty-switching bug in lightdm). Sometimes light-locker kicks in (due to inactivity, I guess?) and shows the "You'll be redirected" message, and then nothing happens. I tried blindly typing in my password, but that had no effect whatsoever. I have to pkill light-locker from another tty to continue. That relates to your last comment here: On Wed, Mar 22, 2017 at 02:53:39PM +0100, Yves-Alexis Perez wrote: > On Wed, 2017-03-22 at 13:45 +0100, Daniel Haid wrote: > > This happens when I use text console logins and use "startx" to start Xorg. > > light-locker only works with lightdm. If light-locker can't cope with being run a session launched by 'startx' on the console, then light-locker should not kick in for such sessions. I don't know whether the fix should be made in light-locker itself or in one of its callers, but _something_ needs to change to stop invoking light-locker in circumstances where it will fail to unlock. Cheers, Daniel
