https://bugs.kde.org/show_bug.cgi?id=520099
TraceyC <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REPORTED |NEEDSINFO CC| |[email protected] Resolution|--- |BACKTRACE --- Comment #1 from TraceyC <[email protected]> --- Thanks for the report. The first thing we need to do is figure out if something is actually crashing, or if the clipboard is just freezing. If it's crashing, then there's a coredump and you can get a backtrace. If there's no coredump, there's actually no crash. You can check for coredumps in the Crashed Process Viewer. If there's a crash, we'll need a backtrace as mentioned in the issue template. If there isn't a coredump, we can still get useful information about the freeze. Can you try the steps outlined in https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_with_GDB ? Basically installing gdb, then running plasmashell inside gdb until the crash occurs. Sometimes this will help if no crash report/coredump is automatically generated. Thanks! -- You are receiving this mail because: You are watching all bug changes.
