Bug#870641: light-locker: screen stays black after closing and opening laptop lid
Confirming fixed in Debian 10.5 point release: Bug is reproducible with kernel 4.19.0-9 running, not reproducible with 4.19.0-10 running. Tested via xdg-screensaver lock.
Bug#870641: light-locker: screen stays black after closing and opening laptop lid
Another weird thing: on 4.19.0-9, if I leave the screen/display off long enough, like: 1 lock the screen 2 see the display off 3 go out for lunch 4 when return, typing or moving mouse can bring the display back on. As comparison, if I leave the screen/display off not long enough, like going to take some drink, when I get back, in 4), the display won't be powered back on by typing or moving mouse. I have no idea of what happened...
Bug#870641: light-locker: screen stays black after closing and opening laptop lid
On Tue, Jul 14, 2020 at 07:38:21PM -0400, David Farrier wrote: > > On Tue, 14 Jul 2020, Aaron Lu wrote: > > > > Anyway, I downloaded this package directly from the mirror's pool: > > linux-image-4.19.0-10-amd64-unsigned_4.19.131-2_amd64.deb > > Is the above package correct? > > > > And the good news is, this kernel also works fine :-) > > > > I tried something similar, but am having mixed results. I added > "buster-proposed-updates main" to sources.list, and installed > linux-image-4.19.0-10-amd64. Which I think should be the same as Aaron Lu > retrieved, except I have the signed variant. I installed on a Panasonic > CF-19 laptop running Debian 10.4 and xfce. > > Recovering from screen blanking and locking does work with that version of > the kernel. So, on my computer, it does work better than the standard buster > kernel 4.19.0-9. However, suspend and hibernate still don't work. I haven't I never tried suspend/hibernation before but I just gave it a shot. Interestingly, the display can be powered back on after resume even with 4.19.0-9 and I can then input my password and unlock the screen. My gut feeling is that, in the case of suspend/resume, the display is powered by the gpu dirver which is i915 in my case while in the normal lock/unlock case, the display is controlled by light-locker through some mechanism and the communication between light-locker and the gpu driver broke somehow. > had a chance to try Aaron Lu's suggestion of backported kernel 5.6.0. Not a suggestion, just installed what is available in the backport repo of that time :-) > However, I have been using 5.4.0 for a while, and blanking, locking, > suspend, and hibernate all work with that version. > > Hope this information is helpful.
Bug#870641: light-locker: screen stays black after closing and opening laptop lid
On Tue, 14 Jul 2020, Aaron Lu wrote: Anyway, I downloaded this package directly from the mirror's pool: linux-image-4.19.0-10-amd64-unsigned_4.19.131-2_amd64.deb Is the above package correct? And the good news is, this kernel also works fine :-) I tried something similar, but am having mixed results. I added "buster-proposed-updates main" to sources.list, and installed linux-image-4.19.0-10-amd64. Which I think should be the same as Aaron Lu retrieved, except I have the signed variant. I installed on a Panasonic CF-19 laptop running Debian 10.4 and xfce. Recovering from screen blanking and locking does work with that version of the kernel. So, on my computer, it does work better than the standard buster kernel 4.19.0-9. However, suspend and hibernate still don't work. I haven't had a chance to try Aaron Lu's suggestion of backported kernel 5.6.0. However, I have been using 5.4.0 for a while, and blanking, locking, suspend, and hibernate all work with that version. Hope this information is helpful.
Bug#870641: light-locker: screen stays black after closing and opening laptop lid
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tue, 2020-07-14 at 10:47 +0800, Aaron Lu wrote: > On Mon, Jul 13, 2020 at 08:26:14PM +0200, Yves-Alexis Perez wrote: > > Could you try linux-image-4.19.0-10-amd64 from testing-proposed-updates > > and > > report back? It should include the fix. > > It doesn't seem easy to install packages from testing-proposed-updates. > https://wiki.debian.org/TestingProposedUpdates doesn't tell me how to do > that and after adding: > deb http://some_debian_mirror/debian/ testing-proposed-updates main > 'apt-cache search linux-image' doesn't show me linux-image-4.19.0-10-amd64.. Yeah sorry it's totally unrelated to testing-proposed-updates but it's the *stable* suite proposed-updates. > > Anyway, I downloaded this package directly from the mirror's pool: > linux-image-4.19.0-10-amd64-unsigned_4.19.131-2_amd64.deb > Is the above package correct? Yes. > > And the good news is, this kernel also works fine :-) Perfect. Thanks for testing. I think there should be a point release including that kernel in the following weeks. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAl8NZUwACgkQ3rYcyPpX RFtUjAf/XtvPxp1Zbd2i1YBkAcFsvj67uOirjOhf/h9TyqCLjjWcG5aoMc6iZXD5 uWsQU4mPlIfy6/EaBo3lka65WiIfvKGJT2zAKD0Y2Mab5OSj8ttVjXfvMlHNdVcn n8bqwYbwKMOXXIV7fYPA2qqQQg0KGIMQpYF5//KJPhLciGIk4BegyejQuSxWDHvR je0ArUty2MzSd+rNFg7uxv1h4leY/BDp8h6d3O5Zu3EqFjMTfox8YGyvBj7jCi5S IzU4iHHhkk7L6fBy0DP3VYvGPYG+Uh5MxhP2Ah4Avow1YWfpN9TcFWZZvV+QJRUW QkmXjzHZ/Pmk3wxPzy6MQqcmL5oUvQ== =lwrA -END PGP SIGNATURE-
Bug#870641: light-locker: screen stays black after closing and opening laptop lid
On Mon, Jul 13, 2020 at 08:26:14PM +0200, Yves-Alexis Perez wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Mon, 2020-07-13 at 10:33 +0800, Aaron Lu wrote: > > On Tue, May 12, 2020 at 11:13:52AM +0200, Yves-Alexis Perez wrote: > > > I've also re-pinged upstream Linux and the patch should be included in the > > > next Linux point release (hopefully 4.19.123), and which will then be > > > included > > > in Debian buster for the next Debian point release (hopefully 10.5). It's > > > not > > > tomorrow but still it should help at one point. > > > > Just want to report that I have installed 5.6.0-0.bpo.2-amd64 from > > buster-backport and now the display can be powered back on when I > > pressed my keyboard or moved my mouse. > > Could you try linux-image-4.19.0-10-amd64 from testing-proposed-updates and > report back? It should include the fix. It doesn't seem easy to install packages from testing-proposed-updates. https://wiki.debian.org/TestingProposedUpdates doesn't tell me how to do that and after adding: deb http://some_debian_mirror/debian/ testing-proposed-updates main 'apt-cache search linux-image' doesn't show me linux-image-4.19.0-10-amd64.. Anyway, I downloaded this package directly from the mirror's pool: linux-image-4.19.0-10-amd64-unsigned_4.19.131-2_amd64.deb Is the above package correct? And the good news is, this kernel also works fine :-) > > I do not see any other problems right now, everything seems to work > > fine, except one error message in dmesg everytime the display goes the > > off-on cycle: > > broken atomic modeset userspace detected, disabling atomic > > But I guess it's a different problem and it doesn't seem to cause any > > problem. > > Actually the problem lies in the way Xorg uses atomic, and that's why the fix > is to disable them. So if you see the message that means the fix is correctly > applied. I see, thanks for the explanation.
Bug#870641: light-locker: screen stays black after closing and opening laptop lid
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Mon, 2020-07-13 at 10:33 +0800, Aaron Lu wrote: > On Tue, May 12, 2020 at 11:13:52AM +0200, Yves-Alexis Perez wrote: > > I've also re-pinged upstream Linux and the patch should be included in the > > next Linux point release (hopefully 4.19.123), and which will then be > > included > > in Debian buster for the next Debian point release (hopefully 10.5). It's > > not > > tomorrow but still it should help at one point. > > Just want to report that I have installed 5.6.0-0.bpo.2-amd64 from > buster-backport and now the display can be powered back on when I > pressed my keyboard or moved my mouse. Could you try linux-image-4.19.0-10-amd64 from testing-proposed-updates and report back? It should include the fix. > I do not see any other problems right now, everything seems to work > fine, except one error message in dmesg everytime the display goes the > off-on cycle: > broken atomic modeset userspace detected, disabling atomic > But I guess it's a different problem and it doesn't seem to cause any > problem. Actually the problem lies in the way Xorg uses atomic, and that's why the fix is to disable them. So if you see the message that means the fix is correctly applied. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAl8Mp0YACgkQ3rYcyPpX RFs+kQgA6vO+abjPhh198KJPDVy/970Y7sEW1qgx7pHsrWy2/McdNWfWydSlld0x 29BKlYY/ZlwHP9AX5yLjR6gnuxHum4AncJu982w/+zlG3cB/VisSjBsCxOeM8nMW 8CsCidxq56YUiOIjA5GaKwroK6jb84SfmMva3BkURYB/teSs7URJ9nnunyWtITDv HJYKrYND99/vc1KaSOTBE6T6FK5jPaH8HPOARMSMXOinVkba/QGLdYl6YC/mtMif WD6QC6DkcLqK7z95Q33hOHIMyL418tqfoUIz+twv3FGel067EnSj6jbU4zGgXrz3 LyPx2UMh8pqBEtrvvFXWUge1I9JY2w== =j2FJ -END PGP SIGNATURE-
Bug#870641: light-locker: screen stays black after closing and opening laptop lid
On Tue, May 12, 2020 at 11:13:52AM +0200, Yves-Alexis Perez wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Mon, 2020-05-11 at 19:34 -0400, David Farrier wrote: > > I see I am coming to this thread a bit late, but for what it is worth, > > here is some additional information. > > > > But first, thanks to Udo Richter for suggesting the workaround of > > installing linux-image-5.4.0-0.bpo.2-amd64, in other words backporting the > > testing/bullseye kernel into buster. On my laptop, this fixed the > > intermittent problem restoring blanked screen. It also seems to have > > introduced a new problem where the computer occasionally does not blank > > or lock when it should, but that is far better than occasionally losing > > work-in-progress due to inability to restore the screen. > > I've also re-pinged upstream Linux and the patch should be included in the > next Linux point release (hopefully 4.19.123), and which will then be included > in Debian buster for the next Debian point release (hopefully 10.5). It's not > tomorrow but still it should help at one point. Just want to report that I have installed 5.6.0-0.bpo.2-amd64 from buster-backport and now the display can be powered back on when I pressed my keyboard or moved my mouse. I do not see any other problems right now, everything seems to work fine, except one error message in dmesg everytime the display goes the off-on cycle: broken atomic modeset userspace detected, disabling atomic But I guess it's a different problem and it doesn't seem to cause any problem.
Bug#870641: light-locker: screen stays black after closing and opening laptop lid
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Mon, 2020-05-11 at 19:34 -0400, David Farrier wrote: > I see I am coming to this thread a bit late, but for what it is worth, > here is some additional information. > > But first, thanks to Udo Richter for suggesting the workaround of > installing linux-image-5.4.0-0.bpo.2-amd64, in other words backporting the > testing/bullseye kernel into buster. On my laptop, this fixed the > intermittent problem restoring blanked screen. It also seems to have > introduced a new problem where the computer occasionally does not blank > or lock when it should, but that is far better than occasionally losing > work-in-progress due to inability to restore the screen. I've also re-pinged upstream Linux and the patch should be included in the next Linux point release (hopefully 4.19.123), and which will then be included in Debian buster for the next Debian point release (hopefully 10.5). It's not tomorrow but still it should help at one point. > > However, this does not seem to simply be a case of buster's default 4.19.0 > kernel being buggy. I say this, because I tried the backport version of > 4.19.0 in stretch. On my laptop, screen blanking and locking work just > fine in stretch, regardless whether it is the default 4.9.0 or the > backported 4.19.0 kernel. Apparently, something besides the kernel > changed between stretch and buster. Yes, it's likely the userland part also has changed. Maybe it changed from the Intel driver to the Modesetting one, or maybe the Modesetting gained (partial) support for atomics or something. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAl66aNAACgkQ3rYcyPpX RFtAJggAvRXqZoOgEKrbDKyN5VoSDnMKB/AA/cbxBiFpXXpCt/RSsn4yyWEqDmj8 Lgp2QjCJvfLrW4G9XWfmq6vNrU/JdplDMUCFE302zHQuBMEXOmSUwUSIQJ8YyOhx f2Fo0SEGV1LPIvr0dQkGZOSi1tSHBWj9/RaWwP3VKys0PxpkXKRfuoCmzUW6S8As FhVjuQDurgQYhbDHcENnHm2D+vjbbjVjJ6/Ww0PsBOVbRu0JYal5KOnIDa2wjNp3 VKxgMvTTskYuCdCiriCdH5c17GYNXmAK5JZD2el63a6mSw0Oxsx0lhlgnuzAf7/K tjJQlOLAqk/AkAnQUiITGcaasZM4Vw== =umz8 -END PGP SIGNATURE-
Bug#870641: light-locker: screen stays black after closing and opening laptop lid
I see I am coming to this thread a bit late, but for what it is worth, here is some additional information. But first, thanks to Udo Richter for suggesting the workaround of installing linux-image-5.4.0-0.bpo.2-amd64, in other words backporting the testing/bullseye kernel into buster. On my laptop, this fixed the intermittent problem restoring blanked screen. It also seems to have introduced a new problem where the computer occasionally does not blank or lock when it should, but that is far better than occasionally losing work-in-progress due to inability to restore the screen. However, this does not seem to simply be a case of buster's default 4.19.0 kernel being buggy. I say this, because I tried the backport version of 4.19.0 in stretch. On my laptop, screen blanking and locking work just fine in stretch, regardless whether it is the default 4.9.0 or the backported 4.19.0 kernel. Apparently, something besides the kernel changed between stretch and buster. Some background info: I have been testing with the xfce desktop on a Panasonic CF-19 laptop. Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06)
Bug#870641: light-locker: screen stays black after closing and opening laptop lid
On 24.03.19 19:35, Udo Richter wrote: I experience this behavior in most cases when light-locker kicks in as screen saver. Closing the lid or suspending never triggers this. i965 driver on Sandybridge CPU. Ctrl-Alt-F6-F7 brings me to a screen-is-locked display, and after some seconds, to the actual login prompt. Bug appeared after upgrading from stretch a few months ago. Some more infos after living with this bug for a year: - The bug can be instantly triggered with xdg-screensaver lock - One new workaround seems to be to use a backport kernel (atm thats linux-image-5.4.0-0.bpo.2-amd64) - The workaround with Ctrl-Alt-F7/F8 worked for me usually. - You can also blindly type your password, and the screen will be back after unlocking - Be aware, if you're too fast after screen lock, the screen might unlock without password prompt and without screen being back on. That way I corrupted a password by typing it blindly into a messenger. ^^' - If the screen is locked quite long (like >30min), screen may wake up by mouse move again. I'm now testing the backports kernel. First test looking good, I'll report if I notice anything new.
Bug#870641: light-locker: screen stays black after closing and opening laptop lid
Package: light-locker Version: 1.8.0-3 Followup-For: Bug #870641 Dear Maintainer, Another user here with the same issue, using Jeremiah Mahler's workaround fixed the problem for me as well. I can confirm I see the same thing in the xorg logs, which is fbdev is being loaded. Afer the work around the display wakes up as normal. When the screen refused to wake up I could CTRL+ALT+F1 to tty1, and kill light-locker and then CTRL+ALT+F7 to get back into my xfce session. $ lspci -v [...] 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller Flags: bus master, fast devsel, latency 0, IRQ 46 Memory at f000 (64-bit, non-prefetchable) [size=4M] Memory at e000 (64-bit, prefetchable) [size=256M] I/O ports at 3000 [size=64] [virtual] Expansion ROM at 000c [disabled] [size=128K] Capabilities: Kernel driver in use: i915 Kernel modules: i915 [...] -- System Information: Debian Release: 10.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8), LANGUAGE=en_CA:en (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 libc62.28-10 ii libcairo21.16.0-4 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 241-3 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-4 light-locker recommends no packages. light-locker suggests no packages. -- no debconf information
Bug#870641: light-locker: screen stays black after closing and opening laptop lid
One more for the mix: I experience this behavior in most cases when light-locker kicks in as screen saver. Closing the lid or suspending never triggers this. i965 driver on Sandybridge CPU. Ctrl-Alt-F6-F7 brings me to a screen-is-locked display, and after some seconds, to the actual login prompt. Bug appeared after upgrading from stretch a few months ago. Debian/Buster, light-locker 1.8.0-3. I tried using the keys to change screen brightness, no effect.
Bug#870641: light-locker: screen stays black after closing and opening laptop lid
Re: Yves-Alexis, On Tue, Oct 23, 2018 at 05:29:02PM +0200, Yves-Alexis Perez wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Tue, 2018-10-23 at 08:07 -0700, Jeremiah Mahler wrote: > > Re: Yves-Alexis, > > > > On Tue, Oct 23, 2018 at 11:01:21AM +0200, Yves-Alexis Perez wrote: > > [...] > > > On Mon, 2018-10-22 at 20:48 -0700, Jeremiah Mahler wrote: > > > > I am experiencing this problem and I found a workaround ... > > > > > > Did you try the other workarounds (vt-switch back and forth)? Was it not > > > working? > > > > > > > Alt-F1, Ctrl-Alt-Backspace, etc, don't get me to the terminal prompt. > > Maybe I'm using the wrong keys in Xfce? > > Try Ctrl-Alt-F1 then Ctrl-Alt-F8. These don't work for me either. > > > > > > If I create an Xorg config file that says to use the Intel > > > > driver it works. > > > > > > Interesting. There might be a bad interaction with the driver where it > > > doesn't > > > switch the backlight on or something. > > > > Perusing the /var/log/Xorg.0.log finds that it was using the > > > > fbdev driver before. > > > > > > Are you sure? I think Intel cards should be using the “modesetting” driver > > > by > > > default. > > > > > > > Hmm, I found references to both fbdev and modesetting modules in the > > Xorg.0.log (see attached). > > That's interesting indeed. Do you have multiple video adapters or just one? > Can you try to remove xserver-xorg-video-fbdev and see what happens? > As far as I can tell I just have one video adapter. It is just a laptop and I'm not using any external monitors. $ lspci 00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers (rev 08) 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 520 (rev 07) 00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model 00:13.0 Non-VGA unclassified device: Intel Corporation Sunrise Point-LP Integrated Sensor Hub (rev 21) 00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21) [...] If I apt-get purge xserver-xorg-video-fbdev and remove /etc/X11/xorg.conf.d/20-intel.conf the screen will lock up as before. With xserver-xorg-video-fbdev still removed, if I re-add /etc/X11/xorg.conf.d/20-intel.conf then light-locker works again. Interestingly, xserver-xorg-video-modesetting is removed on my system too. > Regards, > - -- > Yves-Alexis > -BEGIN PGP SIGNATURE- > > iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAlvPPj4ACgkQ3rYcyPpX > RFu+vwf9Fye72g4ifG+dRcnYDzMyXGCC9iz+5ovkj/Vmvm2VhB1YQX22BtqurFkx > Nw3w0N5YqKto0geRmnaVUNkQgXeT4kRmhl4RGqmvYJvyfy939RY3qBNu4H7gz0m6 > F7bUMvxcB427Tbs1+AAkTDkMRvcek554Y2qFkGsfPkF19MfCIYWi2AZofon7yNPR > iWPV9emqoIUmhsIg2xptEO3+xpU+m17pDtrf763t2nP8kg8mYbzV7vyKUgmjz1Wd > dw9scn3JR8CNpjHfrL21JQhFvaVMuKZoomw8XXd6wHuh8VFo5caLU7GoOF8SMRgg > /G30+guXUHQSMlsq7JItPO9I5CLp6A== > =nwQh > -END PGP SIGNATURE- -- - Jeremiah Mahler
Bug#870641: light-locker: screen stays black after closing and opening laptop lid
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tue, 2018-10-23 at 08:07 -0700, Jeremiah Mahler wrote: > Re: Yves-Alexis, > > On Tue, Oct 23, 2018 at 11:01:21AM +0200, Yves-Alexis Perez wrote: > [...] > > On Mon, 2018-10-22 at 20:48 -0700, Jeremiah Mahler wrote: > > > I am experiencing this problem and I found a workaround ... > > > > Did you try the other workarounds (vt-switch back and forth)? Was it not > > working? > > > > Alt-F1, Ctrl-Alt-Backspace, etc, don't get me to the terminal prompt. > Maybe I'm using the wrong keys in Xfce? Try Ctrl-Alt-F1 then Ctrl-Alt-F8. > > > > If I create an Xorg config file that says to use the Intel > > > driver it works. > > > > Interesting. There might be a bad interaction with the driver where it > > doesn't > > switch the backlight on or something. > > > Perusing the /var/log/Xorg.0.log finds that it was using the > > > fbdev driver before. > > > > Are you sure? I think Intel cards should be using the “modesetting” driver > > by > > default. > > > > Hmm, I found references to both fbdev and modesetting modules in the > Xorg.0.log (see attached). That's interesting indeed. Do you have multiple video adapters or just one? Can you try to remove xserver-xorg-video-fbdev and see what happens? Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAlvPPj4ACgkQ3rYcyPpX RFu+vwf9Fye72g4ifG+dRcnYDzMyXGCC9iz+5ovkj/Vmvm2VhB1YQX22BtqurFkx Nw3w0N5YqKto0geRmnaVUNkQgXeT4kRmhl4RGqmvYJvyfy939RY3qBNu4H7gz0m6 F7bUMvxcB427Tbs1+AAkTDkMRvcek554Y2qFkGsfPkF19MfCIYWi2AZofon7yNPR iWPV9emqoIUmhsIg2xptEO3+xpU+m17pDtrf763t2nP8kg8mYbzV7vyKUgmjz1Wd dw9scn3JR8CNpjHfrL21JQhFvaVMuKZoomw8XXd6wHuh8VFo5caLU7GoOF8SMRgg /G30+guXUHQSMlsq7JItPO9I5CLp6A== =nwQh -END PGP SIGNATURE-
Bug#870641: light-locker: screen stays black after closing and opening laptop lid
Re: Yves-Alexis, On Tue, Oct 23, 2018 at 11:01:21AM +0200, Yves-Alexis Perez wrote: [...] > > On Mon, 2018-10-22 at 20:48 -0700, Jeremiah Mahler wrote: > > I am experiencing this problem and I found a workaround ... > > Did you try the other workarounds (vt-switch back and forth)? Was it not > working? > Alt-F1, Ctrl-Alt-Backspace, etc, don't get me to the terminal prompt. Maybe I'm using the wrong keys in Xfce? > > If I create an Xorg config file that says to use the Intel > > driver it works. > > Interesting. There might be a bad interaction with the driver where it doesn't > switch the backlight on or something. > > > > Perusing the /var/log/Xorg.0.log finds that it was using the > > fbdev driver before. > > Are you sure? I think Intel cards should be using the “modesetting” driver by > default. > Hmm, I found references to both fbdev and modesetting modules in the Xorg.0.log (see attached). [ 1507.899] (==) Matched modesetting as autoconfigured driver 0 [ 1507.899] (==) Matched fbdev as autoconfigured driver 1 [ 1507.899] (==) Matched vesa as autoconfigured driver 2 [ 1507.899] (==) Assigned the driver to the xf86ConfigLayout [ 1507.899] (II) LoadModule: "modesetting" [ 1507.899] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so [ 1507.899] (II) Module modesetting: vendor="X.Org Foundation" [ 1507.899]compiled for 1.20.1, module version = 1.20.1 [ 1507.899]Module class: X.Org Video Driver [ 1507.899]ABI class: X.Org Video Driver, version 24.0 [ 1507.899] (II) LoadModule: "fbdev" [ 1507.899] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so [ 1507.900] (II) Module fbdev: vendor="X.Org Foundation" [ 1507.900]compiled for 1.20.0, module version = 0.5.0 [ 1507.900]Module class: X.Org Video Driver [ 1507.900]ABI class: X.Org Video Driver, version 24.0 > Regards, > - -- > Yves-Alexis [...] > -- - Jeremiah Mahler [ 1507.883] X.Org X Server 1.20.1 X Protocol Version 11, Revision 0 [ 1507.883] Build Operating System: Linux 4.9.0-8-amd64 x86_64 Debian [ 1507.883] Current Operating System: Linux ripley 4.18.0-2-amd64 #1 SMP Debian 4.18.10-2 (2018-10-07) x86_64 [ 1507.883] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.18.0-2-amd64 root=UUID=c72276cc-4e2e-40ef-ad28-fa7028f75d66 ro quiet [ 1507.884] Build Date: 10 October 2018 04:23:15PM [ 1507.884] xorg-server 2:1.20.1-5 (https://www.debian.org/support) [ 1507.884] Current version of pixman: 0.34.0 [ 1507.884]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 1507.884] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 1507.884] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Oct 22 20:22:16 2018 [ 1507.884] (==) Using config directory: "/etc/X11/xorg.conf.d" [ 1507.884] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 1507.884] (==) No Layout section. Using the first Screen section. [ 1507.884] (==) No screen section available. Using defaults. [ 1507.884] (**) |-->Screen "Default Screen Section" (0) [ 1507.884] (**) | |-->Monitor "" [ 1507.884] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 1507.884] (==) Automatically adding devices [ 1507.884] (==) Automatically enabling devices [ 1507.884] (==) Automatically adding GPU devices [ 1507.884] (==) Max clients allowed: 256, resource mask: 0x1f [ 1507.884] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 1507.884]Entry deleted from font path. [ 1507.884] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [ 1507.884] (==) ModulePath set to "/usr/lib/xorg/modules" [ 1507.884] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 1507.884] (II) Loader magic: 0x55fa4f6d0e20 [ 1507.884] (II) Module ABI versions: [ 1507.884]X.Org ANSI C Emulation: 0.4 [ 1507.884]X.Org Video Driver: 24.0 [ 1507.884]X.Org XInput driver : 24.1 [ 1507.884]X.Org Server Extension : 10.0 [ 1507.885] (++) using VT number 7 [ 1507.885] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration [ 1507.886] (II) xfree86: Adding drm device (/dev/dri/card0) [ 1507.898] (--) PCI:*(0@0:2:0) 8086:1916:17aa:2238 rev 7, Mem @ 0xf000/16777216, 0xe000/268435456, I/O @ 0xe000/64, BIOS @ 0x/131072 [ 1507.898] (II) LoadModule: "glx" [ 1507.898] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [
Bug#870641: light-locker: screen stays black after closing and opening laptop lid
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Mon, 2018-10-22 at 20:48 -0700, Jeremiah Mahler wrote: > I am experiencing this problem and I found a workaround ... Did you try the other workarounds (vt-switch back and forth)? Was it not working? > If I create an Xorg config file that says to use the Intel > driver it works. Interesting. There might be a bad interaction with the driver where it doesn't switch the backlight on or something. > > Perusing the /var/log/Xorg.0.log finds that it was using the > fbdev driver before. Are you sure? I think Intel cards should be using the “modesetting” driver by default. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAlvO42EACgkQ3rYcyPpX RFt66gf9FtWRRH72XNEHLEIpkcGGrTXPrJYg+6zt+YQffScwLaXGjyN3DvLiIIpP al36Q/lfekw8upfKYQfM800kcoRl9wLwcOVIZ9DhHvZjEUf8uMuPK4k8d2ocvGFW OnoIRiD2footzeuXFum1UyIrSKFfYiESAmoimA9G4CFz0cq5cRNfgEcCuLA2EBe/ IExgaqnvS1fbUKZKCExXHnGgBj1CEA/1rkhNkViLMwzak6IqIgy0KQcj4eZnZ0fE MtFA0UuKQS/UXRQWe8k7c7RjQl85tWTqhK0OBH4KAiL2htiFwWNf+zyLSySgbg7k FTPzs+NyNr4JW1cyC5XkyVtu7DKOnQ== =0Dos -END PGP SIGNATURE-
Bug#870641: light-locker: screen stays black after closing and opening laptop lid
Package: light-locker Version: 1.8.0-2 Followup-For: Bug #870641 Hi, I am experiencing this problem and I found a workaround ... If I lock the screen it goes black and won't unlock from the keyboard. If I ssh to the machine I can restart lightdm and get a login prompt. $ light-locker-command --lock (goes black, can't wakeup) If I create an Xorg config file that says to use the Intel driver it works. $ cat /etc/X11/xorg.conf.d/20-intel.conf Section "Device" Identifier"Intel Graphics" Driver"intel" EndSection Perusing the /var/log/Xorg.0.log finds that it was using the fbdev driver before. Here is the info on from my card. $ lspci -v [...] 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 520 (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake GT2 [HD Graphics 520] Flags: bus master, fast devsel, latency 0, IRQ 126 Memory at f000 (64-bit, non-prefetchable) [size=16M] Memory at e000 (64-bit, prefetchable) [size=256M] I/O ports at e000 [size=64] [virtual] Expansion ROM at 000c [disabled] [size=128K] Capabilities: [40] Vendor Specific Information: Len=0c Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 2 Capabilities: [100] Process Address Space ID (PASID) Capabilities: [200] Address Translation Service (ATS) Capabilities: [300] Page Request Interface (PRI) Kernel driver in use: i915 Kernel modules: i915 [...] If I can do anything else to help debug this issue, let me know. -- System Information: Debian Release: buster/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (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.0-1 ii libc62.27-6 ii libcairo21.16.0-1 ii libdbus-1-3 1.12.10-1 ii libdbus-glib-1-2 0.110-3 ii libglib2.0-0 2.58.1-2 ii libgtk-3-0 3.24.1-2 ii libpango-1.0-0 1.42.4-3 ii libpangocairo-1.0-0 1.42.4-3 ii libsystemd0 239-10 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
Bug#870641: light-locker: screen stays black after closing and opening laptop lid
I think I am experiencing the same issue as Thomas Maaß, though I am not convinced that it is the same behavior as the initial report. Namely, sometimes the display does not turn on when light-locker should be prompting for a password (I think I have seen this both when returning from hibernation and after a "normal" lock-screen event when the machine should still be running), though other times the display does turn on. Switching to a text terminal and returning causes the display to activate, whereupon things function as expected. I'll try to file a separate report tomorrow with reportbug unless informed otherwise. -Ben
Bug#870641: light-locker: screen stays black after closing and opening laptop lid
I have a similar Problem. But not only when hibernating. I have set up to lock when the screensaver gets activated. I have no screensaver installed, but configured a black screen. But this issue is not always. Sometimes, the unlock screen appears as it should. Sometimes i can enter my pw blind to get my desktop session again. And sometimes I have to switch to the console and back to come back to desktop. Now I installed xscreensaver with none acitvated to use this lock. Needs further testing...
Bug#870641: light-locker: screen stays black after closing and opening laptop lid
Package: light-locker Version: 1.8.0-1 Followup-For: Bug #870641 Here the same with intel igpu. After staying black, ctrl+alt+f1 and killing light-locker makes you able to go back to desktop and resume work. Regards -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.14.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (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.26.1-2 ii libc62.26-2 ii libcairo21.15.8-3 ii libdbus-1-3 1.12.2-1 ii libdbus-glib-1-2 0.108-3 ii libglib2.0-0 2.54.2-5 ii libgtk-3-0 3.22.26-2 ii libpango-1.0-0 1.40.14-1 ii libpangocairo-1.0-0 1.40.14-1 ii libsystemd0 236-2 ii libx11-6 2:1.6.4-3 ii libxext6 2:1.3.3-1+b2 ii libxss1 1:1.2.2-1+b2 ii lightdm 1.18.3-4 light-locker recommends no packages. light-locker suggests no packages. -- no debconf information
Bug#870641: [Pkg-xfce-devel] Bug#870641: light-locker: screen stays black after closing and opening laptop lid
On 3.08.17, Yves-Alexis Perez wrote: > On Thu, 2017-08-03 at 19:36 +0200, G. Milde wrote: > > I use xfce on an eeepc laptop. It's configured to hibernate (Bereitschaft) > > when the lid closes using xfce4-power-manager. > Which graphic card and driver do you use? lspci says: Intel Corporation Atom Processor D2xxx/N2xxx Integrated Grphics Controller (rev 09) the driver is xserver-xorg-video-intel After some more tests, I have to correct the "error description", though. The following holds with both screen-lockers: xscreensaver and light-locker: * hibernation via the eee "sleep-key" (Fn-F1) works: the screen is not locked. * locking the screen via the xfce action button works: the screen is unlocked via lightdm or xscreensaver dialogue. * closing/opening the lid works when setting "turn off screen" as action. * closing/opening the lid results in a black screen and locked xwindows session when setting "hibernate" as action. So it seems rather to be a problem of xfce4-power-manager or its dependencies in case there is a combination of hibernation and screen-lock. Thank you for the fast response. Günter Milde
Bug#870641: [Pkg-xfce-devel] Bug#870641: light-locker: screen stays black after closing and opening laptop lid
On Thu, 2017-08-03 at 19:36 +0200, G. Milde wrote: > I use xfce on an eeepc laptop. It's configured to hibernate (Bereitschaft) > when the lid closes using xfce4-power-manager. Which graphic card and driver do you use? Regards, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#870641: light-locker: screen stays black after closing and opening laptop lid
Package: light-locker Version: 1.7.0-3 Severity: important Dear Maintainer, I use xfce on an eeepc laptop. It's configured to hibernate (Bereitschaft) when the lid closes using xfce4-power-manager. After updating to Debian stretch, the wakeup fails, the screen stays black after opening (with some light flashing) and I cannot resume work. It is possible to switch to a console with Ctrl-Alt-F1 and kill Xorg or re-start lightdm but this requires loggin in as root and unsaved work in the session is lost. The issue dissapears when purging the light-locker package. It may be related to https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1259339 as well as the comments 60 and 65 in #805711 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805711#60 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805711#65
