| Summary: | Power management crash at startup on Wayland | ||
|---|---|---|---|
| Product: | [Plasma] KScreen | Reporter: | Pietro F. Fontana <pietro.fontana> |
| Component: | libkscreen | Assignee: | kscreen-bugs-null <kscreen-bugs-null> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | crash | CC: | kde, magiblot, nate |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Pietro F. Fontana
2020-04-17 08:19:36 UTC
I would say the stack trace is the same as in bug 418730. It looks like a "The Wayland connection broke. Did the Wayland compositor die?" issue. There are other issues mentioning this: bug 378708 and bug 392376. But unfortunately it looks like it's not getting a lot of attention. #6 QMessageLogger::fatal (this=this@entry=0x7fffd70c5ba0, msg=msg@entry=0x7ff994ac00b8 "The Wayland connection broke. Did the Wayland compositor die?") at global/qlogging.cpp:893 This means that the compositor crashed. Due to a Qt issue, when this happens, the app using it will crash too. KDE developers submitted a fix, but sadly it was not merged. See https://codereview.qt-project.org/c/qt/qtwayland/+/308984. Until we get better handling of this in Qt, the best we can do is debug why the compositor crashed in the first place. So can you please get a backtrace of the crash in kwin_wayland and then file a new bug report with it on kwin | wayland-generic? Thanks! You may be able to use the `coredumpctl` utility to retrieve the backtrace. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl @nate: unfortunately, I don't use this system anymore and I cannot currently help in reproducing the issue. |