Your message dated Wed, 2 Dec 2020 19:09:07 +0100
with message-id <X8fYQ0wpG/[email protected]>
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: Locking screen with light-locker crashes system to
blinking cursor
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 [email protected]
immediately.)
--
972417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972417
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: light-locker
Version: 1.7.0-3
Severity: important
Dear Maintainer,
when locking the screen using either the command 'dm-tool lock' or
'light-locker-command -l', the screen will black showing only a blinking
cursor. Switching to TTYs is not possible and only a restart will resolve the
situation. This happens for every execution of the aforementioned commands.
Also when issuing a 'light-locker-command -a', the screen will not be turned
off, instead the following error message is generated:
** Message: The screensaver failed to activate.
seat0.greeter.log:
** Message: Starting lightdm-gtk-greeter 2.0.2 (Nov 16 2016, 20:48:17)
** Message: [Configuration] Reading file:
/usr/share/lightdm/lightdm-gtk-greeter.conf.d/01_debian.conf
** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf
Activating service name='org.a11y.atspi.Registry'
Successfully activated service 'org.a11y.atspi.Registry'
** (lightdm-gtk-greeter:742): WARNING **: [PIDs] Failed to execute command:
upstart
** (lightdm-gtk-greeter:742): WARNING **: Error getting user list from
org.freedesktop.Accounts:
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.freedesktop.Accounts was not provided by any .service files
(lightdm-gtk-greeter:742): Gtk-WARNING **: Drawing a gadget with negative
dimensions. Did you forget to allocate a size? (node menubar owner
GreeterMenuBar)
(lightdm-gtk-greeter:742): Gtk-WARNING **: Drawing a gadget with negative
dimensions. Did you forget to allocate a size? (node menubar owner
GreeterMenuBar)
-- System Information:
Debian Release: 9.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-3-amd64 (SMP w/12 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en (charmap=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+b1
ii libc6 2.24-11+deb9u1
ii libcairo2 1.14.8-1
ii libdbus-1-3 1.10.18-1
ii libdbus-glib-1-2 0.108-2
ii libglib2.0-0 2.50.3-2
ii libgtk-3-0 3.22.11-1
ii libpango-1.0-0 1.40.5-1
ii libpangocairo-1.0-0 1.40.5-1
ii libsystemd0 232-25
ii libx11-6 2:1.6.4-3
ii libxext6 2:1.3.3-1+b2
ii libxss1 1:1.2.2-1
ii lightdm 1.18.3-1
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 ---
