Summary: | kwin_wayland crashes | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | ltstarwarskid |
Component: | wayland-generic | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | nate |
Priority: | NOR | Keywords: | wayland |
Version: | 5.23.2 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
drkonqi crash report
kwin_wayland crash backtrace |
Description
ltstarwarskid
2021-10-27 15:37:21 UTC
> "The Wayland connection broke. Did the Wayland compositor die?") at global/qlogging.cpp:893 This means that KWin crashed; when this happens, all apps automatically crash too. Can you get a backtrace of the kwin_wayland crash? You may be able to retrieve it with the `coredumpctl` utility. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl Created attachment 143353 [details]
kwin_wayland crash backtrace
Here's what I believe to be the backtrace. I didn't have anything in the coredumpctl list, even with multiple repeats, so I had to follow the copy and paste instructions on how to attach GDB to kwin on wayland in the debugging community wiki page.
Hmm, not very helpful to my eyes, but maybe KWin developers can see something useful in it. No, the backtrace looks incomplete. How can the crash be reproduced? 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 Vlad Zahorodnii from comment #4) > No, the backtrace looks incomplete. How can the crash be reproduced? Just turn the monitor off then back on when running on Wayland in the bug originally linked. After the resulting plasmashell crash and recovery, click on the developer information tab or report bug button. At this point drkonqi will hang before crashing. 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! |