Created attachment 144616 [details] The Backtrace SUMMARY Sometimes, when I close an application Plasma will crash and restart. I don't know why it does this and it doesn't happen often. STEPS TO REPRODUCE 1. Close an open application using the applications titlebar 'close' button. OBSERVED RESULT Sometimes Plasma crashes and restarts after the application closes. EXPECTED RESULT The application closes and Plasma continues operating as normal. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed kernel 5.14.14-3-default KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION The particular application that I closed when this crash happened was Lutris, but this has happened to me before with other applications and other versions of KDE Plasma. Some details about my desktop layout: I have one plasma panel on the desktop, at the top of the screen. Arranged from left to right on it are the following applets: Application Launcher, Task Manager (not icons only), Global Menu, Panel Spacer, Color Picker, System Tray, and Digital Clock. I also have three Virtual Desktops, arranged in a single row, and only one Activity. There were four applications open visible in the Task Manager when the crash happened (including Lutris).
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: #7 0x00007f5fcc103537 in ?? () from /usr/lib64/qt5/plugins/plasma/scriptengines/plasma_appletscript_declarative.so #8 0x00007f5fcc10441e in ?? () from /usr/lib64/qt5/plugins/plasma/scriptengines/plasma_appletscript_declarative.so Could you please install debug symbols for plasma-framework, reproduce the crash, and attach a new symbolicated backtrace? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Thanks again!
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!
(In reply to Bug Janitor Service from comment #2) > 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 intended on providing the information needed, and I've installed the necessary packages for producing a useful backtrace, but I haven't been able to reproduce the crash since I reported it. Not being able to reproduce the bug is part of what makes bugs like this one frustrating to report/troubleshoot.
Since I haven't been able to reproduce the crash, and I can't provide more information because of that, I'm marking this bug as 'resolved'. But if it happens to me again (which I think it could, just don't know when) I'm going to reopen this bug providing more information. I try to make my bug reports useful, so if there's something I can do differently in my bug reports to aid in that, please let me know. With this particular bug, I just don't know how to add debug symbols to a backtrace after it's already been generated (or if that's possible).
You can install the debug symbol packages later and then load up the backtrace in gdb. That should work.