Created attachment 187370 [details] Coredump SUMMARY When I went to play a game of CS2's "wingman" mode, during freeze time I hit right shift key to chat in /all. Kwin then crashed instantly. STEPS TO REPRODUCE 1. Start CS2 2. Join a wingman match 3. During freeze time, hit right shift OBSERVED RESULT Kwin crashes. CS2 closes (but sound still present), so did discord and deezer. EXPECTED RESULT I can type in all chat. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon User Edition x86_64 / 6.14.0-36-generic KDE Plasma Version: Plasma 6.5.3 KDE Frameworks Version: 6.20.0 Qt Version: 6.10.1 ADDITIONAL INFORMATION Not sure if related, but of note: - I was split tunneling steam from Mullvad VPN (did so a lot, never had issues). - I haven't tried in a 5v5 match - Hitting right shift during loading screen or main menu does NOT crash KWIN.
Created attachment 187371 [details] Kwin gdb
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: #6 0x00007f0f86d33653 in QMessageLogger::fatal(char const*, ...) const () from /lib/x86_64-linux-gnu/libQt6Core.so.6 #7 0x00007f0f86d2107b in qt_assert_x(char const*, char const*, char const*, int) () from /lib/x86_64-linux-gnu/libQt6Core.so.6 #8 0x00007f0f893ccbf9 in ?? () from /lib/x86_64-linux-gnu/libkwin.so.6 #9 0x00007f0f893f5253 in ?? () from /lib/x86_64-linux-gnu/libkwin.so.6 Could you please install debug symbols and attach a new symbolicated backtrace generated by using `coredumpctl gdb [process that crashed]` 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!
(In reply to Nate Graham from comment #2) > 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: > > #6 0x00007f0f86d33653 in QMessageLogger::fatal(char const*, ...) const () > from /lib/x86_64-linux-gnu/libQt6Core.so.6 > #7 0x00007f0f86d2107b in qt_assert_x(char const*, char const*, char const*, > int) () from /lib/x86_64-linux-gnu/libQt6Core.so.6 > #8 0x00007f0f893ccbf9 in ?? () from /lib/x86_64-linux-gnu/libkwin.so.6 > #9 0x00007f0f893f5253 in ?? () from /lib/x86_64-linux-gnu/libkwin.so.6 > > Could you please install debug symbols and attach a new symbolicated > backtrace generated by using `coredumpctl gdb [process that crashed]` 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! Hi, I've tried looking around, and I followed the steps for kwin wayland here : https://community.kde.org/KWin/Debugging#Debug_KWin_with_GDB I run on KDE Neon, and it just says in here (https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Install_debugging_packages) "Neon has the debug symbols in its regular repository." So I am quite puzzled as to where to find the missing symbols
Just follow the specific instructions I provided.
(In reply to Nate Graham from comment #4) > Just follow the specific instructions I provided. Yes, that is exactly what I did. When doing a coredump --reverse to see which one I want, the kwin_wayland ones are inaccessible (see "kwin_inaccessible" attachement. I've tried to install the debug symbols by looking into the specific section of the same page you provided, which is where it says for KDE Neon (which I'm running) : "Neon has the debug symbols in its regular repository." I still tried "sudo coredumpctl gdb <PID>", then "bt" when "gdb" appears and I get this: > (gdb) bt > #0 0x000073982dc9eb2c in ?? () > #1 0x0000000000000000 in ?? () > (gdb) I don't think that helps much more. For reference, I've put the full terminal as a .txt in attachement too.
Created attachment 187580 [details] kwin_inaccessible
Created attachment 187581 [details] Full_terminal
🐛🧹 ⚠️ 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!