#819329 light-locker doesn't work with gdm but doesn't report it

Package:
light-locker
Source:
light-locker
Description:
simple screen locker for lightDM display manager
Submitter:
Gert N
Date:
2021-12-10 10:03:04 UTC
Severity:
normal
Tags:
#819329#5
Date:
2016-03-26 20:04:17 UTC
From:
To:
Dear Maintainer,

I use light-locker with openbox. The computer becomes unreachable after sleep
or hibernate; the screen is frozen and the computer locked. Only a hard reboot
makes the computer available again.
Remove of light-locker solves the issue. Without light-locker is the computer
waking up well.

Regards,


Gert

#819329#10
Date:
2016-03-29 19:55:23 UTC
From:
To:
control: tag -1 -d-i moreinfo unreproducible

light-locker only shows a locked message on the current vt, and switches to a
login vt. It's quite unlikely to freeze anything, unless you have a problem
with the graphic stack for example.

There's not much we can do here without more information, so please try to
gain remote access to the system, get logs or anything.

Regards,

#819329#19
Date:
2016-04-03 20:31:29 UTC
From:
To:
On Tue, 29 Mar 2016 21:55:23 +0200 Yves-Alexis Perez <corsac@debian.org> wrote:

The option of 'the graphic stack' might be true. My laptop (Dell
Inspiron 1525) contains an Intel GM965/GL960 Integrated Graphics
Controller, that seems famous ;-)

A frequent warning at that time is shown in the attachment.

What log-file could help?

Trying to gain remote access to the system is little difficult at the
moment, sorry.

Regards,


Gert

#819329#24
Date:
2016-04-04 08:36:21 UTC
From:
To:
You might want to check /var/log/Xorg.0.log

Regards,

#819329#29
Date:
2016-04-05 16:20:31 UTC
From:
To:
On Mon, 4 Apr 2016 10:36:21 +0200 Yves-Alexis Perez <corsac@debian.org> wrote:

Attached the Xorg file from that period (when light-locker was
installed). For me there are no clues in it; do I miss something?

Regards,


Gert

#819329#34
Date:
2016-06-21 15:26:51 UTC
From:
To:
Hi Gert,

I might have the same problem. Can you switch to another terminal with ctrl +
alt + F2? If yes, try logging in with your standard user and checking if
light-locker is running. Kill it with 'killall light-locker', then switch back
to your X with ctrl + alt + F1. If that works, there's a bug in light-locker.

Yves-Alexis, current X in testing/sid run rootless, the logs are not written
to /var/log/Xorg.0.log anymore. You can find them by running 'journalctl -u
session-1.scope', if the X session is your first. Otherwise check for other
sessions via 'systemctl'.

For me, I have the exact same symptoms (unresponsive X after resume), which
was triggered by the following change in xfce-session:

xfce4-session (4.12.1-4)
- replace recommendation on xscreensaver by light-locker

I usually use xscreensaver, and this pulled in light-locker. Looking into my
xfce4 "session & startup", I can see that *both* xscreensaver and light-locker
were started at the same time. This can be seen in session-1 logs:

Jun 21 16:19:59 saito /usr/lib/gdm3/gdm-x-session[1569]: xscreensaver:
16:19:59: couldn't grab pointer!  (AlreadyGrabbed)
Jun 21 16:19:59 saito /usr/lib/gdm3/gdm-x-session[1569]: xscreensaver:
16:19:59: unable to grab keyboard or mouse!  Blanking aborted.

Running 'killall light-locker' solved the symptom for me. Attached you will
find the logs of 'light-locker --debug', from resuming to killing it. I'm no
expert with DBUS, so I'm out of depth debugging this, but it looks like the
problem is somewhere there.

Regards,
Lee

#819329#39
Date:
2016-06-21 15:41:47 UTC
From:
To:
Note that the same problem still exists even when xscreensaver is not started
with the session. I just verified that. So this is not an interaction problem,
the issue is that light-locker somehow doesn't unlock.

#819329#44
Date:
2016-06-22 20:04:34 UTC
From:
To:
Well, actually that's wrong. It *can* run rootless, but lightdm doesn't
support it, and light-locker obviously requires lightdm.

Regards,

#819329#49
Date:
2016-06-22 20:31:18 UTC
From:
To:
Ah, sorry, I (naively) assumed that all display managers run rootless by now.

On my system I have gdm3 and lightdm installed, and but gdm3 is my default
display manager. Maybe that is the issue here?

randall@saito:~$ cat /etc/X11/default-display-manager
/usr/sbin/gdm3

The package descriptions says it relies on lightdm, and there's a hard
dependency on lightdm, but maybe that's not enough.

Regards,
Lee

#819329#54
Date:
2016-06-22 20:59:46 UTC
From:
To:
As far as I can tell, only gdm3 does it.

Indeed.

Unfortunately, enforcing a *runtime* dependency on lightdm is not really
possible here, even thought it'd be nice.

Regards,

#819329#63
Date:
2021-12-10 09:53:55 UTC
From:
To:
-- 
Good day, I wrote you earlier but i couldn't get your response, I'm Maj.
CHRISSY COOK/ Us Army, please get back to me, there is some business issue
i would like to discuss with you.

#819329#68
Date:
2021-12-10 09:53:55 UTC
From:
To:
-- 
Good day, I wrote you earlier but i couldn't get your response, I'm Maj.
CHRISSY COOK/ Us Army, please get back to me, there is some business issue
i would like to discuss with you.