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

Bug#846278: 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.7.0-3
Severity: important

Dear Maintainer,

Light-locker cannot unlock a locked screen with lxqt. When lxqt invokes
light-locker to lock the screen, the usual "you will be redirected" message
and subsequent lightdm login screen appear. Typing in the password leads to
a successful pam authentication:

Nov 29 19:26:19 rigel lightdm: pam_sss(lightdm:auth): authentication success; logname= uid=0 euid=0 tty=:1 ruser= rhost= user=juhaj

but that's the last bit which works as expected.

Next, I get a black screen, which is soon replaced by text-mode black screen
with a blinking text-mode cursor at the top left corner. The actual X session
is never recovered.

It can be recovered, though, by logging into a free virtual terminal and using

loginctl unlock-session 2

where 2 happens to be the session number I have been given.

Cheers,
Juha

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.8.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages light-locker depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-2
ii  libc6                                        2.24-5
ii  libcairo2                                    1.14.6-1.1
ii  libdbus-1-3                                  1.10.12-1
ii  libdbus-glib-1-2                             0.108-1
ii  libglib2.0-0                                 2.50.2-1
ii  libgtk-3-0                                   3.22.3-2
ii  libpango-1.0-0                               1.40.3-3
ii  libpangocairo-1.0-0                          1.40.3-3
ii  libsystemd0                                  232-3
ii  libx11-6                                     2:1.6.3-1
ii  libxext6                                     2:1.3.3-1
ii  libxss1                                      1:1.2.2-1
ii  lightdm                                      1.18.2-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: