Unable to unlock the desktop session: systemd-logind: got pause for 13:69

[Po-Hsu Lin]

When this issue happens, you won't be able to unlock your desktop session (VT works fine).
This happened twice today for me, one is after a suspend, one is just a screen lock. Not sure what is the trigger yet.

Syndrome:
On the login screen after typing the correct password, you will see a small circle keep spinning and that's it. I need to restart my computer to get it back to normal.

In the syslog this error message looks fishy:
Aug 8 10:44:57 Leggiero gnome-shell[2118]: g_array_unref: assertion 'array' failed

This is part of the syslog fetching from a VT after a GUI unlock attempt (session 24 is the desktop login attempt):

Aug 8 10:44:42 Leggiero systemd[1]: Started Session 24 of user sam.
Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 226:0
Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) AIGLX: Resuming AIGLX clients after VT switch
Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): EDID vendor "AUO", prod id 4204
Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): Printing DDC gathered Modelines:
Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): Modeline "1366x768"x0.0 76.20 1366 1404 1426 1590 768 771 777 798 +hsync -vsync (47.9 kHz eP)
Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): Modeline "1366x768"x0.0 76.20 1366 1404 1426 1988 768 771 777 798 +hsync -vsync (38.3 kHz e)
Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:78
Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - Dell WMI hotkeys: is tagged by udev as: Keyboard
Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - Dell WMI hotkeys: device is a keyboard
Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:66
Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2 - Sleep Button: is tagged by udev as: Keyboard
Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2 - Sleep Button: device is a keyboard
Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:79
Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - Integrated_Webcam_HD: Integrate: is tagged by udev as: Keyboard
Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - Integrated_Webcam_HD: Integrate: device is a keyboard
Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:68
Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event4 - AT Translated Set 2 keyboard: is tagged by udev as: Keyboard
Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event4 - AT Translated Set 2 keyboard: device is a keyboard
Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:67
Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event3 - Power Button: is tagged by udev as: Keyboard
Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event3 - Power Button: device is a keyboard
Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:71
Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event7 - AlpsPS/2 ALPS GlidePoint: is tagged by udev as: Touchpad
Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event7 - AlpsPS/2 ALPS GlidePoint: device is a touchpad
Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:72
Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event8 - DELL Wireless hotkeys: is tagged by udev as: Keyboard
Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event8 - DELL Wireless hotkeys: device is a keyboard
Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) libinput: PixArt Microsoft USB Optical Mouse: SetProperty on 286 called but device is disabled.
Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: This driver cannot change properties on a disabled device
Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:65
Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event1 - Power Button: is tagged by udev as: Keyboard
Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event1 - Power Button: device is a keyboard
Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) libinput: PixArt Microsoft USB Optical Mouse: SetProperty on 277 called but device is disabled.
Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: This driver cannot change properties on a disabled device
Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) libinput: PixArt Microsoft USB Optical Mouse: SetProperty on 291 called but device is disabled.
Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: This driver cannot change properties on a disabled device
Aug 8 10:44:55 Leggiero gnome-shell[2118]: g_array_unref: assertion 'array' failed
Aug 8 10:44:55 Leggiero gnome-shell[2118]: g_array_unref: assertion 'array' failed
Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) libinput: PixArt Microsoft USB Optical Mouse: SetProperty on 289 called but device is disabled.
Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: This driver cannot change properties on a disabled device
Aug 8 10:44:55 Leggiero kernel: [62483.492900] rfkill: input handler disabled
Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:70
Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event6 - Video Bus: is tagged by udev as: Keyboard
Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event6 - Video Bus: device is a keyboard
Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:69
Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event5 - PixArt Microsoft USB Optical Mouse: is tagged by udev as: Mouse
Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event5 - PixArt Microsoft USB Optical Mouse: device is a pointer
Aug 8 10:44:57 Leggiero gnome-shell[2118]: g_array_unref: assertion 'array' failed
Aug 8 10:44:57 Leggiero gnome-shell[2118]: g_array_unref: assertion 'array' failed
Aug 8 10:44:58 Leggiero gdm-password]: pam_ecryptfs: pam_sm_authenticate: /home/sam is already mounted
Aug 8 10:45:02 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (**) Option "fd" "32"
Aug 8 10:45:02 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event3 - Power Button: device removed
Aug 8 10:45:02 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (**) Option "fd" "67"
Aug 8 10:45:02 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event6 - Video Bus: device removed
Aug 8 10:45:02 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (**) Option "fd" "64"
Aug 8 10:45:02 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event1 - Power Button: device removed
Aug 8 10:45:02 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (**) Option "fd" "21"
Aug 8 10:45:02 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2 - Sleep Button: device removed
Aug 8 10:45:02 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (**) Option "fd" "30"
Aug 8 10:45:02 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - Integrated_Webcam_HD: Integrate: device removed
Aug 8 10:45:02 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (**) Option "fd" "56"
Aug 8 10:45:02 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - Dell WMI hotkeys: device removed
Aug 8 10:45:02 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (**) Option "fd" "31"
Aug 8 10:45:02 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event4 - AT Translated Set 2 keyboard: device removed
Aug 8 10:45:02 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (**) Option "fd" "59"
Aug 8 10:45:02 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event7 - AlpsPS/2 ALPS GlidePoint: device removed
Aug 8 10:45:02 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (**) Option "fd" "62"
Aug 8 10:45:02 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event8 - DELL Wireless hotkeys: device removed
Aug 8 10:45:02 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (**) Option "fd" "54"
Aug 8 10:45:02 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event5 - PixArt Microsoft USB Optical Mouse: device removed
Aug 8 10:45:02 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) AIGLX: Suspending AIGLX clients for VT switch
Aug 8 10:45:02 Leggiero kernel: [62490.783696] rfkill: input handler enabled
Aug 8 10:45:02 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got pause for 226:0
Aug 8 10:45:02 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got pause for 13:78
Aug 8 10:45:02 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got pause for 13:66
Aug 8 10:45:02 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got pause for 13:79
Aug 8 10:45:02 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got pause for 13:68
Aug 8 10:45:02 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got pause for 13:67
Aug 8 10:45:02 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got pause for 13:71
Aug 8 10:45:02 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got pause for 13:72
Aug 8 10:45:02 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got pause for 13:65
Aug 8 10:45:02 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got pause for 13:70
Aug 8 10:45:02 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got pause for 13:69

The systemd-logind service seems ok (22 is the login attempt for desktop):
● systemd-logind.service - Login Service
   Loaded: loaded (/lib/systemd/system/systemd-logind.service; static; vendor preset: enabled)
   Active: active (running) since Mon 2018-08-06 10:49:11 CST; 1 day 23h ago
     Docs: man:systemd-logind.service(8)
           man:logind.conf(5)
           https://www.freedesktop.org/wiki/Software/systemd/logind
           https://www.freedesktop.org/wiki/Software/systemd/multiseat
 Main PID: 918 (systemd-logind)
   Status: "Processing requests..."
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/systemd-logind.service
           └─918 /lib/systemd/systemd-logind

 8月 06 10:49:10 Leggiero systemd-logind[918]: Watching system buttons on /dev/input/event0 (Lid Switch)
 8月 06 10:49:10 Leggiero systemd-logind[918]: Watching system buttons on /dev/input/event2 (Sleep Button)
 8月 06 10:49:11 Leggiero systemd-logind[918]: Watching system buttons on /dev/input/event4 (AT Translated Set 2 keyboard)
 8月 06 10:49:11 Leggiero systemd[1]: Started Login Service.
 8月 06 10:49:11 Leggiero systemd-logind[918]: New session c1 of user gdm.
 8月 06 10:49:29 Leggiero systemd-logind[918]: New session 2 of user sam.
 8月 06 19:39:04 Leggiero systemd-logind[918]: Delay lock is active (UID 1000/sam, PID 2118/gnome-shell) but inhibitor timeout is reached.
 8月 07 10:55:49 Leggiero systemd-logind[918]: Operation 'sleep' finished.
 8月 08 10:37:52 Leggiero systemd-logind[918]: Operation 'sleep' finished.
 8月 08 10:39:22 Leggiero systemd-logind[918]: New session 22 of user sam.

