SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Start KDE Plasma on X.org OBSERVED RESULT Kwin has crashed, there is a message in the compositor settings about an unstable driver (with a button to re-enable opengl detection, when I press it and change opengl version it starts kwin successfully) EXPECTED RESULT Kwin should not crash SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Yes (available in About System) KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Also happened to a youtuber on NVIDIA (https://youtu.be/OfGV-sHGUno?t=506) Intel iGPU I can't attach a backtrace because I'm currently on GNOME (sorry I know)
> I can't attach a backtrace because I'm currently on GNOME (sorry I know) Sure you can! :) The `coredumpctl` tool will show backtraces no matter which DE you're currently using. Can you use it to get a backtrace and attach it? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
I have been trying to reproduce this after a fresh install of Arch on my machine, and I cannot for the life of me reproduce it. It likely got fixed in the hundreds of kwin fixes in 5.24. Sorry. I'll report back with a backtrace if I ever reproduce it.
Thanks for the update.