Created attachment 195526 [details] Kernel journal from the previous boot DESCRIPTION KWin 6.7.4 intermittently crashes with SIGSEGV on Fedora 44 using NVIDIA driver 610.57.04 and a Wayland session. STEPS TO REPRODUCE I have not yet found a 100% reproducible sequence of actions. The issue occurs during normal desktop use under KDE Wayland, specfically while I was playing Counter-Strike 2 without proton (native), with custom args: "SDL_VIDEO_DRIVER=wayland -w 2560 -h 1440" OBSERVED RESULT KWin crashes and generates a core dump. - The core dump reports that Program terminated with signal SIGSEGV, Segmentation fault. - The crashed process is /usr/bin/kwin_wayland - The available core dump currently does not contain a useful resolved frame stack beyond the crashing thread, despite debug information being downloaded. EXPECTED RESULT KWin should remain running and continue compositing the Wayland session. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 44 Qt Version: 6.11.1-1 Kernel: 7.1.10-200 Desktop: KDE Plasma KWin: 6.7.4 KDE Plasma Version: 6.7.4 KDE Frameworks Version: 6.29.0 Session: Wayland GPU: NVIDIA GeForce RTX 3060 Ti NVIDIA driver: 610.57.04 KMD version: 610.57.04 KWin is running on the 3060ti GPU and nvidia-drm is used for the display. ADDITIONAL INFORMATION nvidia-smi reports: GPU: NVIDIA GeForce RTX 3060 Ti Driver Version: 610.57.04 KMD Version: 610.57.04 Display Active: Yes KWin is listed as a GPU process. At the time of investigation, dmesg did not show an NVIDIA Xid error associated with this particular crash. Relevant journal output immediately before/around the crash contains no obvious pageflip/Xid error in the excerpt I currently have. I can provide the complete KWin core/backtrace, journal, and NVIDIA bug report if required. This does not appear to be an isolated configuration issue, because a very simillar issue has been reported with: - Fedora 44 - KDE Plasma / KWin 6.7.4 - Wayland - NVIDIA 610.57.04 - multiple DisplayPort monitors There are also reports of "Pageflip timed out!" / nvidia-drm failures continuing on NVIDIA 610.57.04 with KDE Wayland. My configuration differs from those reports in some details, including GPU model and refresh rate, but the software stack is closely related.
Created attachment 195527 [details] Full GDB backtrace from the KWin crash, including all threads, registers and local variables.
Created attachment 195528 [details] NVIDIA bug report
Created attachment 195529 [details] KWin user journal from the previous boot, covering the crash
Created attachment 195530 [details] Hardware and software configuration summary generated with inxi
I'm relatively confident your crash is caused by a GPU reset, and should be fixed with https://invent.kde.org/plasma/kwin/-/commit/067646a4571a9e75d6cf5bfb64df796c29a79fcb in 6.7.5 If you see it again then, just reopen this with a new backtrace
*** Bug 524325 has been marked as a duplicate of this bug. ***
*** Bug 523771 has been marked as a duplicate of this bug. ***
*** Bug 525354 has been marked as a duplicate of this bug. ***
*** Bug 526342 has been marked as a duplicate of this bug. ***
There's another case where we're missing makeCurrent entirely, rather than just the check if it was successful.
A possibly relevant merge request was started @ https://invent.kde.org/plasma/kwin/-/merge_requests/10003
Git commit ad655ed764a61995776abd6b59d98cec1814531f by Vlad Zahorodnii, on behalf of Xaver Hugl. Committed on 01/10/2026 at 06:19. Pushed by vladz into branch 'master'. plugins/screenshot: make the context current after prePaint prePaint can change the context, and changing it back can fail. The compositor doesn't hit this issue because it calls beginFrame on the layer after prePaint, which makes the context current as well. M +3 -0 src/plugins/screenshot/screenshot.cpp https://invent.kde.org/plasma/kwin/-/commit/ad655ed764a61995776abd6b59d98cec1814531f
Git commit 0e062dad8b206cf830ce1432d4aeeb850b23abc4 by Vlad Zahorodnii. Committed on 01/10/2026 at 06:41. Pushed by vladz into branch 'Plasma/6.7'. plugins/screenshot: make the context current after prePaint prePaint can change the context, and changing it back can fail. The compositor doesn't hit this issue because it calls beginFrame on the layer after prePaint, which makes the context current as well. (cherry picked from commit 3f13a0b86fbc2782e6036b811a52c3a484a3ad62) Co-authored-by: Xaver Hugl <xaver.hugl@kde.org> M +3 -0 src/plugins/screenshot/screenshot.cpp https://invent.kde.org/plasma/kwin/-/commit/0e062dad8b206cf830ce1432d4aeeb850b23abc4
Git commit 785a9e6aff5099d671190cd83574b73045888337 by Vlad Zahorodnii. Committed on 01/10/2026 at 07:28. Pushed by vladz into branch 'Plasma/6.8'. plugins/screenshot: make the context current after prePaint prePaint can change the context, and changing it back can fail. The compositor doesn't hit this issue because it calls beginFrame on the layer after prePaint, which makes the context current as well. (cherry picked from commit ad655ed764a61995776abd6b59d98cec1814531f) Co-authored-by: Xaver Hugl <xaver.hugl@kde.org> M +3 -0 src/plugins/screenshot/screenshot.cpp https://invent.kde.org/plasma/kwin/-/commit/785a9e6aff5099d671190cd83574b73045888337
Git commit 3d4845a2f1e4627dadfba1b18211e218581b6829 by Vlad Zahorodnii. Committed on 07/10/2026 at 10:17. Pushed by vladz into branch 'Plasma/6.6'. plugins/screenshot: make the context current after prePaint prePaint can change the context, and changing it back can fail. The compositor doesn't hit this issue because it calls beginFrame on the layer after prePaint, which makes the context current as well. (cherry picked from commit ad655ed764a61995776abd6b59d98cec1814531f) Co-authored-by: Xaver Hugl <xaver.hugl@kde.org> M +3 -0 src/plugins/screenshot/screenshot.cpp https://invent.kde.org/plasma/kwin/-/commit/3d4845a2f1e4627dadfba1b18211e218581b6829