| Summary: | Dolphin crashes when being resized on wayland | ||
|---|---|---|---|
| Product: | [Applications] dolphin | Reporter: | Janne Mareike Koschinski <janne> |
| Component: | general | Assignee: | Dolphin Bug Assignee <dolphin-bugs-null> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | crash | CC: | janne, kfm-devel, nate |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | 20.08.2 | ||
| Target Milestone: | --- | ||
| Platform: | Neon | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | New crash information added by DrKonqi | ||
|
Description
Janne Mareike Koschinski
2020-10-31 16:35:59 UTC
Created attachment 132920 [details]
New crash information added by DrKonqi
dolphin (20.08.2) using Qt 5.15.0
- What I was doing when the application crashed:
Resizing Dolphin
Dolphin could not be resized, it was stuck
- Environment:
Operating System: KDE neon 5.20
KDE Plasma Version: 5.20.2
KDE Frameworks Version: 5.75.0
Qt Version: 5.15.0
Kernel Version: 5.4.0-52-generic
Graphics Processor: AMD Radeon ™ RX 480 Graphics
-- Backtrace (Reduced):
#4 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#5 0x00007f6636171859 in __GI_abort () at abort.c:79
#6 0x00007f6633d5dc39 in qt_message_fatal (context=..., message=<synthetic pointer>...) at global/qlogging.cpp:1914
#7 QMessageLogger::fatal (this=this@entry=0x7ffcbe31a520, msg=msg@entry=0x7f662ee1d0b8 "The Wayland connection broke. Did the Wayland compositor die?") at global/qlogging.cpp:893
#8 0x00007f662ed61d15 in QtWaylandClient::QWaylandDisplay::checkError (this=<optimized out>) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qlogging.h:90
#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 (In reply to Nate Graham from comment #2) > #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. 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 Yes, we have done work recently to keep the session itself alive when the compositor crashes, so I'm happy it worked! :) Now it restarts itself when it crashes--but unfortunately apps do not, which is why this sometimes happens. |