You are not logged in.

Pages: 1

#1 2024-12-07 05:22:10

coolpanda
Member
Registered: 2022-01-01
Posts: 27

Freeze at login screen after wake up from sleep

My laptop running arch freezes at the login screen after being on sleep for a while. I have to then force shutdown it and boot again to make it run. While freezed on the login screen, I can see the time is also frozen to when the laptop was put to sleep. I have attached journalctl logs below. The time around 9 is before sleep and time around 10 is when its frozen. Thanks.

Dec 07 09:36:51 archlinux plasmashell[1164]: qrc:/qt/qml/org/kde/kirigami/dialogs/PromptDialog.qml:135: TypeError: Cannot read property 'Success' of undefined
Dec 07 09:36:51 archlinux plasmashell[1164]: qrc:/qt/qml/org/kde/kirigami/dialogs/PromptDialog.qml:97: TypeError: Cannot read property 'None' of undefined
Dec 07 09:37:41 archlinux wireplumber[1187]: spa.bluez5.native: RFCOMM receive command but modem not available: AT+VDBTY=2,1,9,2,9
Dec 07 09:37:41 archlinux wireplumber[1187]: spa.bluez5.native: RFCOMM receive command but modem not available: AT+VDSF=7
Dec 07 09:37:41 archlinux wireplumber[1187]: spa.bluez5.native: RFCOMM receive command but modem not available: AT+VDRV=10,1,38913,2,111,3,11072,4,11072,5,111,6,11072,7,11072,8,777,9,026,10,026
Dec 07 09:37:41 archlinux wireplumber[1187]: spa.bluez5.native: RFCOMM receive command but modem not available: AT+OESF=5,15
Dec 07 09:37:54 archlinux kded6[1103]: org.kde.pulseaudio: No object for name "bluez_output.84_0F_2A_F7_FF_05.1"
Dec 07 09:37:54 archlinux kdeconnectd[1407]: 2024-12-07T09:37:54 org.kde.pulseaudio: No object for name "bluez_output.84_0F_2A_F7_FF_05.1"
Dec 07 09:37:54 archlinux plasmashell[1164]: org.kde.pulseaudio: No object for name "bluez_output.84_0F_2A_F7_FF_05.1"
Dec 07 09:37:56 archlinux bluetoothd[805]: No matching connection for device
Dec 07 09:43:54 archlinux wpa_supplicant[815]: wlo1: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-54 noise=9999 txrate=351000
Dec 07 09:45:01 archlinux konsole[3647]: kf.notifications: Playing audio notification failed: Destroyed
Dec 07 09:45:04 archlinux systemd[903]: app-\x7b92c662ec\x2d3ad3\x2d4619\x2dbe4f\x2d1bfa6032a972\x7d@919a99e7d7594670b31a7c0793a0f6a4.service: Consumed 5min 30.062s CPU time, 2.1G memory peak.
Dec 07 09:45:06 archlinux plasmashell[1164]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml:136: TypeError: Cannot read property 'screenGeometry' of null
Dec 07 09:45:06 archlinux plasmashell[1164]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml:250: TypeError: Cannot read property 'plasmoid' of undefined
Dec 07 09:45:06 archlinux systemd[903]: plasma-plasmashell.service: Consumed 26.705s CPU time, 694M memory peak.
Dec 07 09:45:07 archlinux kscreenlocker_greet[4171]: kf.svg: The theme "breeze-alphablack" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format.
Dec 07 09:45:07 archlinux kscreenlocker_greet[4171]: kf.svg: The theme "breeze-alphablack" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format.
Dec 07 09:45:07 archlinux kscreenlocker_greet[4171]: kf.plasma.core: The theme "breeze-alphablack" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format.
Dec 07 09:45:07 archlinux kscreenlocker_greet[4171]: kf.plasma.core: The theme "breeze-alphablack" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format.
Dec 07 09:45:08 archlinux kscreenlocker_greet[4171]: kf.svg: The theme "breeze-alphablack" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format.
Dec 07 09:45:08 archlinux kscreenlocker_greet[4171]: qt.virtualkeyboard.hunspell: Hunspell dictionary is missing for "en_US". Search paths QList("/usr/share/qt6/qtvirtualkeyboard/hunspell", "/usr/share/hunspell", "/usr/share/myspell/dicts")
Dec 07 09:45:15 archlinux ksmserver[1101]: org.kde.kf6.ksmserver: SmsDie timeout, client  "/usr/bin/kdeconnectd" ( 10145dbd1dd000173354410200000011010004 )
Dec 07 09:45:15 archlinux systemd[903]: kde-baloo.service: Killing process 1602 (baloo_file:sh0) with signal SIGKILL.
Dec 07 09:45:16 archlinux systemd[903]: kde-baloo.service: Consumed 54.900s CPU time, 530.3M memory peak.
Dec 07 09:45:16 archlinux systemd[903]: plasma-kwin_x11.service: Main process exited, code=exited, status=15/n/a
Dec 07 09:45:16 archlinux systemd[903]: plasma-kwin_x11.service: Failed with result 'exit-code'.
Dec 07 09:45:16 archlinux wpa_supplicant[815]: nl80211: send_event_marker failed: Source based routing not supported
Dec 07 09:45:16 archlinux wpa_supplicant[815]: wlo1: CTRL-EVENT-DISCONNECTED bssid=e8:48:b8:7f:e5:28 reason=3 locally_generated=1
Dec 07 09:45:16 archlinux wpa_supplicant[815]: wlo1: CTRL-EVENT-DSCP-POLICY clear_all
Dec 07 09:45:16 archlinux wpa_supplicant[815]: wlo1: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Dec 07 09:45:16 archlinux wpa_supplicant[815]: wlo1: CTRL-EVENT-DSCP-POLICY clear_all
Dec 07 09:45:16 archlinux wpa_supplicant[815]: wlo1: CTRL-EVENT-DSCP-POLICY clear_all
Dec 07 09:45:16 archlinux wpa_supplicant[815]: nl80211: deinit ifname=wlo1 disabled_11b_rates=0
Dec 07 10:30:45 archlinux kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Dec 07 10:30:45 archlinux kernel: sd 2:0:0:0: [sdb] Synchronizing SCSI cache
Dec 07 10:30:45 archlinux kernel: ata1.00: Entering standby power mode
Dec 07 10:30:45 archlinux kernel: ata3.00: Entering standby power mode
Dec 07 10:30:45 archlinux kernel: [Firmware Bug]: TSC ADJUST differs: CPU0 0 --> -13755975. Restoring
Dec 07 10:30:45 archlinux kernel: sd 2:0:0:0: [sdb] Starting disk
Dec 07 10:30:45 archlinux kernel: done.
Dec 07 10:30:45 archlinux kernel: random: crng reseeded on system resumption
Dec 07 10:30:45 archlinux dbus-broker[773]: A security policy denied :1.9 to send method call /midi/profile:org.bluez.GattProfile1.Release to :1.46.
Dec 07 10:30:46 archlinux kernel: sd 0:0:0:0: [sda] Starting disk
Dec 07 10:30:47 archlinux wpa_supplicant[815]: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface.P2PDevice dbus_property=P2PDeviceConfig getter failed
Dec 07 10:30:48 archlinux wpa_supplicant[815]: wlo1: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
Dec 07 10:30:48 archlinux wpa_supplicant[815]: wlo1: CTRL-EVENT-REGDOM-BEACON-HINT before freq=5180 max_tx_power=2000 no_ir=1
Dec 07 10:30:48 archlinux wpa_supplicant[815]: wlo1: CTRL-EVENT-REGDOM-BEACON-HINT after freq=5180 max_tx_power=2000
Dec 07 10:30:48 archlinux wpa_supplicant[815]: wlo1: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
Dec 07 10:30:48 archlinux wpa_supplicant[815]: wlo1: CTRL-EVENT-REGDOM-BEACON-HINT before freq=5220 max_tx_power=2000 no_ir=1
Dec 07 10:30:48 archlinux wpa_supplicant[815]: wlo1: CTRL-EVENT-REGDOM-BEACON-HINT after freq=5220 max_tx_power=2000
Dec 07 10:30:51 archlinux wpa_supplicant[815]: wlo1: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
Dec 07 10:30:51 archlinux wpa_supplicant[815]: wlo1: CTRL-EVENT-REGDOM-BEACON-HINT before freq=5805 max_tx_power=2000 no_ir=1
Dec 07 10:30:51 archlinux wpa_supplicant[815]: wlo1: CTRL-EVENT-REGDOM-BEACON-HINT after freq=5805 max_tx_power=2000
Dec 07 10:30:51 archlinux NetworkManager[776]: <warn>  [1733547651.5524] device (wlo1): no secrets: No agents were available for this request.
Dec 07 10:30:51 archlinux NetworkManager[776]: <warn>  [1733547651.5527] device (wlo1): Activation: failed for connection 'HomeWiFi_5G'
Dec 07 10:30:51 archlinux wpa_supplicant[815]: wlo1: WPS-PBC-ACTIVE
Dec 07 10:30:51 archlinux NetworkManager[776]: <warn>  [1733547651.5546] device (wlo1): no secrets: No agents were available for this request.
Dec 07 10:30:51 archlinux NetworkManager[776]: <warn>  [1733547651.5551] device (wlo1): Activation: failed for connection 'HomeWiFi'
Dec 07 10:30:52 archlinux wpa_supplicant[815]: wlo1: WPS-CANCEL
Dec 07 10:30:52 archlinux wpa_supplicant[815]: wlo1: Reject scan trigger since one is already pending
Dec 07 10:31:48 archlinux systemd-resolved[735]: Switching to fallback DNS server 1.1.1.1#cloudflare-dns.com.
Dec 07 10:32:28 archlinux systemd-logind[778]: System is powering down.
Dec 07 10:32:28 archlinux sddm-helper[897]: Signal received: SIGTERM
Dec 07 10:32:28 archlinux sddm[827]: Authentication error: SDDM::Auth::ERROR_INTERNAL "Process crashed"
Dec 07 10:32:28 archlinux sddm[827]: Auth: sddm-helper (--socket /tmp/sddm-auth-6571acc4-95dc-43ac-8547-c1830f7fcaa1 --id 1 --start /usr/bin/startplasma-x11 --user user) crashed (exit code 1)
Dec 07 10:32:28 archlinux sddm[827]: Authentication error: SDDM::Auth::ERROR_INTERNAL "Process crashed"
Dec 07 10:32:28 archlinux sddm[827]: Auth: sddm-helper exited with 1
Dec 07 10:32:28 archlinux sddm[827]: Signal received: SIGTERM
Dec 07 10:32:28 archlinux udisksd[1099]: udisks daemon version 2.10.1 exiting
Dec 07 10:32:28 archlinux systemd[903]: background.slice: Consumed 1min 1.031s CPU time, 746.5M memory peak.
Dec 07 10:32:28 archlinux wireplumber[1187]: wireplumber: stopped by signal: Terminated
Dec 07 10:32:28 archlinux wireplumber[1187]: wireplumber: disconnected from pipewire
Dec 07 10:32:28 archlinux Tor[828]: Your system clock just jumped 3656 seconds forward; assuming established circuits no longer work.
Dec 07 10:32:28 archlinux Tor[828]: Interrupt: exiting cleanly.
Dec 07 10:32:29 archlinux systemd[903]: session.slice: Consumed 1min 10.584s CPU time, 984.7M memory peak.
Dec 07 10:32:29 archlinux systemd[903]: app.slice: Consumed 5min 57.252s CPU time, 2.5G memory peak.
Dec 07 10:32:29 archlinux systemd[1]: user@1000.service: Consumed 8min 17.280s CPU time, 4.2G memory peak.
Dec 07 10:32:29 archlinux systemd[1]: user-1000.slice: Consumed 8min 18.390s CPU time, 4.3G memory peak.
Dec 07 10:32:29 archlinux wpa_supplicant[815]: wlo1: CTRL-EVENT-DSCP-POLICY clear_all
Dec 07 10:32:29 archlinux dbus-broker-launch[746]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
Dec 07 10:32:29 archlinux wpa_supplicant[815]: wlo1: CTRL-EVENT-DSCP-POLICY clear_all
Dec 07 10:32:29 archlinux wpa_supplicant[815]: nl80211: deinit ifname=wlo1 disabled_11b_rates=0
Dec 07 10:32:29 archlinux wpa_supplicant[815]: wlo1: CTRL-EVENT-TERMINATING
Dec 07 10:32:29 archlinux systemd[1]: user.slice: Consumed 8min 19.647s CPU time, 4.4G memory peak.
Dec 07 10:32:29 archlinux systemd[1]: Shutting down.

