Bug 423179 - Plasma Wayland crashes with "The Wayland connection broke. Did the Wayland compositor die" when kwin_wayland crashes
Summary: Plasma Wayland crashes with "The Wayland connection broke. Did the Wayland co...
Status: RESOLVED UPSTREAM
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-crash (show other bugs)
Version: master
Platform: openSUSE Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL: https://bugreports.qt.io/browse/QTBUG...
Keywords: drkonqi, wayland
: 422895 424009 424593 427522 428513 428614 429026 (view as bug list)
Depends on:
Blocks:
 
Reported: 2020-06-18 18:11 UTC by Tony
Modified: 2021-02-26 17:43 UTC (History)
9 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Flashing (2.81 MB, video/mp4)
2020-06-18 18:18 UTC, Tony
Details
New crash information added by DrKonqi (2.82 KB, text/plain)
2020-06-25 19:31 UTC, Tony
Details
New crash information added by DrKonqi (3.07 KB, text/plain)
2020-07-11 19:25 UTC, Tony
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tony 2020-06-18 18:11:19 UTC
Application: plasmashell (5.19.80)

Qt Version: 5.15.0
Frameworks Version: 5.72.0
Operating System: Linux 5.7.1-1-default x86_64
Windowing system: Wayland
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:
Just logged into a new session.

- Unusual behavior I noticed:
There was no wallpaper black background(i think is another bug where plasma its not saving some settings) and part of the screen was flashing, like wanting to render something but it can't.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Plasma (plasmashell), signal: Aborted

[KCrash Handler]
#4  0x00007f27222e44b1 in raise () at /lib64/libc.so.6
#5  0x00007f27222cd539 in abort () at /lib64/libc.so.6
#6  0x00007f27226e6c27 in qt_message_fatal (message=<synthetic pointer>..., context=...) at global/qlogging.cpp:1914
#7  0x00007f27226e6c27 in QMessageLogger::fatal(char const*, ...) const (this=this@entry=0x7ffea02b8960, msg=msg@entry=0x7f271e3050b8 "The Wayland connection broke. Did the Wayland compositor die?") at global/qlogging.cpp:893
#8  0x00007f271e24bf25 in QtWaylandClient::QWaylandDisplay::checkError() const (this=<optimized out>) at /usr/include/qt5/QtCore/qlogging.h:90
#9  0x00007f271e24bf25 in QtWaylandClient::QWaylandDisplay::checkError() const (this=<optimized out>) at qwaylanddisplay.cpp:204
#10 0x00007f271e25c2ae in QtWaylandClient::QWaylandDisplay::flushRequests() (this=0x55b814220db0) at qwaylanddisplay.cpp:222
#11 0x00007f2722936020 in doActivate<false>(QObject*, int, void**) (sender=0x55b814285aa0, signal_index=3, argv=0x7ffea02b8a40, argv@entry=0x0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:395
#12 0x00007f272292f340 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x55b814285aa0, m=m@entry=0x7f2722be1180 <QAbstractEventDispatcher::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3946
#13 0x00007f27228fc6b0 in QAbstractEventDispatcher::aboutToBlock() (this=this@entry=0x55b814285aa0) at .moc/moc_qabstracteventdispatcher.cpp:143
#14 0x00007f2722956f24 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x55b814285aa0, flags=...) at kernel/qeventdispatcher_glib.cpp:410
#15 0x00007f27228fe4cb in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7ffea02b8b60, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141
#16 0x00007f2722906730 in QCoreApplication::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:121
#17 0x000055b814041c97 in main(int, char**) (argc=<optimized out>, argv=0x7ffea02b8d80) at /usr/src/debug/plasma5-workspace-5.19.80git.20200617T081732~8e78f7f43-ku.132.1.x86_64/shell/main.cpp:224
[Inferior 1 (process 6290) detached]

The reporter indicates this bug may be a duplicate of or related to bug 423075, bug 421047.

Possible duplicates by query: bug 423132, bug 423075, bug 422995, bug 422287, bug 421446.

Reported using DrKonqi
Comment 1 Tony 2020-06-18 18:18:55 UTC
Created attachment 129495 [details]
Flashing
Comment 2 Tony 2020-06-25 19:31:10 UTC
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
Comment 3 Christoph Feck 2020-07-08 18:07:24 UTC
The error is: "The Wayland connection broke. Did the Wayland compositor die?"

Qt cannot recover from this error.
Comment 4 Tony 2020-07-11 19:25:23 UTC
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
Comment 5 Nate Graham 2020-11-15 15:33:54 UTC
*** Bug 428513 has been marked as a duplicate of this bug. ***
Comment 6 Tony 2020-11-16 03:24:15 UTC
*** Bug 422895 has been marked as a duplicate of this bug. ***
Comment 7 Tony 2020-11-29 22:30:25 UTC
*** Bug 424593 has been marked as a duplicate of this bug. ***
Comment 8 Tony 2020-11-29 22:31:10 UTC
*** Bug 424009 has been marked as a duplicate of this bug. ***
Comment 9 Tony 2020-11-29 22:31:23 UTC
*** Bug 429026 has been marked as a duplicate of this bug. ***
Comment 10 Tony 2020-11-29 22:34:33 UTC
*** Bug 427522 has been marked as a duplicate of this bug. ***
Comment 11 Nate Graham 2021-02-26 17:42:38 UTC
*** Bug 428614 has been marked as a duplicate of this bug. ***