Bug#922095: light-locker: requires manually switching virtual terminals to unlock
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tue, 2019-02-12 at 08:06 -0500, Dan Robinson wrote: > I was able to actually log in so I didn't realize that was an exact > duplicate. Yes sorry, this is a bit of a mess (which doesn't help user reporting bugs either). If you look at the end of #846278 there are bits about the vt-switch parts. There are other relevant bugs in lightdm/light-locker but unfortunately I didn't manage to merge everything to one single, readable bug. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAlxleOoACgkQ3rYcyPpX RFtyAQgA05ie1cJqQdy6xwBwG+YwqRjDI851kcRRXaORxcAnasY41EVvX4VmFn5z htxdjZ82Jms4Pr4WgXj6ADoDLiLxPAMwxqxX6im7h2hp4jgauBDQ7KaxetF3fCKn nQILTjeliRACxuNDGfRMrWyjHJdqaxlBnctpm8rS1mYUeQX/Q8kYuXYibzB79gXF iIOcHFucEAVsKA0iCs/NE+hK/G6tYGpgtOtzu9PZNm9xjnCRfzuOdcAntj5agwbg x0RW+xSKET6XtE4B/Epb4Dqv8IIhJ3RZWmIJ6Bw94GROoPaRaRe4j/a9eeBSylJM ZHSW3UoBrzN/bTw7QwQMEj7j+QdHqg== =JLhg -END PGP SIGNATURE-
Bug#922095: light-locker: requires manually switching virtual terminals to unlock
I was able to actually log in so I didn't realize that was an exact duplicate. I have an Optimus laptop, it happens either using just the Intel card or with Optimus enabled (but that's still the Intel card driving the display). On Tue, Feb 12, 2019, 02:06 Yves-Alexis Perez -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > control: forcemerge 846278 -1 > > On Mon, 2019-02-11 at 18:28 -0500, Dan Robinson wrote: > > Off a fresh install with no changes to the system, light-locker doesn't > > respond after locking the screen without manually switching VTs. Mouse or > > key > > input just leaves the screen blanked (and backlight off). Manually > switching > > to VT1 and back to VT7 shows the "This session is locked, you'll be > > automatically redirected to the unlock dialog in a few seconds" message. > At > > which point I can log in. > > > > But it's difficult, takes more time than I want to spend unlocking, and > may > > not be intuitive to a new user who doesn't know to switch VTs. > > Hi Dan, > > this awfully looks like #846278 and maybe other duplicates, and it's also > likely an issue in the Intel driver (which I assume you're using)? > > Unfortunately I don't have a magic solution right now. > > Regards, > - -- > Yves-Alexis > -BEGIN PGP SIGNATURE- > > iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAlxicG8ACgkQ3rYcyPpX > RFt10wf/Y+u+5yaZdUBc3f12GJRxFW0cCHBBpyNzuzriag6T716tCC42rml6exvQ > azgioTYTYjiICnucwQbiyyoBZtabQPs2jGyDYv16nk3v276TgZ3J+Wz1grliOLeQ > GFr3wEVt7Dcu1DFFXQWy0HltshjqVQznkJR7SdDUO2WnO5DtNOBrrq5svIpki23t > E9CtugobXc4pBm6XStX8E+eOxszcQw3eegc4ZqQOtnI/hgECfnMkDyixz0J7eCj0 > zJ3CWGUdTVCD0s8GStUT2dxLX3VIYZXGdKaaUoUyJ50s+oHuJ7rcx4KKT8G0oP+v > yt0pmDiHCzvRxa70BZhFF42yW89G/w== > =cl7a > -END PGP SIGNATURE- >
Bug#922095: light-locker: requires manually switching virtual terminals to unlock
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 control: forcemerge 846278 -1 On Mon, 2019-02-11 at 18:28 -0500, Dan Robinson wrote: > Off a fresh install with no changes to the system, light-locker doesn't > respond after locking the screen without manually switching VTs. Mouse or > key > input just leaves the screen blanked (and backlight off). Manually switching > to VT1 and back to VT7 shows the "This session is locked, you'll be > automatically redirected to the unlock dialog in a few seconds" message. At > which point I can log in. > > But it's difficult, takes more time than I want to spend unlocking, and may > not be intuitive to a new user who doesn't know to switch VTs. Hi Dan, this awfully looks like #846278 and maybe other duplicates, and it's also likely an issue in the Intel driver (which I assume you're using)? Unfortunately I don't have a magic solution right now. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAlxicG8ACgkQ3rYcyPpX RFt10wf/Y+u+5yaZdUBc3f12GJRxFW0cCHBBpyNzuzriag6T716tCC42rml6exvQ azgioTYTYjiICnucwQbiyyoBZtabQPs2jGyDYv16nk3v276TgZ3J+Wz1grliOLeQ GFr3wEVt7Dcu1DFFXQWy0HltshjqVQznkJR7SdDUO2WnO5DtNOBrrq5svIpki23t E9CtugobXc4pBm6XStX8E+eOxszcQw3eegc4ZqQOtnI/hgECfnMkDyixz0J7eCj0 zJ3CWGUdTVCD0s8GStUT2dxLX3VIYZXGdKaaUoUyJ50s+oHuJ7rcx4KKT8G0oP+v yt0pmDiHCzvRxa70BZhFF42yW89G/w== =cl7a -END PGP SIGNATURE-
Bug#922095: light-locker: requires manually switching virtual terminals to unlock
Package: light-locker Version: 1.8.0-3 Severity: normal Dear Maintainer, Off a fresh install with no changes to the system, light-locker doesn't respond after locking the screen without manually switching VTs. Mouse or key input just leaves the screen blanked (and backlight off). Manually switching to VT1 and back to VT7 shows the "This session is locked, you'll be automatically redirected to the unlock dialog in a few seconds" message. At which point I can log in. But it's difficult, takes more time than I want to spend unlocking, and may not be intuitive to a new user who doesn't know to switch VTs. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/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 libc62.28-6 ii libcairo21.16.0-2 ii libdbus-1-3 1.12.12-1 ii libdbus-glib-1-2 0.110-4 ii libglib2.0-0 2.58.3-1 ii libgtk-3-0 3.24.5-1 ii libpango-1.0-0 1.42.4-6 ii libpangocairo-1.0-0 1.42.4-6 ii libsystemd0 240-5 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-3 light-locker recommends no packages. light-locker suggests no packages. -- no debconf information
