With Fedora 42 (especially kernel 6.15.10), kwin dumps core when resuming from suspend

With kernel version 6.15.10 on Fedora 42, I’ve had several crashes where, after resuming from suspend, kwin dumps core and all my windows have died.

This doesn’t happen on every resume, but often enough to be a problem. (I think I’ve had it 4 times in the last couple of days.)

When I switch back to booting from kernel 6.15.9, I don’t get the issue. So I’ll just boot from that kernel for now, but of course it would be good to work out what is broken and how to fix it.

Has anyone else seen similar crashes on 6.15.10 (on Fedora or any other distro)? This might narrow down what is causing it. I’m using an NVidia 3060 Ti with the open-kernel drivers, and dual monitors, so I wonder if one or both of those things is relevant.

Plasma version 6.4.4, Frameworks 6.17.0, Qt 6.9.1.

Fuller log available here. Here I’ll just post the top of the stack trace:

Aug 24 09:50:12 systemd-coredump[6648]: Process 2542 (kwin_wayland) of user 1000 dumped core.

                                        Module /usr/bin/kwin_wayland from rpm kwin-6.4.4-2.fc42.x86_64
                                        Module libspa-videoconvert.so from rpm pipewire-1.4.7-1.fc42.x86_64
                                        Module kimg_rgb.so from rpm kf6-kimageformats-6.17.0-1.fc42.x86_64
                                        Module kimg_sct.so from rpm kf6-kimageformats-6.17.0-1.fc42.x86_64
                                        Module libqwbmp.so from rpm qt6-qtimageformats-6.9.1-1.fc42.x86_64
                                        Module libjasper.so.7 from rpm jasper-4.2.3-3.fc42.x86_64
                                        Module libraw.so.23 from rpm LibRaw-0.21.4-1.fc42.x86_64
                                        Module kimg_raw.so from rpm kf6-kimageformats-6.17.0-1.fc42.x86_64
                                        Module libjxl_cms.so.0.11 from rpm jpegxl-0.11.1-4.fc42.x86_64
                                        Module libjxl_threads.so.0.11 from rpm jpegxl-0.11.1-4.fc42.x86_64
                                        Module libjxl.so.0.11 from rpm jpegxl-0.11.1-4.fc42.x86_64

Cross-reference to Fedora forum post: Kwin dumps core when resuming from suspend (seems worse on 6.15.10) - Fedora Discussion

Update: I’ve now observed this once with kernel 6.15.9 (in several days of usage, so much lower frequency than 6.15.10).

Stack trace at kwin crash on kernel 6.15.9 - Pastebin Service

Some highlights:

Aug 26 15:58:29 kwin_wayland[2524]: kwin_scene_opengl: Could not delete texture because no context is current
Aug 26 15:58:29 kwin_wayland[2524]: kwin_scene_opengl: Could not delete framebuffer because no context is current
Aug 26 15:58:29 kwin_wayland[2524]: kwin_scene_opengl: Could not delete texture because no context is current
Aug 26 15:58:29 kwin_wayland[2524]: kwin_scene_opengl: Could not delete vertex buffer because no context is current
Aug 26 15:58:29 kwin_wayland[2524]: kwin_scene_opengl: Could not delete texture because no context is current
Aug 26 15:58:31 kwin_wayland[2524]: No QSGTexture provided from updateSampledImage(). This is wrong.
Aug 26 15:58:31 kwin_wayland[2524]: No QSGTexture provided from updateSampledImage(). This is wrong.
Aug 26 15:58:31 kwin_wayland[2524]: kwin_xwl: Could not find a matching X RandR CRTC/output to set as primary for KWin::DrmOutput(0x559da67477f0, name="DP-2", geometry=QRect(0,0 1920x1080), scale=1)
Aug 26 15:58:31 kwin_wayland[2524]: kwin_xwl: Could not find a matching X RandR CRTC/output to set as primary for KWin::DrmOutput(0x559da67477f0, name="DP-2", geometry=QRect(0,0 1920x1080), scale=1)
Aug 26 15:58:31 kwin_wayland[2524]: kwin_xwl: Could not find a matching X RandR CRTC/output to set as primary for KWin::DrmOutput(0x559da67477f0, name="DP-2", geometry=QRect(0,0 1920x1080), scale=1)
Aug 26 15:58:31 kwin_wayland[2524]: kwin_xwl: Could not find a matching X RandR CRTC/output to set as primary for KWin::DrmOutput(0x559da67477f0, name="DP-2", geometry=QRect(0,0 1920x1080), scale=1)
Aug 26 15:58:31 kwin_wayland_wrapper[2524]: KCrash: Application 'kwin_wayland' crashing... crashRecursionCounter = 2
Aug 26 15:58:32 systemd-coredump[62847]: Process 2524 (kwin_wayland) of user 1000 dumped core.
                                         
                                         Module /usr/bin/kwin_wayland from rpm kwin-6.4.4-2.fc42.x86_64
                                         Module KirigamiPlasmaStyle.so from rpm libplasma-6.4.4-1.fc42.x86_64
                                         Module kimg_rgb.so from rpm kf6-kimageformats-6.17.0-1.fc42.x86_64
                                         Module kimg_sct.so from rpm kf6-kimageformats-6.17.0-1.fc42.x86_64
                                         Module libqwbmp.so from rpm qt6-qtimageformats-6.9.1-1.fc42.x86_64

Hi, your full log page is in 404. Do you have unofficial widgets? I found them to be in my logs reasons for certain crashes ; I check the logs in reverse after a crash with journalctl -r /usr/bin/plasmashell or

journalctl --user -u plasma-plasmashell.service \

-S ‘2025-06-23 14:13’ -U ‘2025-06-23 14:19’

Thank you for looking!

I reuploaded the first logs, they should be visible now.

I don’t have any unofficial widgets. I have a panel using only Plasma standard widgets, and nothing else (no desktop widgets, desktop folder view etc).

Actually, I wonder whether this could be wallpaper-related - I have a JPG as wallpaper and I notice kimageformats and qtimageformats in the stack trace…

Also both crashes have something like this:

Aug 26 15:58:31 plasmashell[2680]: kde.plasmashell: requesting unexisting screen available rect -1
Aug 26 15:58:31 plasmashell[2680]: kf.plasma.quick: Exposed with no visual parent. Window positioning broken.

which makes me wonder about something GPU driver related, although I haven’t changed the NVidia driver version particularly recently (not since well before this started).

Have you tried with another theme, do you use a virtual desktop option? Have you tried without. If I am not wrong -1 is the default window position on Linux. Sorry I can’t really help any further but your error message has several thread in google.

This may be not relevant after I read your last answer :slight_smile: : I am not a hardware specialist on linux but seeing your logs before the crash, opengl seems involved. On Windows I remember that you could either select your graphic card either your cpu to manage your graphic environement, maybe doing so could help you finding the culprit and then open a thread at bug.kde.org with your system’s information or opening the bug at your gpu provider if you see it happening on multiple bug system

1 Like

I don’t use virtual desktops, but theme is a good point.

When I have a little time I’ll switch back to 6.15.10 (which provokes the crash more easily) and experiment with theme and wallpaper settings.

Thanks again!

1 Like

You’re welcome, since you are friendly and on kde I will share with you my most important IT secret for increased productivity : keep alt+tab for toggling through all you apps but assign F1 to access the previous used tab. Really, this is my favorite KDE feature :grinning_face_with_smiling_eyes:

2 Likes

I’m pretty sure this was wallpaper-related.

Instead of my JPG desktop wallpaper, I switched to a solid colour. That almost eliminated the crashes, even on 6.15.10.

I did have one crash, this time when the system was trying to sleep (rather than resuming from sleep). Then I switched the lockscreen wallpaper to a solid colour too. Since then (nearly 2 days of usage), I haven’t had a crash at all.

The question is still - why?!

It must be a rare situation since I haven’t seen any other posts about it, and it’s not like I’m the only person to use JPG wallpapers. It didn’t happen before kernel 6.15.9, even with the version of the NVIDIA drivers I’m currently using.

I guess it’s some kind of interaction between the kernel and the drivers that means painting the screen sometimes fails when entering or leaving sleep. (Loose terminology, I don’t know enough about the video drivers to be more specific.) Multiple monitors may have a role too.
Certainly NVIDIA cards can be unreliable in resuming from sleep properly (not only a Linux issue, I had it on Windows too), but no one else seems to have reported exactly this behaviour.

Kernel 6.16.3 is available now in Fedora, so I’ll upgrade to that and see if I can safely bring the wallpaper back.

1 Like

I think it is a sign from the universe to tell you not to use wallpapers. :grinning_face_with_smiling_eyes:

Honesly I’ve been using a plain color between grey and black for the past few years and can’t live without it. It attracts also less attention when you use your pc in public places(except for the fact that I am programming on Linux and using a stylish Yakuake CLI terminal :slight_smile: )

But hey, happy you found the root cause. Good luck with 6.16.3 maybe it will be solved. I always check reddit.com/r/fedora before I make an upgrade though, but normall x.xx.+2 are safe, anything major or right after a major upgrade I watch out.

1 Like

Unfortunately I did have the problem in 6.16.3 when I brought my wallpaper back.

Also, 6.16.2 and 6.16.3 have some networking issues (UDP broadcast broken on 6.16.2 / Kernel & Hardware / Arch Linux Forums). Arch has patched the kernel for these but Fedora hasn’t yet.

So for now I’m back on 6.15.10 with plain backgrounds. At least I can change the shade to match my mood :slight_smile:

I might see if PNG instead of JPG makes a difference.

1 Like

well, if some other people have the issue, they will come back here, maybe you can remove the “solved” tag.

You may for the moment become very creative with your icons placement to make it very unique/personal wallpaper :grin:

1 Like

Just wanted to pop in and say I’m also experiencing this when using image wallpapers. I also have an Nvidia card. Here’s some system info:

Operating System: Fedora Linux 42
KDE Plasma Version: 6.4.4
KDE Frameworks Version: 6.17.0
Qt Version: 6.9.1
Kernel Version: 6.16.3-200.fc42.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × AMD Ryzen 9 9950X3D 16-Core Processor
Memory: 64 GiB of RAM (62.3 GiB usable)
Graphics Processor: NVIDIA GeForce RTX 3080
Manufacturer: Micro-Star International Co., Ltd.
Product Name: MS-7E51
System Version: 1.0

1 Like

Through some combination of upgrades, this is no longer an issue. I have brought back my JPG wallpaper and don’t get the crashes anymore.

With kernel 6.16.7, Nvidia driver 580.82.09 and Plasma 6.4.4 and 6.4.5 everything works fine, though I’m not exactly sure what changed to make it so.

@Janooba do you still see the issue on your setup?