Created attachment 170739 [details] saved crash report SUMMARY STEPS TO REPRODUCE 1. Use the desktop as normal for few days 24h/d 2. (maybe?) do an update to newer version 3. Use the desktop as normal for some time OBSERVED RESULT Crash - killing all my ongoing work ! EXPECTED RESULT Even if Crashed - it should not crash any other app! SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 6.0.5 (updated to 6.1 without reboot) KDE Frameworks Version: ?? Qt Version: ?? ADDITIONAL INFORMATION the submit bug was not working even after clicking to "fetch diagnostic symbols", that only proves that once again kwin_wayland is not production ready... (kwin_x11 did actually recover just fine without losing a session ...)
Blocking sending request because "Data from crash report are not helpful" is also ... just bad, unless the signal that it did crash was reported somewhere, but I doubt as that would say data is leaked without user knowledge. Why? Because the desktop could crash for a lot of people and non would be wiser...
It most likely related to the OS Update, but if so, it should tell the user that "reboot advices or it might crash", but better ... fix that it will not crash, or even if it crashes it would not take down everything with it ...
The information you provided isn't useful, because the binary and debug information is for 6.1 and the running instance was 6.0. We need a proper backtrace, without it this is not actionable.
(In reply to Zamundaaa from comment #3) > The information you provided isn't useful, because the binary and debug > information is for 6.1 and the running instance was 6.0. We need a proper > backtrace, without it this is not actionable. That was the whole point of this PR, to make is useful in the future if this happen again (and I can guess that it will). Because the crash handler UI that showed was useless in this case, as it did downloaded debugging symboles but looks like wrong ones. What can be done to make it useful? Some manual work can be done to get more data from that crash or to prepare for the next one? Or maybe something could be done to improve the crash UI to help with similar crashes after update in the future?
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!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone!