[dolphin] [Bug 428519] Dolphin crashes when being resized on wayland

[Janne Mareike Koschinski]

https://bugs.kde.org/show_bug.cgi?id=428519

--- Comment #3 from Janne Mareike Koschinski <newsletter at kuschku.de> ---
(In reply to Nate Graham from comment #2)
> #6  QMessageLogger::fatal (this=this at entry=0x7fffd70c5ba0,
> msg=msg at 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.

But the compositor didn’t crash, it stayed running, and other apps continued
working?

> 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!

I did encounter other crashes, and for every kwin_wayland crash I’ve found,
I’ve filed a report, but as said above, kwin_wayland did not crash in this
case. The session stayed open just fine.

> 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

-- 
You are receiving this mail because:
You are on the CC list for the bug.