[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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-----


Reply to: