| Summary: | kwin_wayland crashed | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Lyubomir <liubomirwm> |
| Component: | wayland-generic | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | kfm-devel, nate |
| Priority: | NOR | ||
| Version: | 5.21.90 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | dolphin.gdb | ||
|
Description
Lyubomir
2021-06-03 15:22:19 UTC
Created attachment 138981 [details]
dolphin.gdb
The crash log only tells us that KWin crashed; sadly it's a known and unavoidable issue that when kwin_wayland crashes, all apps crash too (see https://bugreports.qt.io/browse/QTBUG-85631). The app crash logs are not useful; all they do is tell us that KWin crashed. But we need to know why KWin crashed. For that, we need a backtrace of the KWin crash itself. You may be able to retrieve it with `coredumpctl`. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl My memory betrays me, but judging from the plain stupid comment i made ("Attaching stacktrace from forced SIGSEGV") i guess i manually send signal 11 using htop to the process and that should be why it crashed.
If this is the case it might be because it had high CPU usage after login, but i don't remember if that was the case or if it was really a crash unprovoked by me. I doubt it judging by the comment.
Just installed systemd-coredump over apport. It shows many crashes, all of which "missing" corefiles. It seems this bug would be a no-op. That said can apport be used for invoking gdb (and if so updating KDE documentation) instead of coredumpctl, as apport would report to Canonical in case of Ubuntu crash. Looks like conflict of interest for bug info between KDE and Canonical. Sorry for the spam, just fount out one can apport-unpack the crash report and gdb the coredump afterwards. I suggest including such apport instructions here: 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! 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! |