In some attempts, there will be some Permission denied error message for gsd-color:
gsd-color[1384]: failed to set screen _ICC_PROFILE: Failed to open file “/home/sam/.local/share/icc/edid-9eb5c4e022e314fd8b3c62e228523bd6.icc”: Permission denied

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gdm3 3.28.2-0ubuntu1.3
ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
Uname: Linux 4.15.0-30-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug 8 14:05:28 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-07-12 (391 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: gdm3
UpgradeStatus: Upgraded to bionic on 2018-07-23 (15 days ago)

[Daniel van Vugt (vanvugt)]

I think 13:69 is /dev/input/event5, which is your:

Aug 8 10:45:02 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event5 - PixArt Microsoft USB Optical Mouse: device removed

However I wouldn't think it's a problem with the mouse. More likely the kernel has detected a USB hub disconnect, which seemingly includes the keyboard:

Aug 8 10:45:02 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event4 - AT Translated Set 2 keyboard: device removed

Please try removing any external USB hubs/docks you are using and see if the problem persists. If it does persist then please include a full kernel log from running 'dmesg'.

[Po-Hsu Lin (cypressyew)]

Hello Daniel,

thanks for the reply, but I don't have any other USB device connected to this laptop except this Microsoft mouse (connected directly without any hub in between).

~$ xinput --list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ PixArt Microsoft USB Optical Mouse id=10 [slave pointer (2)]
⎜ ↳ AlpsPS/2 ALPS GlidePoint id=14 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
    ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
    ↳ Power Button id=6 [slave keyboard (3)]
    ↳ Video Bus id=7 [slave keyboard (3)]
    ↳ Power Button id=8 [slave keyboard (3)]
    ↳ Sleep Button id=9 [slave keyboard (3)]
    ↳ Integrated_Webcam_HD: Integrate id=11 [slave keyboard (3)]
    ↳ Dell WMI hotkeys id=12 [slave keyboard (3)]
    ↳ AT Translated Set 2 keyboard id=13 [slave keyboard (3)]
    ↳ DELL Wireless hotkeys id=15 [slave keyboard (3)]

$ lsusb
Bus 001 Device 004: ID 1bcf:2989 Sunplus Innovation Technology Inc.
Bus 001 Device 005: ID 0cf3:e005 Atheros Communications, Inc.
Bus 001 Device 002: ID 8087:8001 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 045e:00cb Microsoft Corp. Basic Optical Mouse v2.0
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

[Po-Hsu Lin (cypressyew)]

This just happened again, with the same HW config.

When this happens, I have zombie processes (was testing ssh-agent) related to gnome-session, not sure if this will be the cause.

USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
sam 1590 0.0 0.0 0 0 ? Zs 14:00 0:00 [ssh-agent] <defunct>
sam 14593 0.0 0.0 15044 968 tty3 S+ 19:06 0:00 grep --color=auto Z

systemd(1)---gdm3(1076)---gdm-session-wor(1467)---gdm-x-session(1497)---gnome-session-b(1510)---ssh-agent(1590)

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1785964

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc8

[Po-Hsu Lin (cypressyew)]

I tried to reproduce this today on 4.15 with only one successful attempt,
however I haven't figure what's the correct combination to make this fail.

Now I'm running this laptop with 4.18rc8 for daily work, will keep an eye on this issue to see if it can be reproduced.

Also I will try to find a more robust way to reproduce it in 4.15.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Diego Bersanetti (diegobersanetti)]

This bug happened to me a number of times as well, on a fresh install of Ubuntu 18.04.1 on a Clevo W230ST (Intel Haswell, nvidia Optimus); it never happened after a lock screen but only after a suspend/resume; the nvidia proprietary drivers 396 are installed but not loaded, as I am using the Intel integrated graphics; the nouveau module is blacklisted. I attach the relevant syslog.

[GrzesiekC (grzesiekc)]

Hi all,

You can add another person to the list

Ubuntu 18.04.1 + all updates + meas 18.2.3
Dell 7470 using internal Intel(R) Core(TM) i5-6300U
No Wayland.

There are many more people like us:
https://askubuntu.com/questions/1038723/slow-recovering-from-lock-screen-ubuntu-18-04
https://askubuntu.com/questions/1074235/ubuntu-18-04-hangs-after-screen-lock

