Created attachment 184169 [details] kcrash backtrace SUMMARY I’m experiencing a very persistent and reproducible crash of KWin on my machine. The crash occurs every time when I lock my session and allow the screens to enter standby while HDR is enabled for either monitor. It does not happen if the screens get turned off without the session being locked. It also does not happen when HDR is disabled for both monitors. When I later wake the system (not hibernating or suspend to ram) and the monitors turn back on, but before I log in, I hear the ping from KCrash. After logging in, normally KWin has already restarted, but all my running applications have crashed, and KCrash prompts me to submit a crash report. Sometimes KWin does not restart automatically, and I have to manually start it using "plasmashell --replace & disown". STEPS TO REPRODUCE 1. Lock the Session 2. Wait for the configured 1 min until my screens go to standby 3. Wake the system SOFTWARE/OS VERSIONS Linux: Arch linux Kernel: 6.16.1-2-cachyos KDE Plasma Version: 6.4.4 KDE Frameworks Version: 6.17.0 Qt Version: 6.9.1 Nvidia driver version: 580.76.05 ADDITIONAL INFORMATION I have 2 2560p x 1440p 120hz HDR monitors connected via Display Port. I’ve attached the backtrace provided by KCrash as well as what I believe is the relevant portion of the systemd journal.
Created attachment 184170 [details] relevant journald lines
Thank you for the bug report! Unfortunately the backtrace is incomplete and missing debug symbols for the following lines that we need to figure out exactly what's going wrong: #5 0x00007ff8207a7f3a n/a (libkwin.so.6 + 0x5a7f3a) #6 0x00007ff81bc133fe n/a (libffi.so.8 + 0x83fe) #7 0x00007ff81bc0fa5d n/a (libffi.so.8 + 0x4a5d) #8 0x00007ff81bc1278e ffi_call (libffi.so.8 + 0x778e) #9 0x00007ff81d18d240 n/a (libwayland-server.so.0 + 0x6240) #10 0x00007ff81d193374 n/a (libwayland-server.so.0 + 0xc374) Could you please install debug symbols and attach a new symbolicated backtrace generated by using `coredumpctl gdb` in a terminal window? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl for details about how to do this. Thanks again!
Created attachment 184266 [details] backtrace with all debug symbols Thanks for your quick reply. I have installed all the necessary debug symbols and provoked another crash.
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
*** This bug has been marked as a duplicate of bug 508765 ***