Bug#934210: light-locker: VT corruption with Nvidia cards
Package: light-locker
Version: 1.8.0-3
Severity: important
On some machines with a Nvidia card and using the non-free driver, I
have the issue that about 25% of the time, when light-locker locks the
screen, I see a text console flickering on and off rapidly. When this
happens, there is no way to unlock the screen. Trying to switch VTs does
not work. Without remote access into the machine to stop light-locker,
the only option is to reset the machine by pressing the reset button or
by using Alt-Sysrq.
I have seen many other bug reports with light-locker issues, and on a
laptop with Intel HD620 graphics, I have the issue that after resuming
from suspend-to-RAM, the screen stays black, I have to switch to VT1 and
back to VT7, and then I get an annoying message that "your session is
locked, we will show the unlock screen in a few seconds". With all these
issues, I believe that the way light-locker works is fundamentally
flawed, and maybe should not have been the default when using lightdm +
XFCE.
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-5-amd64 (SMP w/12 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages light-locker depends on:
ii dconf-gsettings-backend [gsettings-backend] 0.30.1-2
ii libc6 2.28-10
ii libcairo2 1.16.0-4
ii libdbus-1-3 1.12.16-1
ii libdbus-glib-1-2 0.110-4
ii libglib2.0-0 2.60.6-1
ii libgtk-3-0 3.24.10-1
ii libpango-1.0-0 1.42.4-7
ii libpangocairo-1.0-0 1.42.4-7
ii libsystemd0 241-7
ii libx11-6 2:1.6.7-1
ii libxext6 2:1.3.3-1+b2
ii libxss1 1:1.2.3-1
ii lightdm 1.26.0-5
light-locker recommends no packages.
light-locker suggests no packages.
-- no debconf information
Reply to: