Summary: | kwin_wayland crashes after unplugging external USB-C monitor and closing the laptop lid | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Robert <robertdejager> |
Component: | wayland-generic | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | nate |
Priority: | NOR | ||
Version First Reported In: | 5.26.0 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 5.27 | |
Sentry Crash Report: |
Description
Robert
2022-11-24 12:48:08 UTC
I'm afraid I'm going to need some help with the backtrace. The instructions on the community page cover crashing applications. Can someone tell me what to run? Try `coredumpctl debug kwin_wayland`. Sorry for the late reaction. After your comment, I upgraded to plasma 5.26.4 before I could try to reproduce. Since then, it worked ok on my 1080p monitor at home. I tried a few times on the 4k monitor at work, also switched back and forth without issue. The last attempt produced the crash. Unfortunately, "coredumpctl debug kwin_wayland" resulted in a "No match found." 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! The issue still presents itself sometimes after reconnecting the external monitor. Does anyone have any idea how to extract some useful information after it happens? Hmm, that's hard to say if there's no crash log. Fortunately, a big multiscreen refactor landed in the upcoming Plasma 5.27. There's a good chance that work fixed this issue. Let's mark this bug as fixed, and if you still experience it after upgrading to Plasma 5.27, feel free to re-open it. Thanks a lot! Ok, I'll wait until 5.27 lands, and try to update this ticket then. Happy holidays. |