| Summary: | KDE randomly restarted when launching Audacity | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Christian Lampe <kontakt> |
| Component: | wayland-generic | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | carl, kontakt, nate, nicolas.fella |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | The crash handler windows in the window spread view. | ||
|
Description
Christian Lampe
2024-01-19 19:30:44 UTC
This means kwin_wayland has crashed. Please follow https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports to get a backtrace for kwin_wayland and paste it here. Thanks! 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! Created attachment 165728 [details]
The crash handler windows in the window spread view.
Well, I cannot get the stack trace as it seems to be a completely random crash, although I recently accidentally reproduced it on KDE 5.27 (from the Ubuntu jammy Backports repo). I tried to repeat it but it didn't crash again.
I dragged a .desktop file for PyCharm (I don't have the snap but the .tar.gz) onto the panel, it didn't appear in there. So I dragged it onto there two more times without it appearing. Then I launched PyCharm from the .desktop file in `nemo` and as soon as it appeared in the panel I right-clicked onto the icon to pin it, right when the window tried closing itself (because the first window only is a splash screen). The context menu started appearing, then the whole desktop locked up and restarted to the same flood of crash handler windows. See the newly-attached screenshots.
The only stack trace I got was the one attached in the initial comment under the [KCrash handler] section. I'm afraid we still need a kwin_wayland backtrace for this to be actionable. You may be able to use `coredumpctl` to get it; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl 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! As I have so far been unable to determine a reliable way to trigger the bug I'll mark this as "RESOLVED→WORKSFORME" now… I have seen a similar, reliably triggerable crash, but it manifests a little differently and doesn't seem to be related AFAIK. |