Bug 422895 - [Wayland] Systemsettings crashes with "The Wayland connection broke. Did the Wayland compositor die?"
Summary: [Wayland] Systemsettings crashes with "The Wayland connection broke. Did the ...
Status: RESOLVED DUPLICATE of bug 423179
Alias: None
Product: systemsettings
Classification: Applications
Component: generic-crash (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords: drkonqi, wayland
: 424729 (view as bug list)
Depends on:
Blocks:
 
Reported: 2020-06-12 21:49 UTC by Tony
Modified: 2020-11-16 03:24 UTC (History)
4 users (show)

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


Attachments
terminal log for systemsettings5 (15.12 KB, text/plain)
2020-06-25 05:15 UTC, Tony
Details
New crash information added by DrKonqi (5.22 KB, text/plain)
2020-06-27 16:26 UTC, Tony
Details
Systemsettings5 terminal log (18.14 KB, text/plain)
2020-06-27 16:28 UTC, Tony
Details
New crash information added by DrKonqi (4.61 KB, text/plain)
2020-07-11 12:11 UTC, Tony
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tony 2020-06-12 21:49:49 UTC
Application: systemsettings5 (5.19.80)

Qt Version: 5.15.0
Frameworks Version: 5.71.0
Operating System: Linux 5.7.2-xanmod1 x86_64
Windowing system: Wayland
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:

Log out from x session and logged into wayland.
On the new wayland session opened systemsettings and clicked on "startup and shutdown".

The crash can be reproduced sometimes.

-- Backtrace:
Application: System Settings (systemsettings5), signal: Aborted

[KCrash Handler]
#4  0x00007f7bb4e2c4b1 in raise () at /lib64/libc.so.6
#5  0x00007f7bb4e15539 in abort () at /lib64/libc.so.6
#6  0x00007f7bb522ec27 in qt_message_fatal (message=<synthetic pointer>..., context=...) at global/qlogging.cpp:1914
#7  0x00007f7bb522ec27 in QMessageLogger::fatal(char const*, ...) const (this=this@entry=0x7ffd198dae20, msg=msg@entry=0x7f7bb061d0b8 "The Wayland connection broke. Did the Wayland compositor die?") at global/qlogging.cpp:893
#8  0x00007f7bb0563f25 in QtWaylandClient::QWaylandDisplay::checkError() const (this=<optimized out>) at /usr/include/qt5/QtCore/qlogging.h:90
#9  0x00007f7bb0563f25 in QtWaylandClient::QWaylandDisplay::checkError() const (this=<optimized out>) at qwaylanddisplay.cpp:204
#10 0x00007f7bb05744c1 in QtWaylandClient::QWaylandDisplay::dispatchQueueWhile(wl_event_queue*, std::function<bool ()>, int) (this=0x562fce90a400, queue=0x562fcead3e40, condition=..., timeout=timeout@entry=100) at qwaylanddisplay.cpp:260
#11 0x00007f7bb057b120 in QtWaylandClient::QWaylandWindow::waitForFrameSync(int) (this=0x562fcead1bf0, timeout=100) at /usr/include/c++/9/new:174
#12 0x00007f7bae9e14ea in QtWaylandClient::QWaylandGLContext::swapBuffers(QPlatformSurface*) (this=0x562fcfa7c0f0, surface=<optimized out>) at ../../../../hardwareintegration/client/wayland-egl/qwaylandglcontext.cpp:486
#13 0x00007f7bb5bd3c93 in QPlatformBackingStore::composeAndFlush(QWindow*, QRegion const&, QPoint const&, QPlatformTextureList*, bool) (this=this@entry=0x562fceac69d0, window=0x562fceab5f50, region=..., offset=..., textures=textures@entry=0x562fcecbe090, translucentBackground=translucentBackground@entry=false) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:116
#14 0x00007f7bb5fb1e13 in QWidgetRepaintManager::flush(QWidget*, QRegion const&, QPlatformTextureList*) (this=this@entry=0x562fceba74d0, widget=0x562fce95a040, region=..., widgetTextures=<optimized out>) at kernel/qwidgetrepaintmanager.cpp:1179
#15 0x00007f7bb5fb3e6b in QWidgetRepaintManager::flush() (this=this@entry=0x562fceba74d0) at kernel/qwidgetrepaintmanager.cpp:1082
#16 0x00007f7bb5fb596e in QWidgetRepaintManager::paintAndFlush() (this=<optimized out>) at kernel/qwidgetrepaintmanager.cpp:1014
#17 0x00007f7bb5fe5807 in QWidget::event(QEvent*) (this=0x562fce95a040, event=0x562fcf46f4b0) at kernel/qwidget.cpp:8972
#18 0x00007f7bb6a49a59 in KXmlGuiWindow::event(QEvent*) (this=0x562fce95a040, ev=0x562fcf46f4b0) at /usr/src/debug/kxmlgui-5.71.0git.20200611T182047~c2d78f3-ku.9.1.x86_64/src/kxmlguiwindow.cpp:121
#19 0x00007f7bb5fa50cf in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=<optimized out>, receiver=0x562fce95a040, e=0x562fcf46f4b0) at kernel/qapplication.cpp:3671
#20 0x00007f7bb5447b0a in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x562fce95a040, event=0x562fcf46f4b0) at ../../include/QtCore/5.15.0/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:325
#21 0x00007f7bb544a531 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (receiver=0x0, event_type=0, data=0x562fce8f3660) at kernel/qcoreapplication.cpp:1815
#22 0x00007f7bb549f8c3 in postEventSourceDispatch(GSource*, GSourceFunc, gpointer) (s=0x562fce946020) at kernel/qeventdispatcher_glib.cpp:277
#23 0x00007f7bb2fcc2c7 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0
#24 0x00007f7bb2fcc648 in  () at /usr/lib64/libglib-2.0.so.0
#25 0x00007f7bb2fcc6ff in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#26 0x00007f7bb549ef4f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x562fce923780, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#27 0x00007f7bb54464cb in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7ffd198db9e0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141
#28 0x00007f7bb544e730 in QCoreApplication::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:121
#29 0x0000562fce8a8fd9 in main(int, char**) (argc=<optimized out>, argv=0x7ffd198dbaf0) at /usr/src/debug/systemsettings5-5.19.80git.20200607T021509~3fcceee6-ku.32.1.x86_64/app/main.cpp:168
[Inferior 1 (process 29009) detached]

Possible duplicates by query: bug 422233, bug 422029, bug 422014, bug 421828, bug 421699.

Reported using DrKonqi
Comment 1 David Edmundson 2020-06-24 22:58:43 UTC
We were killed by kwin for making a protocol violation.

Can you run from a terminal and reproduce and paste the contents
Comment 2 Tony 2020-06-25 05:15:16 UTC
Created attachment 129656 [details]
terminal log for systemsettings5

Sadly i can't reproduced the crash anymore, may be it was related to some other issue i had over the past weekend, i end up deleting ~/.cache and those as well as this one don't happen anymore.

The attatchement it may not be of any help now although I do find wierd this line keeps repeating in it :
dri_create_context: requested glthread but driver is missing backgroundCallable V2 extension
Comment 3 David Edmundson 2020-06-25 07:04:07 UTC
Ok, well please do keep us informed if it comes up again.

Typically a protocol error would be some code in Qt, systemsettings won't be doing anything natively itself. So it might get fixed with different Qt releases
Comment 4 Tony 2020-06-27 16:26:07 UTC
Created attachment 129725 [details]
New crash information added by DrKonqi

systemsettings5 (5.19.80) using Qt 5.15.0

- What I was doing when the application crashed:

Mostly the same steps, switched from x session to wayland.

The main difference this time being :
I updated the system from a different tty.
After the installation finished, ran systemctl daemon-reload && systemctl daemon-reexec.
Deleted ~/.cache
Switch bacl to sdd and log in.

-- Backtrace (Reduced):
#4  0x00007f4360a244b1 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#5  0x00007f4360a0d539 in __GI_abort () at abort.c:79
#6  0x00007f4360e26c27 in qt_message_fatal (message=<synthetic pointer>..., context=...) at global/qlogging.cpp:1914
#7  0x00007f4360e26c27 in QMessageLogger::fatal(char const*, ...) const (this=this@entry=0x7fff64646fa0, msg=msg@entry=0x7f435c2150b8 "The Wayland connection broke. Did the Wayland compositor die?") at global/qlogging.cpp:893
#8  0x00007f435c15bf25 in QtWaylandClient::QWaylandDisplay::checkError() const (this=<optimized out>) at /usr/include/qt5/QtCore/qlogging.h:90
Comment 5 Tony 2020-06-27 16:28:17 UTC
Created attachment 129726 [details]
Systemsettings5 terminal log

Also this time i did run systemsettings from a terminal when it happen.
Comment 6 Christoph Feck 2020-06-29 20:23:24 UTC
New information was added with recent comments; changing status for inspection.
Comment 7 Tony 2020-07-11 12:11:44 UTC
Created attachment 130038 [details]
New crash information added by DrKonqi

systemsettings5 (5.19.80) using Qt 5.15.0

- What I was doing when the application crashed:

This time it happen but instead of clicking on "start up and shutdown" it happen with display and monitor.

-- Backtrace (Reduced):
#4  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#5  0x00007f9b1fce5539 in __GI_abort () at abort.c:79
#6  0x00007f9b200fec27 in qt_message_fatal (message=<synthetic pointer>..., context=...) at global/qlogging.cpp:1914
#7  QMessageLogger::fatal (this=this@entry=0x7ffef33bd990, msg=msg@entry=0x7f9b1b4ed0b8 "The Wayland connection broke. Did the Wayland compositor die?") at global/qlogging.cpp:893
#8  0x00007f9b1b433f25 in QtWaylandClient::QWaylandDisplay::checkError (this=<optimized out>) at /usr/include/qt5/QtCore/qlogging.h:90
Comment 8 Nate Graham 2020-10-12 22:49:02 UTC
*** Bug 424729 has been marked as a duplicate of this bug. ***
Comment 9 Tony 2020-11-16 03:24:15 UTC

*** This bug has been marked as a duplicate of bug 423179 ***