Hi! This is just a simple report of an issue I have encountered yesterday.
My system was suspending (s2ram) fine since the last update I did on 18 May. However, yesterday, I started experiencing the following issue: when trying to resume my laptop (Thinkpad T14 G1), the system went into an almost fully unresponsive state. I couldn’t type anything to unlock my LightDM session. I was able switch to a terminal, but after typing my username and password, nothing happened, fully unresponsive/stuck. This is the most relevant error message from the logs: “Cannot stop frozen unit User Manager for UID 968.”
Here’s the log in reverse order:
May 24 19:56:04 tpad1.home.arpa systemd-logind[1119]: Session 7 logged out. Waiting for processes to exit.
May 24 19:56:04 tpad1.home.arpa systemd-logind[1119]: Failed to abandon session scope, ignoring: Connection timed out
May 24 19:54:49 tpad1.home.arpa systemd-logind[1119]: Session 6 logged out. Waiting for processes to exit.
May 24 19:54:49 tpad1.home.arpa systemd-logind[1119]: Failed to abandon session scope, ignoring: Connection timed out
May 24 19:53:59 tpad1.home.arpa lightdm[1661]: Error terminating login1 session: Timeout was reached
May 24 19:53:34 tpad1.home.arpa NetworkManager[5196]: <info> [1748109214.8893] device (enp5s0): Activation: successful, device activated.
May 24 19:53:34 tpad1.home.arpa NetworkManager[5196]: <info> [1748109214.8890] manager: NetworkManager state is now CONNECTED_GLOBAL
May 24 19:53:34 tpad1.home.arpa NetworkManager[5196]: <info> [1748109214.8886] device (enp5s0): state change: secondaries -> activated (reason 'none', managed-type: 'full')
May 24 19:53:34 tpad1.home.arpa NetworkManager[5196]: <info> [1748109214.8882] device (enp5s0): state change: ip-check -> secondaries (reason 'none', managed-type: 'full')
May 24 19:53:34 tpad1.home.arpa lightdm[1661]: Error terminating login1 session: Timeout was reached
May 24 19:53:34 tpad1.home.arpa systemd-logind[1119]: Session 5 logged out. Waiting for processes to exit.
May 24 19:53:34 tpad1.home.arpa systemd-logind[1119]: Failed to abandon session scope, ignoring: Connection timed out
May 24 19:53:10 tpad1.home.arpa mkinitcpio[46205]: ==> Build complete.
May 24 19:53:10 tpad1.home.arpa mkinitcpio[46205]: -> Running build hook: [sd-shutdown]
May 24 19:53:10 tpad1.home.arpa mkinitcpio[46205]: ==> Starting build: 'none'
May 24 19:53:10 tpad1.home.arpa NetworkManager[5196]: <info> [1748109190.1970] device (enp5s0): state change: ip-config -> ip-check (reason 'none', managed-type: 'full')
May 24 19:53:09 tpad1.home.arpa systemd-resolved[496]: enp5s0: Bus client set DNS server list to: 192.168.1.7
May 24 19:53:09 tpad1.home.arpa systemd-resolved[496]: enp5s0: Bus client set default route setting: yes
May 24 19:53:09 tpad1.home.arpa systemd-resolved[496]: enp5s0: Bus client set search domain list to: home.arpa
May 24 19:53:09 tpad1.home.arpa NetworkManager[5196]: <info> [1748109189.8447] policy: set 'lan-eth0' (enp5s0) as default for IPv4 routing and DNS
May 24 19:53:09 tpad1.home.arpa NetworkManager[5196]: <info> [1748109189.8431] dhcp4 (enp5s0): state changed new lease, address=192.168.1.50
May 24 19:53:09 tpad1.home.arpa NetworkManager[5196]: <info> [1748109189.6718] dhcp4 (enp5s0): state changed new lease, address=192.168.1.50, acd pending
May 24 19:53:09 tpad1.home.arpa udisksd[2592]: udisks daemon version 2.10.1 exiting
May 24 19:53:09 tpad1.home.arpa systemd[1]: Cannot stop frozen unit User Manager for UID 968.
May 24 19:53:09 tpad1.home.arpa systemd[1]: Stopping Daemon for power management...
I was forced to hold down the power button to reboot.
So I decided to update to the lastest stable release yesterday, but stil got hit with the same issue after suspending/resuming.
I found a few similar reports, like this one:
https://bbs.archlinux.org/viewtopic.php?pid=2180537#p2180537
I was running 6.14.4, now I’m on 6.14.6 and systemd is 257.5-3-manjaro. It still unclear to me if this is an issue with systemd or the kernel.
I need to read and google a little bit more…