Last edited by coolpanda (2024-12-07 05:24:28)

Offline

#2 2024-12-07 16:28:39

seth
Member
Registered: 2012-09-03
Posts: 59,911

Re: Freeze at login screen after wake up from sleep

Dec 07 09:45:15 archlinux systemd[903]: kde-baloo.service: Killing process 1602 (baloo_file:sh0) with signal SIGKILL.
Dec 07 09:45:16 archlinux systemd[903]: kde-baloo.service: Consumed 54.900s CPU time, 530.3M memory peak.
Dec 07 09:45:16 archlinux systemd[903]: plasma-kwin_x11.service: Main process exited, code=exited, status=15/n/a
Dec 07 09:45:16 archlinux systemd[903]: plasma-kwin_x11.service: Failed with result 'exit-code'.

Can you please post the entire journal and not just some random lines?
There's a 45m gap, but the sleep itself isn't logged.
For the previous boot:

sudo journalctl -b -1 | curl -F 'file=@-' 0x0.st

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

Offline

#3 2024-12-07 16:49:17

coolpanda
Member
Registered: 2022-01-01
Posts: 27

Re: Freeze at login screen after wake up from sleep

seth wrote:
Dec 07 09:45:15 archlinux systemd[903]: kde-baloo.service: Killing process 1602 (baloo_file:sh0) with signal SIGKILL.
Dec 07 09:45:16 archlinux systemd[903]: kde-baloo.service: Consumed 54.900s CPU time, 530.3M memory peak.
Dec 07 09:45:16 archlinux systemd[903]: plasma-kwin_x11.service: Main process exited, code=exited, status=15/n/a
Dec 07 09:45:16 archlinux systemd[903]: plasma-kwin_x11.service: Failed with result 'exit-code'.

Can you please post the entire journal and not just some random lines?
There's a 45m gap, but the sleep itself isn't logged.
For the previous boot:

sudo journalctl -b -1 | curl -F 'file=@-' 0x0.st

Sure, here it is: http://0x0.st/XhzM.txt

18:27 to 21:03 can be assumed as the sleep period.

Offline

#4 2024-12-07 17:07:41

seth
Member
Registered: 2012-09-03
Posts: 59,911

Re: Freeze at login screen after wake up from sleep

Unrelated: Disable systemd-networkd if you want to use NetworkManager.

Sleep:

Dec 07 18:27:28 archlinux systemd[1]: Reached target Sleep.
Dec 07 18:27:28 archlinux systemd-sleep[75844]: Successfully froze unit 'user.slice'.
Dec 07 18:27:28 archlinux systemd-sleep[75844]: Performing sleep operation 'suspend'...
Dec 07 21:03:32 archlinux kernel: ACPI: PM: Preparing to enter system sleep state S3
Dec 07 21:03:32 archlinux kernel: ACPI: PM: Waking up from system sleep state S3
Dec 07 21:03:32 archlinux systemd-sleep[75844]: System returned from sleep operation 'suspend'.
Dec 07 21:03:34 archlinux systemd-sleep[75844]: Successfully thawed unit 'user.slice'.
Dec 07 21:03:34 archlinux systemd[1]: Stopped target Sleep.

kwin dies before the sleep 

Dec 07 18:27:27 archlinux systemd[912]: plasma-kwin_x11.service: Main process exited, code=exited, status=15/n/a
Dec 07 18:27:27 archlinux systemd[912]: plasma-kwin_x11.service: Failed with result 'exit-code'.
Dec 07 18:27:27 archlinux systemd[912]: plasma-kwin_x11.service: Consumed 10min 46.305s CPU time, 234.4M memory peak.

Actually the entire session gets torn down:

Dec 07 18:27:27 archlinux systemd[912]: Stopped target plasma-workspace-x11.target.
Dec 07 18:27:27 archlinux systemd[912]: Stopped target KDE Plasma Workspace.

Do you log out before you sleep the system?

Because of 

Dec 07 18:27:18 archlinux systemd-logind[754]: Lid closed.
Dec 07 21:03:32 archlinux systemd-logind[754]: Lid opened.

what if you don't use the lid but "systemctl sleep"?

PS: your journal is full of spam from discord and qjournalctl - you might want to address that.

Last edited by seth (2024-12-07 17:08:39)

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

Offline

#5 2024-12-08 06:37:44

coolpanda
Member
Registered: 2022-01-01
Posts: 27

Re: Freeze at login screen after wake up from sleep

Do you log out before you sleep the system?

No

Dec 07 18:27:18 archlinux systemd-logind[754]: Lid closed.
Dec 07 21:03:32 archlinux systemd-logind[754]: Lid opened.

Yes, I close the lid after I sleep the system. Also, I've configured my power settings to lock the system on lid close. But I don't think this should affect anything as system's already on sleep before lid close.

what if you don't use the lid but "systemctl sleep"?

No, I don't use lid close as a way to sleep the system. I close the lid after I put it to sleep. Also, I just tried that, and the freeze doesn't happen if done this way.

