| Summary: | kwin crashes when enabling laptop screen | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Andrius Štikonas <andrius> |
| Component: | wayland-generic | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | normal | CC: | hein, kde, thuryn1 |
| Priority: | NOR | ||
| Version First Reported In: | 5.15.1 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Andrius Štikonas
2019-02-20 01:06:00 UTC
I can also see this in journalctl vas. 20 00:59:19 laptop kdeinit5[3778]: kscreen.kded: KScreen::Output( 2 "SAM HDMI-A-1-S24C300/808661304" connected enabled primary pos: QPoint(1920,0) res: QSize(-1, -1) modeId: "0" scale: 1 followPreferred> vas. 20 00:59:19 laptop kdeinit5[3778]: kscreen.kded: Change detected vas. 20 00:59:19 laptop kdeinit5[3778]: kscreen.kded: KScreen::Output( 1 "AUO eDP-1-unknown" connected disabled pos: QPoint(0,0) res: QSize(-1, -1) modeId: "0" scale: 1 followPreferredMode: false ) vas. 20 00:59:19 laptop kdeinit5[3778]: kscreen.kded: KScreen::Output( 2 "SAM HDMI-A-1-S24C300/808661304" connected enabled primary pos: QPoint(1920,0) res: QSize(-1, -1) modeId: "0" scale: 1 followPreferred> vas. 20 00:59:19 laptop kdeinit5[3778]: kscreen.kded: Change detected vas. 20 00:59:19 laptop kdeinit5[3778]: kscreen.kded: KScreen::Output( 1 "AUO eDP-1-unknown" connected disabled pos: QPoint(0,0) res: QSize(-1, -1) modeId: "0" scale: 1 followPreferredMode: false ) vas. 20 00:59:19 laptop kdeinit5[3778]: kscreen.kded: KScreen::Output( 2 "SAM HDMI-A-1-S24C300/808661304" connected enabled primary pos: QPoint(1920,0) res: QSize(-1, -1) modeId: "0" scale: 1 followPreferred> vas. 20 00:59:19 laptop kdeinit5[3778]: kscreen.kded: Change detected vas. 20 00:59:19 laptop kdeinit5[3778]: kscreen.kded: KScreen::Output( 1 "AUO eDP-1-unknown" connected disabled pos: QPoint(0,0) res: QSize(-1, -1) modeId: "0" scale: 1 followPreferredMode: false ) vas. 20 00:59:19 laptop kdeinit5[3778]: kscreen.kded: KScreen::Output( 2 "SAM HDMI-A-1-S24C300/808661304" connected enabled primary pos: QPoint(1920,0) res: QSize(-1, -1) modeId: "0" scale: 1 followPreferred> vas. 20 00:59:19 laptop kernel: traps: kwin_wayland[3739] general protection ip:7fe8e2ae4040 sp:7ffe3c050b60 error:0 in libQt5Core.so.5.12.1[7fe8e279f000+65f000] vas. 20 00:59:19 laptop systemd[1]: Started Process Core Dump (PID 5436/UID 0). vas. 20 00:59:20 laptop kdeinit5[3778]: kscreen.kded: Saving current config to file vas. 20 00:59:20 laptop kdeinit5[3778]: kscreen.kded: Config saved on: "/home/andrius/.local/share/kscreen/2c86d3716a57a3dfb9e034cabaced403" vas. 20 00:59:20 laptop kdeinit5[3778]: kscreen.kded: KScreen::Output( 1 "AUO eDP-1-unknown" connected disabled pos: QPoint(0,0) res: QSize(-1, -1) modeId: "0" scale: 1 followPreferredMode: false ) vas. 20 00:59:20 laptop kdeinit5[3778]: kscreen.kded: KScreen::Output( 2 "SAM HDMI-A-1-S24C300/808661304" connected enabled primary pos: QPoint(1920,0) res: QSize(-1, -1) modeId: "0" scale: 1 followPreferred> vas. 20 00:59:22 laptop konsole[5372]: The Wayland connection broke. Did the Wayland compositor die? vas. 20 00:59:22 laptop systemsettings5[5308]: The Wayland connection broke. Did the Wayland compositor die? vas. 20 00:59:22 laptop plasmashell[4391]: The Wayland connection broke. Did the Wayland compositor die? vas. 20 00:59:22 laptop org.kde.kpasswdserver[3701]: The Wayland connection broke. Did the Wayland compositor die? vas. 20 00:59:22 laptop org.kde.kpasswdserver[3701]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* vas. 20 00:59:22 laptop org.kde.kuiserver[3701]: The Wayland connection broke. Did the Wayland compositor die? I don't see a crash in the frame stacks. On 2019-02-20 05:24, Martin Flöser wrote:
> https://bugs.kde.org/show_bug.cgi?id=404580
>
> --- Comment #2 from Martin Flöser <mgraesslin@kde.org> ---
> I don't see a crash in the frame stacks.
How can I obtain a crash log then.
I obtained this by running coredumpctl debug /usr/bin/kwin_wayland.
And dmesg clearly indicates General protection fault, so some illegal
action was being attempted.
Oh, I'm sure this is the backtrace. I just don't see any crash. All threads are in their event loop except for thread 1 which is looking innocent: qdbus code from event loop. None of the threads is in KWin code. #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 |