This bug drives me crazy.

I can post logs, but my messages are like with other cases.

IMHO this happens only if the deivce stays locked for a longer period. I.e. 1H or suspended

[Alex Garel (alex-garel)]

I have the same bug here, and it's been quite a long time. It comes from time to time. After a while logins happens, but sometimes it's after a really long time !

I'm not sure but it seems uptime is generally high on my side.

$ uptime
 15:10:50 up 8 days, 19:07, 2 users, load average: 1,47, 1,38, 1,40

I attach apport informations and some syslog around the times it happens.

[GrzesiekC (grzesiekc)]

Hello again all,

In my #10 comment, I forgot to mention that my system it is upgraded from ubuntu 16.04.4.

As it is, on Thursday (25-10-2018), two major things happened:
1. The kernel was updated to - Linux E7470 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

2. I "rewound" my bash history file. I was looking for any workarounds, I performed during the lifespan of my 16.04.x. I found a line where I was messing with my Intel driver. To be honest, ATM I'm not sure why, but I added this file to resolve some other forgotten issue.

/usr/share/X11/xorg.conf.d/20-intel.conf

and here is the content:

Section "Device"
Driver "Intel"
Identifier "Intel"
EndSection

I deleted the file.

Why I bother you with this long post - since Thursday , I haven't had any single lock-up.
So, it looks like, one of those two helped in my case.
Finger cross it will stay this why for a bit longer.

[Alex Garel (alex-garel)]

@grzesiekc thanks for the comment, on my side I have no such specific content.

[GrzesiekC (grzesiekc)]

Well you can disregard #14, happened again.

However, I notice one more thing, which my be helpful to troubleshoot the issue. In may case, it usually happens when I switch IP networks (wireless>wireless, wireless>wire, wire>wireless, etc).

Here is an example:
I can stay the whole weekend in my home, connected to my SSID. Many locks and unlocks, suspends and resumes. The problem won't appear.
Then Monday morning, I go to my office, reconnect to another AP IP network and the the issue appears.

To support this theory. Today, for many hours, I have not had any issues. I.e. many locks and unlocks. Then I had to connect my printer over a new external wireless bridge.
At some point, in order to configure the bridge, I had to connect laptop's wire LAN port to the bridge and disconnect from my WiFi. When I finished configuring, I disconnected the bridge from the laptop and went to my printer. During that time, my computer locked itself and wasn't connected to any network (i.e. neither wired nor wireless). When I came back I was unable to unlock (i.e. after providing the password, freeze for many minutes).

[Alex Garel (alex-garel)]

@grzesiekC, on my side, I quite frequently do the same (connecting / reconnecting), I will try to pay attention, to see if it's correlated.

[Alex Garel (alex-garel)]

I got the issue, today while using sudo (to use bindfs), just after I typed my password, whole gnome got blocked (the mouse cursor moving but without changing shape and being unable to type, neither have any action on any window or program), but I could log in a new tty console. Note also that this was during an internet downtime.

I attach the syslog around this time.

[Diego Bersanetti (diegobersanetti)]

I have some new information: the bug is still happening as before, today I resumed my session and the login screen got stuck as usual; I left it there for a couple of minutes, then I unplugged and replugged the ethernet cable and, as soon as the network was up again, the session was unlocked! Maybe this can be helpful to understand the bug...

[Alex Garel (alex-garel)]

Thanks Diego for the information, I also got the feeling that the bug is linked to logind waiting for something from the network or usb (not sure).

I also wanted to add that this bug cause another annoyance : while I plug a USB storage key in, the system is blocked for a while : I can move the mouse, or change console, but I cannot click, change window, scroll, change workspace… until few minutes (duration vary).

In syslog I got the same message as for the lock screen : systemd got paused for ….

[GrzesiekC (grzesiekc)]

Thanks Diego. A similar situation here today. The whole Christmas season at home no issues at all - many suspends (lid close), with and without power supply. Coming today to the office, boom, unlock screen freeze after providing the password.

One more hint - I've got the same SSID at home and my office. But different IP networks, thus the WLAN card has to acquire an address each time coming to the office.

Again, nothing special in the logs, besides what was already mentioned above.

Cheers

[Pavlushka (pavelsayekat)]

Is all the affected one's have external graphics card and made any switch from external to integrated or from external to integrated then back or any kind of switch between external and integrated Graphics Cards?

[GrzesiekC (grzesiekc)]

Intel HD Graphics 520 - Internal

[Alex Garel (alex-garel)]

        *-display
             description: VGA compatible controller
             produit: Skylake GT2 [HD Graphics 520]
             fabriquant: Intel Corporation
             identifiant matériel: 2
             information bus: pci@0000:00:02.0
             version: 07
             bits: 64 bits
             horloge: 33MHz
             fonctionnalités: pciexpress msi pm vga_controller bus_master cap_list rom
             configuration: driver=i915 latency=0
             ressources: irq:125 mémoire:de000000-deffffff mémoire:c0000000-cfffffff portE/S:f000(ta
ille=64) mémoire:c0000-dffff

I don't have an external graphic card but I often plug / unplug my computer on an external display.

[Diego Bersanetti (diegobersanetti)]

I have integrated graphics Intel HD4600 (Haswell) and discrete Nvidia GTX750M as well, which is managed by the Nvidia binary blob (the nouveau module is blacklisted) but usually disabled. I also have an external monitor always plugged in while at home, and nothing elsewhere. Unfortunately the bug happens in every situation. I have to say, though, that the frequency has been going down, I haven't experienced it in the last ~10 days and I am not sure why, as my usage pattern (physical places, networks, monitors, etc...) is always the same.

[GrzesiekC (grzesiekc)]

Hi all,
can you cross check if you have any of these Gnome Shell plug-ins installed ?
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1813248/comments/10

I had both.
First I uninstalled gnome-shell-extension-multi-monitors, did not help.
Next, I uninstalled gnome-shell-extension-system-monitor. Many meetings, back and forth to my office, home, etc. AS it is for now, over last 3 days no issues with unlocking. Finger crossed it stays this way. ;-)

[GrzesiekC (grzesiekc)]

Also I did a lot of docking and unlocking (I've got 3 screen setup - built-in and two external monitors)

[Dmitrii Shcherbakov (dmitriis)]

Had this with nvidia graphics drivers after installing and then removing proprietary drivers downloaded from nvidia website. I could not log in at all at first boot.

If you see nvidia modules loaded, make sure that you select an xorg session on the login screen (not wayland) if you this control presented to you.

lsmod| grep nvidia
nvidia_uvm 794624 0
nvidia_drm 40960 13
nvidia_modeset 1040384 1 nvidia_drm
nvidia 17285120 653 nvidia_uvm,nvidia_modeset
ipmi_msghandler 102400 2 ipmi_devintf,nvidia
drm_kms_helper 172032 2 nvidia_drm,i915
drm 458752 13 drm_kms_helper,nvidia_drm,i915

Alternatively, just set WaylandEnable to false (and restart gdm).

cat /etc/gdm3/custom.conf
# ...
[daemon]
# Uncoment the line below to force the login screen to use Xorg
WaylandEnable=false
# ...

I also suspect that /etc/X11/xorg.conf generated by nvidia-xconfig (which I ran during driver installation from the website) was causing issues.

Steps I performed from a VT session:

1) sudo apt purge 'nvidia*'
2) reboot
3) sudo rm /etc/X11/xorg.conf
4) sudo apt install nvidia-driver-<version> nvidia-dkms-<version> nvidia-settings nvidia-prime
5) reboot

I also have 11-nvidia-prime.conf file at /usr/share/X11/xorg.conf.d which is generated by ubuntu-drivers-common:

cat /usr/share/X11/xorg.conf.d/11-nvidia-prime.conf

# DO NOT EDIT. AUTOMATICALLY GENERATED BY gpu-manager

Section "OutputClass"
    Identifier "Nvidia Prime"
    MatchDriver "nvidia-drm"
    Driver "nvidia"
    Option "AllowEmptyInitialConfiguration"
    Option "IgnoreDisplayDevices" "CRT"
    Option "PrimaryGPU" "Yes"
    ModulePath "/x86_64-linux-gnu/nvidia/xorg"
