Arch Linux

aHumanPerson

Member

From: Canada

Registered: 2022-03-31

Posts: 17

Unable to login for 90 seconds after resuming from sleep

When resuming from suspend on my laptop I am unable to log in for the next 90 seconds. All I see is a mouse cursor on a black screen, though I can move it around. If I switch to a TTY the login prompt shows up but my shell doesn't start.
Sometimes it even seems to go back to sleep, and then I have to wait another 90 seconds. Running KDE.

This has been happening for a while now, more than a couple weeks.

journalctl -b output: http://sprunge.us/Wp2ovY
dmesg output: http://sprunge.us/xm0yCF

seth

Member

Registered: 2012-09-03

Posts: 51,768

Re: Unable to login for 90 seconds after resuming from sleep

May 30 18:47:07 framework python3[3393]: ERROR: Can't get value of subfeature temp1_input: Can't read

There's some bogus temperature monitoring script messing the journal, but it also clocks every 2s during the "hang"

May 30 18:48:21 framework systemd-sleep[3073]: System returned from sleep state.
May 30 18:48:21 framework kernel: PM: suspend exit
…
May 30 18:48:21 framework systemd[1]: Started Session 5 of User smcbride.
…
May 30 18:48:27 framework systemd[1]: libvirtd.service: Deactivated successfully.
May 30 18:48:27 framework systemd[1]: libvirtd.service: Unit process 952 (dnsmasq) remains running after unit stopped.
May 30 18:48:27 framework systemd[1]: libvirtd.service: Unit process 953 (dnsmasq) remains running after unit stopped.
…
May 30 18:49:18 framework python3[4593]: ERROR: Can't get value of subfeature temp1_input: Can't read
May 30 18:49:20 framework python3[4594]: ERROR: Can't get value of subfeature temp1_input: Can't read
…
May 30 18:49:51 framework appimagelauncherd[1329]: Executing deferred operations
May 30 18:49:51 framework appimagelauncherd[1329]: Integrating: /home/smcbride/.Xauthority-c
May 30 18:49:51 framework appimagelauncherd[1329]: ERROR: file does not exist, cannot integrate
…
May 30 18:49:51 framework systemd[1]: Stopped target Sleep.

You also have dnsmasq, resolved, networkmanager, systemd-networkd and iwd running.

* Start by fixing the network setup, chose NM or systemd-networkd, disable the other
If you want to use iwd as backend for NM, https://wiki.archlinux.org/title/Networ … Fi_backend and disable iwd.

* I've no idea whether it's possible to mix dnsmasq and resolved, so that might be the next thing to look at.
Since libvirtd stops after the resume but leaves dnsmasq pending, stop libvirtd and dnsmasq before the S3

* Stop appimagelauncherd.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc