https://bugs.kde.org/show_bug.cgi?id=512990
Nate Graham <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] Resolution|--- |WAITINGFORINFO Status|REPORTED |NEEDSINFO --- Comment #2 from Nate Graham <[email protected]> --- 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! -- You are receiving this mail because: You are watching all bug changes.
