https://bugs.kde.org/show_bug.cgi?id=521796
TraceyC <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] Resolution|--- |BACKTRACE Status|REPORTED |NEEDSINFO --- Comment #1 from TraceyC <[email protected]> --- Thanks for the crash report. As the message at the top of the summary says, if something crashed, we need a backtrace of it so we can figure out what's going on. We need the full backtrace, not just an excerpt or what's in the journal logs. I do see from the logs that you'll need to install debug packages, based on the n/a in these lines: #0 0x00007f2322f0981c n/a (libkwin.so.6 + 0x50981c) #4 0x00007f2322f13943 n/a (libkwin.so.6 + 0x513943) Could you please install debug packages 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 for details about how to do this. Thanks again! -- You are receiving this mail because: You are watching all bug changes.