EndSection

dpkg -l | grep ubuntu-drivers-common
ii ubuntu-drivers-common 1:0.5.2.2

https://github.com/tseliot/ubuntu-drivers-common/blob/bionic/share/hybrid/gpu-manager.c#L1359-L1375

[Dmitrii Shcherbakov (dmitriis)]

nvidia-xconfig -generated xorg.conf looked like this https://paste.ubuntu.com/p/4hRVzHmbJV/

[Ufos92 (ufos92)]

Dell Precision 5520 freeze cuz of Nvidia confirmed.
`sudo apt purge 'nvidia*'` solved it. Let's see what happens after I install it again.

[Ufos92 (ufos92)]

`sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf.bckp`
`sudo apt install nvidia-driver-<version>` (check in GUI "Additional Drivers", mine is `430`)
everything works. Even the screen layout wasn't broken.

Thx to Dmitrii!

[spi (spi-gmxpro)]

Have the same issue for quite some time. Couldn't find any pattern yet. Also have the impression gdm is waiting for something. It happens for me when I am on Ethnernet as well when on wifi.

Have Dell XPS13 with Ubuntu 18.04.2, kernel 4.18.0-25-generic.

Found today dozens in syslog:

/usr/lib/gdm3/gdm-x-session[475]: (II) systemd-logind: got pause for 13:67

[spi (spi-gmxpro)]

I had the following gnome extensions installed:
GSConnect
gnome-shell-extension-multi-monitors
gnome-shell-extension-system-monitor
gnome-shell-extension-caffeine
gnome-shell-extension-disconnect-wifi
gnome-shell-extension-shortcuts
gnome-shell-extension-top-icons-plus
gnome-shell-extension-ubuntu-dock
gnome-shell-extension-weather

Removed all but gnome-shell-extension-ubuntu-dock and login process hasn't frozen yet.

Reinstalled
gnome-shell-extension-ubuntu-dock
gnome-shell-extension-top-icons-plus
gnome-shell-extension-disconnect-wifi
gsconnect
to observe login freeze.

[spi (spi-gmxpro)]

It seems it's the Gnome extension GSConnect (https://extensions.gnome.org/extension/1319/gsconnect/) in my case. Removed that and had no freezes since. Will examine further.

[spi (spi-gmxpro)]

Ok, very weird. Removing just GSConnect (**) didn't help after all. I also had to remove:
gnome-shell-extension-multi-monitors (*)
No topleft hot corner (**)

* these ones I installed from the Debian repository
** these ones are installed from https://extensions.gnome.org directly

[spi (spi-gmxpro)]

Still weird. The only Gnome extensions active are the follwoing ones from the Ubuntu repository:

gnome-shell-extension-disconnect-wifi
gnome-shell-extension-top-icons-plus
gnome-shell-extension-ubuntu-dock

I am still facing the freezing issues, but only if my Dell XPS13 notebook goes into S3 suspend for quite some time (like more than 5 minutes).

I changed that behavior to S2 instead (removed "mem_sleep_default=deep" from GRUB_CMDLINE_LINUX_DEFAULT in grub config).

Now even after more than 5 minutes of hibernation there wasn't any freezing.

Suspending into S2 is just for debugging exercises and currently not a permanent solution as S2 significantly drains the battery (see https://bugzilla.kernel.org/show_bug.cgi?id=199689).

[spi (spi-gmxpro)]

S2 instead of S3 didn't resolve the freezing too - took some time for the freezing to occur again. I stumbled across autofs and quick tests suggest with autofs turned off the freezing is gone.

Is anybody else who is facing the freezing using autofs (or systemd's automount feature)?

[spi (spi-gmxpro)]

I added a systemd unit to stop autofs before going into suspend and start autofs again after resume. I haven't had any freezes with gdm3 anymore. But there is still a difference between Ethernet and Wifi. When connected to Wifi, it takes some seconds longer to unlock the user session. It seems gdm3 is waiting for an active network sonnection.