[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



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.


Reply to: