Panel's randomly freeze on wake from sleep since 6.6 update

Help
,
1

Hey folks,

I’ve been struggling with troubleshooting an issue which originated after upgrading to 6.6. Most of the time when I wake the system from sleep everything is fine, but about 1/5 to 1/10 of those wakes results in various panels in KDE being frozen. They’ll still respond to clicks by opening the relevant pop-up menu or application (besides the app launcher, which is pretty much totally stuck once it’s frozen) but the image on the panel itself won’t update. Most of the time I pick up on this when I notice the clock I have on a panel along the top of my screen stops matching my other clocks, though I do see this failure occur where that element is fine and others are frozen instead.

I’m running Arch with Nvidia & Wayland. I did try the items listed under section 10 on this wiki, as in manually enabling/setting those too but that didn’t change anything (not surprised, I think it would have already been set correctly, but worth a shot). NVIDIA/Tips and tricks - ArchWiki

Looking at the logs there hasn’t been a true smoking gun that’s present both when this failure occurs and when it doesn’t, though I could totally be missing something. Here are some common log entries I’ve found that look potentially related to this problem but can’t say for sure given lack of expertise and success correcting on my own:

repeated kwin_wayland[1541]: Failed to open drm node: "/dev/dri/card0" entries appearing right after wake from sleep.

I disabled my integrated AMD GPU in the BIOS after this, thinking there might be a conflict between GPUs. No dice.

[drm:__nv_drm_semsurf_wait_fence_work_cb [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to register auto-value-update on pre-wait value for sync FD semaphore surface

This one appears in logs most often with this error but also appears when it’s not present as an issue.

This one looked suspicious at first too but the more I’ve dug I can’t find a resolution that makes it disappear, and it appears both when the issue is present and when it isn’t:

Feb 28 12:12:54 archlinux kwin_wayland[1541]: Atomic modeset test failed! Permission denied
Feb 28 12:12:54 archlinux kwin_wayland[1541]: Applying output configuration failed!

I’ve tried adding a couple of groups to my user record too which did nothing (video in particular).

At this point I’m really out of things to try on my own. Any ideas what might be happening? Is this just a bug and needs to be reported to the devs?

Similar issues:

This bug sounds very similar to what I’m dealing with but indicates it ought to have been solved by the existing updates to Arch which I’ve validated my system is using.

Thanks to any kind souls who read this!

2

Can confirm this occurs on a new user on my machine as well.

3

what does swapon say?

4

NAME TYPE SIZE USED PRIO
/dev/zram0 partition 31G 1.6G 100

5

are you using zram or a real partition?

6

Should be zram:

NAME ALGORITHM DISKSIZE DATA COMPR TOTAL STREAMS MOUNTPOINT
/dev/zram0 zstd 31G 1.6G 451.5M 523.1M [SWAP]

7

i would try with just a regular swap file.

zram does not play well with suspend/resume.

8

Interesting. Do you have any links to information on the topic that I could read up on? We exclusively rely on zram in KDE Linux so it’s a topic I try to keep an eye on.

9

i don’t use zram, but my understanding is that keeps everything in ram unless you set it to dump certain pages to disk such as discussed here

depending on your h/w, firmware and suspend settings in both systemd and plasma you could find yourself in a situation where RAM is trying to be written to RAM for safe keeping before it is powered off.

this would result in corruption of the file and when read back may produce unexpected results.

10

Super great information in that thread; thanks for linking it! I learned some things.