Some issues with screen lock/sleep and freezing desktop

CorrectPoke · March 8, 2025, 11:02am

Fresh install here, and I have been having a few issues with Plasma on my multi-monitor setup. There are a few different issues, but I am suspicious, though not positive that they may all be rooted in the same issue.

On a fresh boot everything seems to run fine and no issues present. However after resuming from sleep, or more frequently, after waking the monitors after they have powered off (lock screen after inactivity > turn off monitors after further inactivity) the issues begin. Through frustratingly, not every time.

The first noticeable issue is that one of my monitors will have its resolution locked at 640x480. Power cycling the monitor does not fix, nor am I able to change the resolution anymore in the settings. Unplugging the DP cable and re-plugging brings the monitor back to normal. Of my three monitors, the primary (LG 38WN95C) is connected via DP, one secondary (both secondary monitors Dell U2212HM in portrait mode) is connected via DP, the third via a HDMI>DVI adapter. This issue seems to follow whichever secondary is connected via the DP cable so I have another HDMI>DVI cable on the way so this might not be an issue for much longer. I have not seen this issue in the past few days, though it was inconsistent to begin with. The LG has never had this issue.

After a seemingly random amount of sleep/wake or monitor poweroffs the above and more annoying issues begin. The desktop will start having frequent hitching issues. I’m able to consistently trigger the hitching by trying to load a video in a browser, though I have had the hitching start randomly as well. While it’s like this the entire desktop freezes, unable to move the mouse or use the keyboard until it stops, though keys and mouseclicks are queued and fired all at once when the hitching stops. If I have music playing it continues playing normally so I don’t think it’s a full system freeze, only the Plasma desktop. journalctl only spits out kwin_wayland_drm: The main thread was hanging temporarily!
during this time. So no Pageflip errors like I’ve seen in a lot of other topics with this issue. Sometimes it will freeze for 10-20 seconds and start working normally and other times it will freeze>update screen once>frozen again>repeat indefinitely. This will continue until the PC is rebooted at which point everything works as expected.

The third issue is when the above issues start appearing, the Power Management section of the system settings stops loading. The settings app hangs entirely and needs to be killed. I’ve been using this as an indicator for when the hitching will start, as the resolution issue doesn’t always happen, but if I can’t load that section of the settings app I know that loading videos will freeze my desktop. This isn’t a huge deal as I don’t need to change these settings, but I mention it because all of my issues only start when the PC is brought out of sleep or after the monitors get disconnected due to inactivity, so I think maybe it’s related.

I have not switched to an X11 session for long enough to say it’s not happening there, but when I briefly switched these issues disappeared.

Sorry this is a lot, I’m new to desktop linux so my troubleshooting is not great. This is also my first foray into Arch so I’m largely unfamiliar with its tools.

System:

Operating System: EndeavourOS 
KDE Plasma Version: 6.3.2
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Kernel Version: 6.13.5-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 9800X3D 8-Core Processor
Memory: 30.5 GiB of RAM
Graphics Processor 1: AMD Radeon RX 7900 XTX
Graphics Processor 2: AMD Radeon Graphics
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: X870 AORUS ELITE WIFI7
System Version: -CF-WCP

johnandmegh · March 10, 2025, 2:59am

Hi! Based on your description, I wonder if you might be experiencing the following bug reported in the KDE Bugtracking System? https://bugs.kde.org/show_bug.cgi?id=495765

If the situation there sounds like the one you’re dealing with, comment #13 describes what sounds like a solution coming down the pipeline in a future Linux kernel version, since it’s rooted in the AMD graphics drivers. Perhaps a graphics-related issue might make sense, since you mentioned that audio continues to play uninterrupted?

CorrectPoke · March 10, 2025, 10:06pm

It’s possible, as the issues do seem similar, though I am not having any issues with logging back into the machine, nor any stability issues outside of the random hitching. Sleep/resume seems to function just fine, but something is specifically causing the desktop renderer (?) to freeze periodically after a currently unknown wake process fails. And while I’m thinking that resume may be causing this, I mainly get these issues after letting the monitors power off from inactivity. As was mentioned in the linked post, the time the monitors were off weirdly does seem to effect the likelihood of issues appearing, so I at least have something that I can test out in the mean time.

Currently on a fresh boot as of this morning, and after sleeping all day while at work this resume seems to be fine. The only thing I see in common with the linked journalctl logs is the

kscreenlocker_greet[5489]: qt.qpa.wayland: Could not create EGL surface (EGL error 0x3000)
kscreenlocker_greet[5489]: qt.qpa.wayland: Could not create EGL surface (EGL error 0x3000)
kscreenlocker_greet[5489]: qt.qpa.wayland: Could not create EGL surface (EGL error 0x3000)
>kscreenlocker_greet[5489]: Failed to write to the pipe: Bad file descriptor.

Bad file descriptor line.
There is also

plasmashell[1564]: The cached device pixel ratio value was stale on window update.  Please file a QTBUG which explains how to reproduce.

which I see somewhat frequently, though I have no idea what it means or if it’s relevant. I’m scared to list too many of these being that I don’t know what they mean, and I don’t want to flood the thought process with too many irrelevant statuses. I can post a larger log excerpt once I get this machine back into it’s weird state and let the smarter-than-me folks sort it out I suppose.

In the mean time, I’m going to let the monitors poweroff for a while and see if anything looks different afterwards. I see a kernel update to 6.13.6 but nothing in the changelog looks like it addressed this specifically so I’ll hold off on that until I can poke at this a bit more.

CorrectPoke · March 11, 2025, 2:43am

Can’t find an edit post button so adding on a new reply.

As an update, after letting the monitors poweroff for a few hours the issue has reappeared, despite not being present after the initial resume today. It’s still possible the system was already in a funny state after waking it earlier and simply showed no issues, but as of now the most consistent trigger for this is still letting the monitors go to sleep, waiting a while, then waking them up again.

So the order for today’s issues is as of now:
Fresh boot this morning: everything OK
PC put to sleep while I was away for the day
Resume this afternoon: everything OK
After going AFK after the last post the session auto locks and monitors power off 1 min later
After a few hours, wake the monitors up and login like normal: system starts hitching when playing videos

As a side note, when waking the monitors up again, it plays a sound for disconnecting a device and immediately plays another one for connecting one. I assume this is one of the monitors being “disconnected” and then reconnected.

I’ve attached the last 200 lines of journalctl below. It starts around when I was making the last post (~line 24, 18:08) and ends just after I woke the monitors and tested to see if things were broken (~line 67, 21:57). The Main Thread Hanging lines was me loading a video in Firefox, and there is more than usual because this was one of the times where it continued hitching even after the initial 10-15sec freeze it usually does.

journalctl -b -n 200
Mar 10 17:55:57 user plasma-systemmonitor[8596]: file:///usr/share/ksysguard/sensorfaces/org.kde.ksysguard.applicationstable/contents/ui/FullRepresentation.qml:158:13: TypeError: Cannot read property 'detailsWidth' of null
Mar 10 17:55:57 user plasma-systemmonitor[8596]: file:///usr/share/ksysguard/sensorfaces/org.kde.ksysguard.applicationstable/contents/ui/FullRepresentation.qml:159: TypeError: Value is null and could not be converted to an object
Mar 10 17:55:57 user plasma-systemmonitor[8596]: file:///usr/lib/qt6/qml/org/kde/kirigami/ScrollablePage.qml:249:9: QML MouseArea: Binding loop detected for property "implicitHeight":
                                                    file:///usr/lib/qt6/qml/org/kde/kirigami/ScrollablePage.qml:264:13
Mar 10 17:55:57 user plasma-systemmonitor[8596]: file:///usr/lib/qt6/qml/org/kde/kirigami/ScrollablePage.qml:249:9: QML MouseArea: Binding loop detected for property "implicitHeight":
                                                    file:///usr/lib/qt6/qml/org/kde/kirigami/ScrollablePage.qml:264:13
Mar 10 17:55:57 user plasma-systemmonitor[8596]: file:///usr/lib/qt6/qml/org/kde/kirigami/ScrollablePage.qml:249:9: QML MouseArea: Binding loop detected for property "implicitHeight":
                                                    file:///usr/lib/qt6/qml/org/kde/kirigami/ScrollablePage.qml:264:13
Mar 10 17:56:01 user plasma-systemmonitor[8596]: file:///usr/lib/qt6/qml/org/kde/kirigami/ScrollablePage.qml:252:13: QML MouseArea: Binding loop detected for property "height"
Mar 10 17:56:01 user plasma-systemmonitor[8596]: qrc:/qt/qml/org/kde/kirigami/dialogs/Dialog.qml:344:18: QML ScrollView: Binding loop detected for property "calculatedImplicitWidth":
                                                    qrc:/qt/qml/org/kde/kirigami/dialogs/Dialog.qml:358:9
Mar 10 17:56:28 user plasma-systemmonitor[8596]: file:///usr/lib/qt6/qml/org/kde/kirigami/ScrollablePage.qml:252:13: QML MouseArea: Binding loop detected for property "height"
Mar 10 17:56:28 user plasma-systemmonitor[8596]: qrc:/qt/qml/org/kde/kirigami/dialogs/Dialog.qml:344:18: QML ScrollView: Binding loop detected for property "calculatedImplicitWidth":
                                                    qrc:/qt/qml/org/kde/kirigami/dialogs/Dialog.qml:358:9
