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

Bug#922095: marked as done (light-locker, lightdm: screen stays off after resume)

Your message dated Wed, 2 Dec 2020 19:09:07 +0100
with message-id <X8fYQ0wpG/6eY9tb@pivert.maison>
and subject line Re: Bug#972417: xfce4-power-manager: System left idle => 'display power management' auto-locks session => no X session or lightdm greeter
has caused the Debian Bug report #972417,
regarding light-locker, lightdm: screen stays off after resume
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
972417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972417
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
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  libc6                                        2.28-6
ii  libcairo2                                    1.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

--- End Message ---
--- Begin Message --- 
Dear Yves-Alexis,

Thanks for your reply.

I am happy to announce that this bug #972417 disappeared, even if I don't know what solved it.
Bug occurred until Nov 4th 2020, at least.
Bug did not occur from (at least) Nov 21st 2020, and did not reoccur until today.
Thus I'll close this bug report.

For the record let me answer your points:

> The lightdm greeter is on tty8, so try with Ctrl-Alt-F8.
When bug occurred, tty8 remained black.

> With all those bugs already opened and the mess we're already in, why opening
> *yet another one*? Honestly it adds more confusion than anything at that
> point.
Because this bug report was filled against xfce4-power-manager, due to reasons explained in '[ Guilty package ]'.
Other reports that I listed were all filled against other packages. None against xfce4-power-manager yet.
Sorry that it got felt as 'confusing', that was not intended.

> As indicated in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870641#218
> the bug *should* be fixed in 10.5 with kernel 4.19.0-10. You indicated that
> you tested with linux-image-4.19.0-11-amd64-unsigned     4.19.146-1
> 
> Can you retry with that kernel and check you have the “atomic” message in the
> kernel log:
> 
> broken atomic modeset userspace detected, disabling atomic

I tested when bug still occurred. Results:

1) with current stable kernel: linux-image-4.19.0-12-amd64   4.19.152-1
- Bug still occurred
- I could not find "broken atomic modeset userspace detected, disabling atomic" in kernel log, ie nothing found by
  - grep -ri "broken atomic" /var/log
  - dmesg | grep -i "broken atomic"

2) with old old stable kernel: linux-image-4.19.0-10-amd64   4.19.132-1
- Bug still occurred
- I could not find "broken atomic modeset userspace detected, disabling atomic" in kernel log, ie nothing found by
  - grep -ri "broken atomic" /var/log
  - dmesg | grep -i "broken atomic"

Regards,
Franck

--- End Message ---
Reply to: