#861329 Lightdm lockscreen error

Package:
lightdm
Source:
lightdm
Description:
simple display manager
Submitter:
Stefan Clauss
Date:
2020-11-15 17:42:03 UTC
Severity:
important
#861329#5
Date:
2017-04-27 12:52:05 UTC
From:
To:
Dear Maintainer,


    * What led up to the situation?

After locking the screen the mouse is frozen and a login isn't possible.

    * What exactly did you do (or not do) that was effective (or
      ineffective)?
I have activate the locking screen button in Xfce desktop environment.

    * What was the outcome of this action?

No action posible but a restart.

    * What outcome did you expect instead?

The lock screen should be running.

If you need more information please contact me via e-mail or debian bugs
ticket.

#861329#10
Date:
2017-06-14 18:32:28 UTC
From:
To:
I'm not sure if my issue is related or not but since there hasn't been any
updates to yet i figured i might as well start here at least.

Lock screen does one of two undesirable behaviors for me when initiated
either through the menus or a commandline.

1) session is terminated instead of locked (all applications closed). This
sometimes means having to enter my username and password twice. Sometimes i
only have to enter it once but either way all the old applications are gone.

2) session terminates and greeter window never reappears. I am left with a
black screen, and a blinking cursor going abnormally fast. The Ctrl-Alt-Fx
keys do not work and the only possible option is to hit the reset button

I'm not all that well versed on reading the logs but there are several
errors present:

lightdm user_get_uid assertion 'user != NULL' failed

Error using VT_WAITACTIVE 7 on /dev/tty0: Interruped system call
org.a11y.atspi.Registry XIO: fatal IO error 11

#861329#15
Date:
2017-06-16 21:10:10 UTC
From:
To:
I've pulled a number of additional error messages from the logs after
another occurrence of the problem. In this case i just was switching ttys
via ctrl-alt-f1 and then trying to return to the x session with
ctrl-alt-f7.

I'm not sure if switching ttys automatically tries to lock the screen or if
this is just another clue about where the problem is occurring.

another new error message in lightdm.log:

[+174391.19s] CRITICAL: session_get_login1_session_id: assertion 'session
!= NULL' failed

From journalctl i see this sequence of events around the time i am changing
ttys but i'm not sure exactly when in the process it happened. There is
nothing relevant before these lines

org.a11y.atspi.Registry[2554]: XIO:  fatal IO error 11 (Resource
temporarily unavailable) on X server ":0"
 org.a11y.atspi.Registry[2554]:       after 73123 requests (73123 known
processed) with 0 events remaining.
org.a11y.atspi.Registry[3028]: XIO:  fatal IO error 11 (Resource
temporarily unavailable) on X server ":0"
 org.a11y.atspi.Registry[3028]:       after 73135 requests (73135 known
processed) with 0 events remaining.
 polkitd(authority=local)[2196]: Unregistered Authentication Agent for
unix-session:5 (system bus name :1.51, object path
/org/gnome/PolicyKit1/AuthenticationAgent, locale en_US.utf8) (disconnected
from bus)

pam_unix(lightdm:session): session closed for user hannasm
 systemd-logind[2144]: Removed session c2.
 systemd[1]: Stopping User Manager for UID 114...
systemd[3014]: Stopping Virtual filesystem service...

etc...

It looks like during this process, Xorg restarted at least 2 times, so the
XOrg.0.log from the original session was automatically wiped out. The
XOrg.0.log.old contains timestamps starting after i hit the ctrl-alt-fX
keys. It does contain a few additional error messages.

[174414.803]
X.Org X Server 1.19.2
Release Date: 2017-03-02
[174414.803] X Protocol Version 11, Revision 0

... snip ...

[174422.283] (EE) RADEON(G0): failed to set mode: No space left on device
[174422.283] (EE)
Fatal server error:
[174422.283] (EE) EnterVT failed for gpu screen 0
[174422.283] (EE)
[174422.283] (EE)
Please consult the The X.Org Foundation support
         at http://wiki.x.org
 for help.
[174422.283] (EE) Please also check the log file at "/var/log/Xorg.0.log"
for additional information.
[174422.283] (EE)
[174422.284] (II) AIGLX: Suspending AIGLX clients for VT switch
[174422.288] (EE) Server terminated with error (1). Closing log file.

#861329#20
Date:
2017-06-17 12:15:31 UTC
From:
To:
It looks like you need to do some cleanup on your hard drive. It might be the
cause of every weird behavior you're seeing.

Regards,

#861329#25
Date:
2017-06-19 03:33:11 UTC
From:
To:
I have plenty of free disk space.. i was assuming this was referring to the
video card memory

On Sat, Jun 17, 2017 at 8:15 AM, Yves-Alexis Perez <corsac@debian.org> wrote:

#861329#30
Date:
2020-11-15 17:38:06 UTC
From:
To:
Hi,
Same issue, but this can also be reproduced by logging in after system
suspend. The login screen is not shown and a blank page is shown.
P.S.: For getting back to the session, instead of reset, switch to tty's
(alt ctrl F1) and switch back to GUI (alt ctrl F7)
the
device
be