PS: your journal is full of spam from discord and qjournalctl - you might want to address that.

Yes, I'm trying to fix that.

Last edited by coolpanda (2024-12-08 06:40:36)

Offline

#6 2024-12-08 07:40:04

seth
Member
Registered: 2012-09-03
Posts: 59,911

Re: Freeze at login screen after wake up from sleep

I close the lid after I sleep the system.

Dec 07 10:32:13 archlinux kernel: input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:19/PNP0C09:01/PNP0C0D:00/input/input0
Dec 07 10:32:13 archlinux kernel: ACPI: button: Lid Switch [LID]
Dec 07 10:32:13 archlinux kernel: ata3.00: Features: Dev-Sleep NCQ-sndrcv NCQ-prio
Dec 07 10:32:57 archlinux kded6[1116]: kscreen.kded: PowerDevil SuspendSession action not available!
Dec 07 18:27:18 archlinux systemd-logind[754]: Lid closed.
Dec 07 18:27:18 archlinux kscreenlocker_greet[75752]: kf.svg: The theme "breeze-alphablack" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format.
Dec 07 18:27:27 archlinux systemd-logind[754]: Suspending...
Dec 07 18:27:27 archlinux NetworkManager[752]: <info>  [1733576247.4433] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Dec 07 18:27:27 archlinux NetworkManager[752]: <info>  [1733576247.4435] device (B4:31:61:2D:59:6E): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
Dec 07 18:27:27 archlinux NetworkManager[752]: <info>  [1733576247.4439] manager: NetworkManager state is now ASLEEP
Dec 07 18:27:27 archlinux NetworkManager[752]: <info>  [1733576247.4441] device (wlo1): state change: activated -> deactivating (reason 'sleeping', managed-type: 'full')
Dec 07 18:27:27 archlinux fprintd[75782]: Device reported an error during verify: Cannot run while suspended.
Dec 07 18:27:27 archlinux NetworkManager[752]: <info>  [1733576247.7516] device (wlo1): state change: deactivating -> disconnected (reason 'sleeping', managed-type: 'full')
Dec 07 18:27:28 archlinux NetworkManager[752]: <info>  [1733576248.2841] device (wlo1): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
Dec 07 18:27:28 archlinux systemd[1]: Reached target Sleep.
Dec 07 18:27:28 archlinux systemd[1]: Starting System Suspend...
Dec 07 18:27:28 archlinux systemd-sleep[75844]: Successfully froze unit 'user.slice'.
Dec 07 18:27:28 archlinux systemd-sleep[75844]: Performing sleep operation 'suspend'...
Dec 07 18:27:28 archlinux kernel: PM: suspend entry (deep)
Dec 07 21:03:32 archlinux kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Dec 07 21:03:32 archlinux kernel: ACPI: PM: Preparing to enter system sleep state S3
Dec 07 21:03:32 archlinux kernel: ACPI: PM: Waking up from system sleep state S3
Dec 07 21:03:32 archlinux kernel: PM: suspend exit
Dec 07 21:03:32 archlinux systemd-logind[754]: Lid opened.
Dec 07 21:03:32 archlinux systemd-sleep[75844]: System returned from sleep operation 'suspend'.
Dec 07 21:03:34 archlinux systemd-sleep[75844]: Successfully thawed unit 'user.slice'.
Dec 07 21:03:34 archlinux systemd[1]: systemd-suspend.service: Deactivated successfully.
Dec 07 21:03:34 archlinux systemd[1]: Finished System Suspend.
Dec 07 21:03:34 archlinux systemd[1]: Stopped target Sleep.
Dec 07 21:03:34 archlinux systemd[1]: Reached target Suspend.
Dec 07 21:03:34 archlinux systemd-logind[754]: Operation 'suspend' finished.
Dec 07 21:03:34 archlinux systemd[1]: Stopped target Suspend.
Dec 07 21:03:34 archlinux NetworkManager[752]: <info>  [1733585614.4794] manager: sleep: wake requested (sleeping: yes  enabled: yes)

You closed the lid and that triggered the screenlocker and the sleep - if the system had been asleep when closing the lid, the event could not have been logged.

Also, I've configured my power settings to lock the system on lid close. But I don't think this should affect anything as system's already on sleep before lid close.

1. wrong premise.
2. even w/ a correct premise we're not living in "shouldland" …
=> Disable that, see what happens.

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

Offline

Pages: 1

Board footer

Powered by FluxBB