Summary: | Plasma Wayland crashes with "The Wayland connection broke. Did the Wayland compositor die" when kwin_wayland crashes | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | Tony <jodr666> |
Component: | generic-crash | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED UPSTREAM | ||
Severity: | crash | CC: | bug2017, carl, janne, jodr666, khabalex, nate, plasma-bugs, tosak, twinshadows404 |
Priority: | NOR | Keywords: | drkonqi, wayland |
Version: | master | ||
Target Milestone: | 1.0 | ||
Platform: | openSUSE | ||
OS: | Linux | ||
URL: | https://bugreports.qt.io/browse/QTBUG-85631 | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
Flashing
New crash information added by DrKonqi New crash information added by DrKonqi |
Description
Tony
2020-06-18 18:11:19 UTC
Created attachment 129495 [details]
Flashing
Created attachment 129681 [details]
New crash information added by DrKonqi
plasmashell (5.19.80) using Qt 5.15.0
- What I was doing when the application crashed:
This time i hovered the mouse of all the way to the left, towards the launcher and clicked on it after closing a firefox window.
I have set the desktop background to plain color, black, to avoid the rendering issue with image wallpapers.
I haven't found a consistence way to tigger it.
-- Backtrace (Reduced):
#6 0x00007f44ab4b6c27 in qt_message_fatal (message=<synthetic pointer>..., context=...) at global/qlogging.cpp:1914
#7 0x00007f44ab4b6c27 in QMessageLogger::fatal(char const*, ...) const (this=this@entry=0x7ffd773edbe0, msg=msg@entry=0x7f44a70d50f8 "The Wayland connection experienced a fatal error: %s") at global/qlogging.cpp:893
#8 0x00007f44a702c260 in QtWaylandClient::QWaylandDisplay::checkError() const (this=<optimized out>) at /usr/include/qt5/QtCore/qlogging.h:90
#9 0x00007f44a702c2ae in QtWaylandClient::QWaylandDisplay::flushRequests() (this=0x5599597c9db0) at qwaylanddisplay.cpp:222
#10 0x00007f44ab706020 in doActivate<false>(QObject*, int, void**) (sender=0x5599597edde0, signal_index=4, argv=0x7ffd773edcc0, argv@entry=0x0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:395
The error is: "The Wayland connection broke. Did the Wayland compositor die?" Qt cannot recover from this error. Created attachment 130048 [details]
New crash information added by DrKonqi
plasmashell (5.19.80) using Qt 5.15.0
- What I was doing when the application crashed:
This time it happen while right clicking on the desktop and hitting configure desktop.
Would please reconfirm this is a QT issue not a wayland/kde one as well as poiting to any upstream bug if possible.
I woud like to have those as reference as this keeps happening all over the place making the wayland season pretty unstable on top of annoying.
-- Backtrace (Reduced):
#4 0x00007f4205d344b1 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#5 0x00007f4205d1d539 in __GI_abort () at abort.c:79
#6 0x00007f4206136c27 in qt_message_fatal (message=<synthetic pointer>..., context=...) at global/qlogging.cpp:1914
#7 0x00007f4206136c27 in QMessageLogger::fatal(char const*, ...) const (this=this@entry=0x7ffffdfb61b0, msg=msg@entry=0x7f4201d550b8 "The Wayland connection broke. Did the Wayland compositor die?") at global/qlogging.cpp:893
#8 0x00007f4201c9bf25 in QtWaylandClient::QWaylandDisplay::checkError() const (this=<optimized out>) at /usr/include/qt5/QtCore/qlogging.h:90
*** Bug 428513 has been marked as a duplicate of this bug. *** *** Bug 422895 has been marked as a duplicate of this bug. *** *** Bug 424593 has been marked as a duplicate of this bug. *** *** Bug 424009 has been marked as a duplicate of this bug. *** *** Bug 429026 has been marked as a duplicate of this bug. *** *** Bug 427522 has been marked as a duplicate of this bug. *** *** Bug 428614 has been marked as a duplicate of this bug. *** |