Bug 427695

Summary:	Yakuake crash upon startup
Product:	[Applications] yakuake	Reporter:	phrxmd <philipp.reichmuth>
Component:	general	Assignee:	Eike Hein <hein>
Status:	RESOLVED UPSTREAM
Severity:	crash	CC:	robert
Priority:	NOR	Keywords:	drkonqi
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	New crash information added by DrKonqi

Description phrxmd 2020-10-14 14:53:46 UTC

Application: yakuake (20.08.1)

Qt Version: 5.15.1
Frameworks Version: 5.75.0
Operating System: Linux 5.8.14-1-default x86_64
Windowing system: Wayland
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
Yakuake crashes upon startup in the OpenSUSE "Full Wayland" session (Plasma 5.19.5).

The crash can be reproduced every time.

-- Backtrace:
Application: Yakuake (yakuake), signal: Aborted

[KCrash Handler]
#4  0x00007f82656e0641 in raise () at /lib64/libc.so.6
#5  0x00007f82656c9538 in abort () at /lib64/libc.so.6
#6  0x00007f8265ae6c37 in qt_message_fatal (message=<synthetic pointer>..., context=...) at global/qlogging.cpp:1914
#7  QMessageLogger::fatal(char const*, ...) const (this=this@entry=0x7ffc4b38dd00, msg=msg@entry=0x7f8261cbb0b8 "The Wayland connection broke. Did the Wayland compositor die?") at global/qlogging.cpp:893
#8  0x00007f8261c36ed9 in QtWaylandClient::QWaylandDisplay::checkError() const (this=<optimized out>) at /usr/include/qt5/QtCore/qlogging.h:90
#9  QtWaylandClient::QWaylandDisplay::checkError() const (this=<optimized out>) at qwaylanddisplay.cpp:204
#10 0x00007f8261c44dce in QtWaylandClient::QWaylandDisplay::flushRequests() (this=0x556023612290) at qwaylanddisplay.cpp:222
#11 0x00007f8265d37680 in doActivate<false>(QObject*, int, void**) (sender=0x556023683b50, signal_index=4, argv=0x7ffc4b38dde0, argv@entry=0x0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:395
#12 0x00007f8265d309a0 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x556023683b50, m=m@entry=0x7f8265fe4180 <QAbstractEventDispatcher::staticMetaObject>, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at kernel/qobject.cpp:3946
#13 0x00007f8265cfdbf3 in QAbstractEventDispatcher::awake() (this=this@entry=0x556023683b50) at .moc/moc_qabstracteventdispatcher.cpp:149
#14 0x00007f8265d585ec in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x556023683b50, flags=...) at kernel/qeventdispatcher_glib.cpp:430
#15 0x00007f8265cffa1b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7ffc4b38df00, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141
#16 0x00007f8265d07c90 in QCoreApplication::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:121
#17 0x0000556022d8c5d7 in main(int, char**) (argc=<optimized out>, argv=0x7ffc4b38e020) at /usr/src/debug/yakuake-20.08.1-1.1.x86_64/app/main.cpp:87
[Inferior 1 (process 5034) detached]

Possible duplicates by query: bug 424911, bug 423951, bug 423132, bug 417285, bug 414922.

Reported using DrKonqi

Comment 1 Robert Riemann 2020-12-20 22:56:35 UTC

Created attachment 134240 [details]
New crash information added by DrKonqi

yakuake (20.08.3) using Qt 5.15.2

- What I was doing when the application crashed:

I logged in using a Wayland (full) Plasma session.

- Unusual behavior I noticed:

Before, my session crashed due to a problem with external monitor/sleep.

-- Backtrace (Reduced):
#6  0x00007f4caf5590e7 in qt_message_fatal (message=<synthetic pointer>..., context=...) at global/qlogging.cpp:1914
#7  QMessageLogger::fatal (this=this@entry=0x7ffedbec7b90, msg=msg@entry=0x7f4cad94d0b8 "The Wayland connection broke. Did the Wayland compositor die?") at global/qlogging.cpp:893
#8  0x00007f4cad8c8f79 in QtWaylandClient::QWaylandDisplay::checkError (this=<optimized out>) at qwaylanddisplay.cpp:209
#9  QtWaylandClient::QWaylandDisplay::checkError (this=<optimized out>) at qwaylanddisplay.cpp:204
#10 0x00007f4cad8d7e0a in QtWaylandClient::QWaylandDisplay::flushRequests (this=0x55b76f934400) at qwaylanddisplay.cpp:222

Comment 2 Nate Graham 2021-01-13 18:44:48 UTC

#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