Mar 10 17:56:32 user plasma-systemmonitor[8596]: QProcess: Destroyed while process ("/usr/lib/ksysguard/ksgrd_network_helper") is still running.
Mar 10 17:56:32 user plasma-systemmonitor[8596]: org.kde.ksysguard.plugin.network: Helper process terminated abnormally: ""
Mar 10 17:56:32 user systemd[1212]: app-org.kde.plasma\x2dsystemmonitor@56d96e98ccf04471a0de162b479badcc.service: Consumed 7.088s CPU time, 190.1M memory peak.
Mar 10 18:06:34 user sudo[8147]: pam_unix(sudo:session): session closed for user root
Mar 10 18:06:36 user konsole[6398]: QThreadStorage: Thread 0x619c1e9ad3b0 exited after QThreadStorage 9 destroyed
Mar 10 18:06:36 user systemd[1212]: app-org.kde.konsole@1c4ef7b95fbe4452b6a8a50d148330be.service: Consumed 656ms CPU time, 143.2M memory peak.
Mar 10 18:06:36 user systemd[1212]: app-org.kde.konsole-6398.scope: Consumed 1.855s CPU time, 23.7M memory peak.
Mar 10 18:07:56 user systemd[1]: Starting Time & Date Service...
Mar 10 18:07:56 user systemd[1]: Started Time & Date Service.
Mar 10 18:08:01 user systemd[1212]: app-firefox@9091b62130da40d0b7c4896778821e8b.service: Consumed 3min 12.668s CPU time, 1.3G memory peak.
Mar 10 18:08:26 user systemd[1]: systemd-timedated.service: Deactivated successfully.
Mar 10 18:13:57 user kded6[1500]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_75_00.6.analog-stereo.monitor"
Mar 10 18:13:57 user kdeconnectd[1786]: 2025-03-10T18:13:57 org.kde.pulseaudio: No object for name "alsa_output.pci-0000_75_00.6.analog-stereo.monitor"
Mar 10 18:13:57 user plasmashell[1564]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_75_00.6.analog-stereo.monitor"
Mar 10 18:13:57 user kernel: amdgpu 0000:03:00.0: [drm] REG_WAIT timeout 1us * 100 tries - dcn32_program_compbuf_size line:140
Mar 10 18:40:56 user steam[1913]: [2025-03-10 18:40:56] Background update loop checking for update. . .
Mar 10 18:40:56 user steam[1913]: [2025-03-10 18:40:56] Downloading manifest: ....
Mar 10 18:40:56 user steam[1913]: [2025-03-10 18:40:56] Manifest download: send request
Mar 10 18:40:56 user kernel: x86/split lock detection: #DB: CHTTPClientThre/3003 took a bus_lock trap at address: 0x59ce41b4
Mar 10 18:40:56 user kernel: x86/split lock detection: #DB: CHTTPClientThre/3003 took a bus_lock trap at address: 0x59ce41b4
Mar 10 18:40:56 user steam[1913]: [2025-03-10 18:40:56] Manifest download: waiting for download to finish
Mar 10 18:40:56 user kernel: x86/split lock detection: #DB: CHTTPClientThre/3003 took a bus_lock trap at address: 0x59ce41b4
Mar 10 18:40:56 user kernel: x86/split lock detection: #DB: CHTTPClientThre/3003 took a bus_lock trap at address: 0x59ce41b4
Mar 10 18:40:56 user kernel: x86/split lock detection: #DB: CHTTPClientThre/3003 took a bus_lock trap at address: 0x59ce41b4
Mar 10 18:40:56 user kernel: x86/split lock detection: #DB: CHTTPClientThre/3003 took a bus_lock trap at address: 0x59ce41b4
Mar 10 18:40:57 user kernel: x86/split lock detection: #DB: CHTTPClientThre/3003 took a bus_lock trap at address: 0x59ce41b4
Mar 10 18:40:57 user kernel: x86/split lock detection: #DB: CHTTPClientThre/3003 took a bus_lock trap at address: 0x59ce41b4
Mar 10 18:40:57 user kernel: x86/split lock detection: #DB: CHTTPClientThre/3003 took a bus_lock trap at address: 0x59ce41b4
Mar 10 18:40:57 user steam[1913]: [2025-03-10 18:40:57] Manifest download: finished
Mar 10 18:40:57 user steam[1913]: [2025-03-10 18:40:57] Download skipped by HTTP 304 Not Modified
Mar 10 18:40:57 user steam[1913]: [2025-03-10 18:40:57] Nothing to do
Mar 10 18:45:42 user NetworkManager[1001]: <info>  [1741646742.8260] dhcp4 (enp8s0): state changed new lease, address=....
Mar 10 18:45:42 user systemd[1]: Starting Network Manager Script Dispatcher Service...
Mar 10 18:45:42 user systemd[1]: Started Network Manager Script Dispatcher Service.
Mar 10 18:45:52 user systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Mar 10 19:22:05 user kdeconnectd[1786]: 2025-03-10T19:22:05 default: new capabilities for  "snip"
Mar 10 19:22:05 user kdeconnectd[1786]: 2025-03-10T19:22:05 kdeconnect.plugin.battery: No Primary Battery detected on this system. This may be a bug.
Mar 10 19:22:05 user kdeconnectd[1786]: 2025-03-10T19:22:05 kdeconnect.plugin.battery: Total quantity of batteries found:  0
Mar 10 19:22:05 user kdeconnectd[1786]: 2025-03-10T19:22:05 kdeconnect.plugin.battery: Primary Battery seems to have been removed. Suspending packets until it is reconnected.
Mar 10 19:22:06 user kdeconnectd[1786]: 2025-03-10T19:22:06 kdeconnect.plugin.clipboard: Ignoring clipboard without timestamp
Mar 10 19:45:42 user NetworkManager[1001]: <info>  [1741650342.8259] dhcp4 (enp8s0): state changed new lease, address=....
Mar 10 19:45:42 user systemd[1]: Starting Network Manager Script Dispatcher Service...
Mar 10 19:45:42 user systemd[1]: Started Network Manager Script Dispatcher Service.
Mar 10 19:45:52 user systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Mar 10 20:45:42 user NetworkManager[1001]: <info>  [1741653942.8248] dhcp4 (enp8s0): state changed new lease, address=....
Mar 10 20:45:42 user systemd[1]: Starting Network Manager Script Dispatcher Service...
Mar 10 20:45:42 user systemd[1]: Started Network Manager Script Dispatcher Service.
Mar 10 20:45:52 user systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Mar 10 21:45:42 user NetworkManager[1001]: <info>  [1741657542.8263] dhcp4 (enp8s0): state changed new lease, address=....
Mar 10 21:45:42 user systemd[1]: Starting Network Manager Script Dispatcher Service...
Mar 10 21:45:42 user systemd[1]: Started Network Manager Script Dispatcher Service.
Mar 10 21:45:52 user systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Mar 10 21:57:55 user kernel: HDR SB:01 1a 02 00 78 86 46 3c 5b 32 d8 82 cd 1c 04 0c
Mar 10 21:57:55 user kernel: HDR SB:09 3d 47 40 c8 01 f3 03 c8 01 c8 01 00 00 00 00
Mar 10 21:57:55 user kernel: HDR SB:01 1a 02 00 78 86 46 3c 5b 32 d8 82 cd 1c 04 0c
Mar 10 21:57:55 user kernel: HDR SB:09 3d 47 40 c8 01 f3 03 c8 01 c8 01 00 00 00 00
Mar 10 21:57:55 user kernel: HDR SB:01 1a 02 00 78 86 46 3c 5b 32 d8 82 cd 1c 04 0c
Mar 10 21:57:55 user kernel: HDR SB:09 3d 47 40 c8 01 f3 03 c8 01 c8 01 00 00 00 00
Mar 10 21:57:55 user kded6[1500]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_75_00.6.analog-stereo.monitor"
Mar 10 21:57:55 user plasmashell[1564]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_75_00.6.analog-stereo.monitor"
Mar 10 21:57:55 user kdeconnectd[1786]: 2025-03-10T21:57:55 org.kde.pulseaudio: No object for name "alsa_output.pci-0000_75_00.6.analog-stereo.monitor"
Mar 10 21:57:56 user plasmashell[1564]: file:///usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/main.qml:310:13: QML Image: Cannot open: file:///usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/start-here-kde-symbolic
Mar 10 21:57:56 user plasmashell[1564]: kde.plasmashell: requesting unexisting screen available rect -1
Mar 10 21:57:56 user plasmashell[1564]: kde.plasmashell: requesting unexisting screen available rect -1
Mar 10 21:57:56 user plasmashell[1564]: file:///usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/main.qml:310:13: QML Image: Cannot open: file:///usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/start-here-kde-symbolic
Mar 10 21:57:56 user plasmashell[1564]: file:///usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/main.qml:310:13: QML Image: Cannot open: file:///usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/start-here-kde-symbolic
Mar 10 21:57:56 user kded6[1500]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_75_00.6.analog-stereo.monitor"
Mar 10 21:57:56 user kdeconnectd[1786]: 2025-03-10T21:57:56 org.kde.pulseaudio: No object for name "alsa_output.pci-0000_75_00.6.analog-stereo.monitor"
Mar 10 21:57:56 user plasmashell[1564]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_75_00.6.analog-stereo.monitor"
Mar 10 21:57:57 user org_kde_powerdevil[1614]: [  1836] Removing connected display on bus 8
Mar 10 21:57:57 user org_kde_powerdevil[1614]: [  1836] Emitting DDCA_Display_Status_Event[55025.339:  DDCA_EVENT_DISPLAY_DISCONNECTED, card1-DP-1, dref: DDCA_Display_Ref[3], io_path:/dev/i2c-8, ddc working: false]
Mar 10 21:57:57 user org_kde_powerdevil[1614]: [  1836] libddcutil callback thread 0x76eb2802a550 started
Mar 10 21:57:57 user org_kde_powerdevil[1614]: [  1836] Started 1 event callback thread(s)
Mar 10 21:57:57 user kernel: HDR SB:01 1a 02 00 78 86 46 3c 5b 32 d8 82 cd 1c 04 0c
Mar 10 21:57:57 user kernel: HDR SB:09 3d 47 40 c8 01 f3 03 c8 01 c8 01 00 00 00 00
Mar 10 21:57:57 user kernel: HDR SB:01 1a 02 00 78 86 46 3c 5b 32 d8 82 cd 1c 04 0c
Mar 10 21:57:57 user kernel: HDR SB:09 3d 47 40 c8 01 f3 03 c8 01 c8 01 00 00 00 00
Mar 10 21:57:57 user kwin_wayland[1274]: kwin_core: KWin::LayerShellV1Window doesn't support setting maximized state
Mar 10 21:57:57 user kwin_wayland[1274]: kwin_core: KWin::LayerShellV1Window doesn't support setting fullscreen state
Mar 10 21:57:57 user kwin_wayland[1274]: kwin_core: KWin::LayerShellV1Window doesn't support setting maximized state
Mar 10 21:57:57 user kwin_wayland[1274]: kwin_core: KWin::LayerShellV1Window doesn't support setting fullscreen state
Mar 10 21:57:57 user plasmashell[1564]: file:///usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/main.qml:310:13: QML Image: Cannot open: file:///usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/start-here-kde-symbolic
Mar 10 21:57:57 user kernel: HDR SB:01 1a 02 00 78 86 46 3c 5b 32 d8 82 cd 1c 04 0c
Mar 10 21:57:57 user kernel: HDR SB:09 3d 47 40 c8 01 f3 03 c8 01 c8 01 00 00 00 00
Mar 10 21:57:57 user plasmashell[1564]: file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:233:17: Unable to assign [undefined] to bool
Mar 10 21:57:57 user kded6[1500]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_75_00.6.analog-stereo.monitor"
Mar 10 21:57:57 user plasmashell[1564]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_75_00.6.analog-stereo.monitor"
Mar 10 21:57:57 user kdeconnectd[1786]: 2025-03-10T21:57:57 org.kde.pulseaudio: No object for name "alsa_output.pci-0000_75_00.6.analog-stereo.monitor"
Mar 10 21:57:57 user plasmashell[1564]: file:///usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/main.qml:310:13: QML Image: Cannot open: file:///usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/start-here-kde-symbolic
Mar 10 21:57:57 user org_kde_powerdevil[1614]: [  1836] Adding connected display with bus 8
Mar 10 21:57:58 user org_kde_powerdevil[1614]: org.kde.powerdevil: [DDCutilDisplay]: ddca_get_non_table_vcp_value -3007
Mar 10 21:57:58 user org_kde_powerdevil[1614]: [  1836] Emitting DDCA_Display_Status_Event[55026.604:  DDCA_EVENT_DISPLAY_CONNECTED, card1-DP-1, dref: DDCA_Display_Ref[4], io_path:/dev/i2c-8, ddc working: true]
Mar 10 21:57:58 user org_kde_powerdevil[1614]: [  1836] libddcutil callback thread 0x76eb2800d220 started
Mar 10 21:57:58 user org_kde_powerdevil[1614]: [  1836] Started 1 event callback thread(s)
Mar 10 21:57:58 user org_kde_powerdevil[1614]: [  1614] Quiescing libddcutil API...
Mar 10 21:58:01 user org_kde_powerdevil[1614]: Error queiscing libdducitl API. 1 active API calls outstanding.
Mar 10 21:58:01 user org_kde_powerdevil[1614]: [  1614] Error queiscing libdducitl API. 1 active API calls outstanding.
Mar 10 21:58:01 user org_kde_powerdevil[1614]: org.kde.powerdevil: [DDCutilDisplay]: ddca_set_non_table_vcp_value -3032
Mar 10 21:58:01 user org_kde_powerdevil[1614]: library quiesced, ddca_set_non_table_vcp_value temporarily unavailable
Mar 10 21:58:01 user org_kde_powerdevil[1614]: org.kde.powerdevil: [DDCutilDisplay]: ddca_close_display -3032
Mar 10 21:58:01 user org_kde_powerdevil[1614]: [  1614] Display redetection starting.
Mar 10 21:58:01 user org_kde_powerdevil[1614]: library quiesced, ddca_close_display temporarily unavailable
Mar 10 21:58:01 user org_kde_powerdevil[1614]: [  1835] recheck thread terminating because watch thread terminated
Mar 10 21:58:01 user org_kde_powerdevil[1614]: [  1614] Watch thread terminated.
Mar 10 21:58:01 user org_kde_powerdevil[1614]: [  1614] Attempting to unlock display lock owned by different thread
Mar 10 21:58:01 user org_kde_powerdevil[1614]: [  1614] Unexpected error DDCRC_LOCKED from unlock_display_by_dpath(Display_Path[/dev/i2c-6])
Mar 10 21:58:03 user kscreenlocker_greet[9001]: qt.qpa.wayland: Could not create EGL surface (EGL error 0x3000)
Mar 10 21:58:03 user kscreenlocker_greet[9001]: qt.qpa.wayland: Could not create EGL surface (EGL error 0x3000)
Mar 10 21:58:03 user kscreenlocker_greet[9001]: qt.qpa.wayland: Could not create EGL surface (EGL error 0x3000)
Mar 10 21:58:03 user kscreenlocker_greet[9001]: Failed to write to the pipe: Bad file descriptor.
Mar 10 21:58:08 user plasmashell[1564]: The cached device pixel ratio value was stale on window update.  Please file a QTBUG which explains how to reproduce.
Mar 10 21:58:08 user plasmashell[1564]: The cached device pixel ratio value was stale on window update.  Please file a QTBUG which explains how to reproduce.
Mar 10 21:58:08 user systemd[1212]: Started Firefox - Web Browser.
Mar 10 21:58:08 user systemd[1]: Starting Time & Date Service...
Mar 10 21:58:08 user systemd[1]: Started Time & Date Service.
Mar 10 21:58:08 user rtkit-daemon[1312]: Supervising 6 threads of 3 processes of 1 users.
Mar 10 21:58:08 user rtkit-daemon[1312]: Supervising 6 threads of 3 processes of 1 users.
Mar 10 21:58:08 user rtkit-daemon[1312]: Supervising 6 threads of 3 processes of 1 users.
Mar 10 21:58:08 user rtkit-daemon[1312]: Supervising 6 threads of 3 processes of 1 users.
Mar 10 21:58:08 user rtkit-daemon[1312]: Successfully made thread 10219 of process 10075 owned by '1000' RT at priority 10.
Mar 10 21:58:08 user rtkit-daemon[1312]: Supervising 7 threads of 4 processes of 1 users.
Mar 10 21:58:09 user rtkit-daemon[1312]: Supervising 7 threads of 4 processes of 1 users.
Mar 10 21:58:09 user rtkit-daemon[1312]: Supervising 7 threads of 4 processes of 1 users.
Mar 10 21:58:09 user rtkit-daemon[1312]: Supervising 7 threads of 4 processes of 1 users.
Mar 10 21:58:09 user rtkit-daemon[1312]: Supervising 7 threads of 4 processes of 1 users.
Mar 10 21:58:09 user rtkit-daemon[1312]: Supervising 7 threads of 4 processes of 1 users.
Mar 10 21:58:09 user rtkit-daemon[1312]: Supervising 7 threads of 4 processes of 1 users.
Mar 10 21:58:11 user rtkit-daemon[1312]: Supervising 7 threads of 4 processes of 1 users.
Mar 10 21:58:11 user rtkit-daemon[1312]: Supervising 7 threads of 4 processes of 1 users.
Mar 10 21:58:11 user keepassxc[1871]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
Mar 10 21:58:15 user rtkit-daemon[1312]: Supervising 7 threads of 4 processes of 1 users.
Mar 10 21:58:15 user rtkit-daemon[1312]: Supervising 7 threads of 4 processes of 1 users.
Mar 10 21:58:15 user rtkit-daemon[1312]: Successfully made thread 10464 of process 10312 owned by '1000' RT at priority 10.
Mar 10 21:58:15 user rtkit-daemon[1312]: Supervising 8 threads of 5 processes of 1 users.
Mar 10 21:58:16 user firefox[10191]: Failed to create /home for shader cache (Permission denied)---disabling.
Mar 10 21:58:16 user firefox[10191]: Failed to create /home for shader cache (Permission denied)---disabling.
Mar 10 21:58:16 user firefox[10191]: Failed to create /home for shader cache (Permission denied)---disabling.
Mar 10 21:58:38 user systemd[1]: systemd-timedated.service: Deactivated successfully.
Mar 10 21:58:40 user kwin_wayland[1274]: kwin_wayland_drm: The main thread was hanging temporarily!
Mar 10 21:58:40 user kwin_wayland[1274]: kwin_wayland_drm: The main thread was hanging temporarily!
Mar 10 21:58:41 user firefox[10191]: Failed to create /home for shader cache (Permission denied)---disabling.
Mar 10 21:59:05 user kwin_wayland[1274]: kwin_wayland_drm: The main thread was hanging temporarily!
Mar 10 21:59:06 user firefox[10191]: Failed to create /home for shader cache (Permission denied)---disabling.
Mar 10 21:59:30 user kwin_wayland[1274]: kwin_wayland_drm: The main thread was hanging temporarily!
Mar 10 21:59:30 user kwin_wayland[1274]: kwin_wayland_drm: The main thread was hanging temporarily!
Mar 10 21:59:30 user kwin_wayland[1274]: kwin_wayland_drm: The main thread was hanging temporarily!
Mar 10 21:59:31 user firefox[10191]: Failed to create /home for shader cache (Permission denied)---disabling.
Mar 10 21:59:55 user kwin_wayland[1274]: kwin_wayland_drm: The main thread was hanging temporarily!
Mar 10 21:59:55 user kwin_wayland[1274]: kwin_wayland_drm: The main thread was hanging temporarily!
Mar 10 21:59:55 user kwin_wayland[1274]: kwin_wayland_drm: The main thread was hanging temporarily!
Mar 10 21:59:56 user firefox[10191]: Failed to create /home for shader cache (Permission denied)---disabling.
Mar 10 22:00:20 user kwin_wayland[1274]: kwin_wayland_drm: The main thread was hanging temporarily!
Mar 10 22:00:20 user kwin_wayland[1274]: kwin_wayland_drm: The main thread was hanging temporarily!
Mar 10 22:00:20 user kwin_wayland[1274]: kwin_wayland_drm: The main thread was hanging temporarily!
Mar 10 22:00:21 user firefox[10191]: Failed to create /home for shader cache (Permission denied)---disabling.
Mar 10 22:00:45 user kwin_wayland[1274]: kwin_wayland_drm: The main thread was hanging temporarily!
Mar 10 22:00:45 user kwin_wayland[1274]: kwin_wayland_drm: The main thread was hanging temporarily!
Mar 10 22:00:46 user firefox[10191]: Failed to create /home for shader cache (Permission denied)---disabling.
Mar 10 22:01:10 user kwin_wayland[1274]: kwin_wayland_drm: The main thread was hanging temporarily!
Mar 10 22:01:10 user kwin_wayland[1274]: kwin_wayland_drm: The main thread was hanging temporarily!
Mar 10 22:01:10 user systemd[1]: Starting Time & Date Service...
Mar 10 22:01:10 user systemd[1]: Started Time & Date Service.
Mar 10 22:01:16 user systemd[1212]: app-firefox@d438b040fb4e4db8b1a59713e860a58d.service: Consumed 14.651s CPU time, 804.4M memory peak.
Mar 10 22:01:35 user kwin_wayland[1274]: kwin_wayland_drm: The main thread was hanging temporarily!
Mar 10 22:01:38 user systemd[1212]: Started Konsole - Terminal.
Mar 10 22:01:38 user systemd[1212]: Started app-org.kde.konsole-11580.scope.

I also have a log for the entire day today, starting from the initial boot this morning, though it is quite long. The only other thing I can think to test now is doing a fresh boot, letting the monitors sleep without sleeping the entire system and seeing if that alone is enough to trigger this.

johnandmegh · March 12, 2025, 4:32am

This likely needs someone with more knowledge than I do for further help, but just to see if it narrows down the culprit - if you can get to a terminal or virtual console (Ctrl+Alt+F3, for example) while the issue is occurring, does running the command systemctl --user restart plasma-plasmashell.service unfreeze anything?

CorrectPoke · March 12, 2025, 11:08am

While the hitching is happening I can’t, as neither the mouse or keyboard respond to inputs. I did try preloading the command in terminal, forcing a freeze and alt-tabbing back to terminal and hitting enter to see if it would work, but only the alt-tab was registered when the freeze stopped. I restarted plasmashell anyways, but today was one of the times it would only hitch once and everything works again, so I can’t force a freeze again until later. That said, the power management section of system settings is still not loading so it seems the PC is still in it’s mood at the moment even though the hitching isn’t happening. Terminating the system settings app does actually generate a stack trace as the app crashes proper, but I’m still unclear how related the two issues are for now.

I did consider heading to the bug tracker to file a report there, but the issues is still vague and I don’t know if my available info is enough to work with yet so I held off.

pingas12345 · March 15, 2025, 3:41pm

Hi all, this is happening to me as well. Ryzen 5 3600 and RX 5600 XT.

I’ve noticed this occurring after sleep and will affect things like watching videos, middle clicking to scroll in Firefox and whenever a game is loaded. I can’t seem to find any leads from the errors I have gotten in journalctl as every search has lead to a dead end. I am replying because this is the only thread I have found that has described the issue almost exactly the same, bar the monitor resolution issues. I would much appreciate the help.

Stefan2 · March 16, 2025, 12:56pm

I’m having a very similar problem. My laptop gets into that state after being resumed from sleep and/or running for some time (not sure exactly what triggers it). Once it is in that state, I can reproduce a 20-30 seconds freeze by resuming a Youtube video that had been paused for a while.

This is usually accompanied by this log entry:

vivaldi-stable[250852]: [250848:250874:0315/140415.988459:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.PowerManagement.Inhibit.Inhibit: object_path= /org/freedesktop/PowerManagement/Inhibit: org.freedesktop.D
Bus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

For me, restarting (only) powerdevil heals the problem (no idea why). Maybe you could try

systemctl --user restart plasma-powerdevil

next time you’re in that state.

CorrectPoke · March 16, 2025, 3:10pm

So for the past few days I have not had any issues, and the only thing I’m doing differently as of now is that I just disabled the ability for the PC to turn off the monitors after inactivity. After multiple sleep/wake cycles there has been no freezing or other oddities. I obviously can’t say for certain it won’t happen again, but as of now I am more confident the issue seems to be something with the power monitor instead of only being a sleep issue. Which is what I have been suspicious about the entire time due to the mentioned issues with the power menu in system settings refusing to work once this is triggered. I will have to re-enable monitor power saving settings to see if it starts again so I can report back, but I’ll give it a little more time to see if I can still trigger it by sleep alone. Being you are on a laptop I assume something similar is happening with the monitors being ‘disconnected’ whenever the lid is closed, but I don’t know how that behavior works as I don’t mess with laptops often. Out of curiosity, are you on all AMD hardware too? As mentioned above this may be an issue with some AMD drivers that might get fixed in kernel 6.14.

As a side note, I’ve been running my secondary monitors both on a HDMI>DVI adapter and have not seen the resolution issued I mentioned in the first post since. It’s possible these monitors have some internal issues when being driven over DP, as I know DP ports have some differences in handling power compared to other plugs. But this is still something specific to either linux or the GPU as they never did this on Windows when I was using them there.

Stefan2 · March 16, 2025, 3:55pm

I’m on Intel (processor and integrated graphics).

I have 2 4k monitors connected to my laptop, and have had issues like the 640x480 in the past with different laptops and different Linux installs. I’ve also had bad experiences with not being able to resume sessions when going to sleep with the monitors connected, so I don’t do that anymore.

The 20-30 second freezes are new.

By the way, the “main thread was hanging temporarily” is quite related to the “pageflip error”, as you can see in the source code of kwin, which I’m for some reason not allowed to link. It seems like “main thread was hanging temporarily” is what you get when the pageflip is delayed for a bit.

XuChe · March 19, 2025, 7:29am

I also have a similar problem, mainly desktop freezes and stutters. My laptop is equipped with an Intel integrated graphics card and an NVIDIA discrete graphics card. Interestingly, I encounter freezes whether I enable dual-graphics mode in the BIOS (in which case KWin runs on the Intel iGPU) or enable only the NVIDIA dGPU. But I haven’t encountered the display resolution issues mentioned by others.

I’m not entirely sure if this is completely related to resuming from sleep. But I found this problem might be related to the driver in use. When I disable the Intel iGPU and use the nouveau driver, I experience freezes; but when I similarly disable the Intel iGPU and switch to the nvidia-open-dkms driver, the freezing problem disappears.

Here are some logs from my computer, I’m not sure if they are all related to this error:

kwin_wayland[1261]: kwin_core: Cannot grant a token to KWin::ClientConnection(0x6400c501ca80)
kwin_wayland[1261]: kwin_wayland_drm: The main thread was hanging temporarily!
kwin_wayland[1261]: kwin_scene_opengl: 0x3: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
kwin_wayland[1261]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11
kwin_wayland_wrapper[1368]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!
kwin_wayland_wrapper[485666]: The XKEYBOARD keymap compiler (xkbcomp) reports:
kwin_wayland_wrapper[485666]: > Warning:          Could not resolve keysym XF86RefreshRateToggle
kwin_wayland_wrapper[485666]: > Warning:          Could not resolve keysym XF86Accessibility
kwin_wayland_wrapper[485666]: > Warning:          Could not resolve keysym XF86DoNotDisturb
kwin_wayland_wrapper[485666]: Errors from xkbcomp are not fatal to the X server
kwin_scene_opengl: 0x3: GL_INVALID_VALUE in glTexStorage2D(width, height or depth < 1)
kwin_wayland[1261]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
kwin_wayland[1261]: kwin_scene_opengl: 0x3: GL_INVALID_OPERATION in glBindFramebuffer(non-gen name)
kwin_wayland[1261]: kwin_scene_opengl: 0x3: GL_INVALID_FRAMEBUFFER_OPERATION in glClear(incomplete framebuffer)
kwin_wayland[1261]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11

pingas12345 · March 19, 2025, 8:46am

systemctl --user restart plasma-powerdevil

Seems to fix the issue whenever waking up from sleep, thanks for that! Don’t wanna do this every time the PC wakes from sleep, so hopefully there’s a permanent solution with the next kernel update.

Stefan2 · March 22, 2025, 7:36am

In my case, the problem with powerdevil was connected to a bug in libddcutil. The developer already fixed it, but no idea how long it will take until a new version is released and makes it into the distributions.

You can use powerdevil without libddcutil by starting it with the environment variable POWERDEVIL_NO_DDCUTIL=1. It is explained in the README.md of the powerdevil repository. (Are links disallowed in general or only for me?) I haven’t tried it, but I guess the only thing you lose is the ability to control the brightness of external monitors through plasma.

CorrectPoke · March 22, 2025, 12:57pm

Just to make sure, are you running on Wayland as well? I’ve had a similar thought before, but some of the docs for powerdevil mention that while it does handle monitor poweroff functions, when running Wayland some of those tasks are handled by KWin instead. Mentioned here. I want to make sure that I’m testing the right thing before I make any changes to powerdevil configs. If you haven’t done it yet I’m willing to try myself, but if powerdevil isn’t actually handling these functions in Wayland I don’t have hopes for it working.

FYI, not being able to post links is a userclass limit here. I bumped into the same thing earlier when posting some of those logs as they had URLs in them (I think Steam was checking for updates?) For anyone else reading here I believe you were talking about this section of the Readme.

It’s been nearly a week since I checked in last, and I can even more confidently say that the freezing issues are not caused by sleep alone. No hitching to be had despite many sleep/wake cycles of various durations for the past week+. In fact, the only issue I currently have is related to desktop icons wandering around, which I’ll need to look into more threads for help, or make one myself. Though not being able to turn monitors off after inactivity is not ideal, so I’ll re-enable that to see if it was fixed in a random update, or start testing a couple things posted here to see if they work if it wasn’t.

Stefan2 · March 22, 2025, 1:55pm

Yes, I’m on Wayland.

The “systemctl --user restart plasma-powerdevil” doesn’t make any changes to the config. You should try that first. If you’re in a state where you can reproduce freezes and restarting powerdevil doesn’t fix it, you don’t have the same problem as me, and there is no point in changing the config.

In my case, the main thread of powerdevil just went into an infinite loop sometimes after waking up from sleep, which in a mysterious way caused the freezes. I found out by attaching a debugger to powerdevil. I still have the backtrace in case anyone needs it.

lands · March 22, 2025, 9:14pm

i’m seeing alot of errors similar to this in my journal, and kde has also been occasionally segfaulting after locking. i made a post about this Plasmashell segfault - #4 by lands and also found this [SOVLED]log into the KDE desktop(wayland), plasmashell... crashes / Applications & Desktop Environments / Arch Linux Forums which sounds like the same issue i’m having. really annoyed, i just want my laptop to work

LeafOfLuthien2276 · March 24, 2025, 5:42am

Just registered to throw my hat in, too.

I’ve noticed very similar issues starting after an update early last week (around March 16). I don’t sleep my computer, only lock, and sometimes manually, but most of the time automatically. Freezing also ALWAYS happens after manually turning Night Light on or off, or by adjusting the color temp. The only recovery for the Night Light issue is a full reboot.

Issues are:

Freezing when middle clicking on Firefox. Freezing when launching apps like games and Discord. Freezing when turning Night Light on or off. All of these freezes can last between 1 minute to whenever I run out of patience. The mouse is still active and I can move it between the second monitor and main one. I can also alt-tab to windows on the main monitor and then hot-key move it to the other one. Clicking on Power Management in settings locks up the Settings window only (but, not if the freezing was done forcefully by manipulating Night Light).

A full reboot fixes these issues until whatever triggers them happens again.

Previously and currently, my power settings are:

“killall Discord” is there because Discord still doesn’t send notifs to my cell after being idle and this is my work around. When I notice the freezing happening after unlocking my computer over night, I also notice that this command wasn’t ever sent because Discord was still active when unlocking the computer.

Turning off screen locking and Night Light has completely avoided these issues for the last two nights. I still allow Power Management to turn my monitors off without affect.

I think that the problem exists between Night Light and screen locking, but I’m also still very new to Linux and I’m not sure where to poke at things.

LeafOfLuthien2276 · March 24, 2025, 5:42am

I forgot to post my specs!

OS: EndeavourOS x86_64
Display (DELD10F): 2560x1440 @ 165 Hz in 31" [External] *
Display (GN246HL): 1920x1080 @ 60 Hz in 24" [External]
DE: KDE Plasma 6.3.3
CPU: AMD Ryzen 7 5800X (16) @ 4.85 GHz
GPU: NVIDIA GeForce RTX 3080 Ti [Discrete]

LeafOfLuthien2276 · March 26, 2025, 5:28pm

In another thread called “My entire monitor freezes when I adjust the temperature slider” (check my Post History for it. I can’t post links yet), I was asked to turn off Night Light completely while still locking my computer.

I did so and I have no issues at the moment.

Is anyone else running Night Light in this thread?

CorrectPoke · March 26, 2025, 9:18pm

I am using night light settings.

I’d give disabling it a try, except I actually haven’t been able to trigger the freezes at all since re-enabling screen locking after my last post. No crashes in the power settings, no hitching when watching videos in a browser either. It appears that a random update actually did fix something, and I’m kinda kicking myself for not keeping a log of when I ran updates and what packages got changed.

I did find this thread while searching for something else, and I believe it’s what Stefan2 was talking about earlier. It very much looks similar to my original issue, and says it will be fixed in ddcutil 2.2.1, but I’m currently on 2.2.0 released before I even installed this system. My intuition (which isn’t worth much here) says that this may be more the core of what my issues were, but without knowing which packages were updated recently I can’t say which update actually fixed the issue, if it’s even fixed at all. It may still be present but I just can’t trigger it as easily as before.

Unfortunately, until I can start reproducing the freezes I won’t be much help in testing for anyone else having the same issue. The only thing other than updates that is different for me since the issue started is I set the display to never dim, turn off after 15 min or 1 min when locked. Auto lock has been set to 10 minutes since the start. Night light has been on the whole time.