Bug 425361 - Sometimes Plasma Wayland session crashes with "The Wayland connection experienced a fatal error" when I open an app via Dashboard launcher
Summary: Sometimes Plasma Wayland session crashes with "The Wayland connection experie...
Status: RESOLVED FIXED
Alias: None
Product: kdeplasma-addons
Classification: Plasma
Component: Application Dashboard (show other bugs)
Version: unspecified
Platform: Neon Linux
: NOR crash
Target Milestone: ---
Assignee: Eike Hein
URL:
Keywords: drkonqi
: 426368 (view as bug list)
Depends on:
Blocks:
 
Reported: 2020-08-14 23:25 UTC by Patrick Silva
Modified: 2023-11-19 13:18 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (2.58 KB, text/plain)
2021-02-19 23:37 UTC, k2c6l3m8l
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick Silva 2020-08-14 23:25:50 UTC
Application: plasmashell (5.19.80)

Qt Version: 5.14.2
Frameworks Version: 5.74.0
Operating System: Linux 5.4.0-42-generic x86_64
Windowing system: Wayland
Distribution: KDE neon Unstable Edition

-- Information about the crash:
- What I was doing when the application crashed:
Sometimes Plasma crashes on Wayland when I open an app via Dashboard launcher.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Plasma (plasmashell), signal: Aborted
Content of s_kcrashErrorMessage: (null)
[KCrash Handler]
#6  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#7  0x00007f2664f16859 in __GI_abort () at abort.c:79
#8  0x00007f2665355b69 in qt_message_fatal (context=..., message=<synthetic pointer>...) at global/qlogging.cpp:1914
#9  QMessageLogger::fatal(char const*, ...) const (this=this@entry=0x7fff93079700, msg=msg@entry=0x7f26611241c0 "The Wayland connection experienced a fatal error: %s") at global/qlogging.cpp:893
#10 0x00007f2661082084 in QtWaylandClient::QWaylandDisplay::checkError() const (this=<optimized out>) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qlogging.h:90
#11 0x00007f26610820de in QtWaylandClient::QWaylandDisplay::flushRequests() (this=0x555882df3fc0) at qwaylanddisplay.cpp:209
#12 0x00007f26655a3550 in doActivate<false>(QObject*, int, void**) (sender=0x555882e22420, signal_index=3, argv=0x7fff93079840) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:395
#13 0x00007f266559daf7 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x555882e22420, m=m@entry=0x7f2665849ba0 <QSocketNotifier::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff93079840) at kernel/qobject.cpp:3930
#14 0x00007f26655a6d95 in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) (this=this@entry=0x555882e22420, _t1=<optimized out>, _t2=...) at .moc/moc_qsocketnotifier.cpp:141
#15 0x00007f26655a70f1 in QSocketNotifier::event(QEvent*) (this=0x555882e22420, e=0x7fff93079b00) at kernel/qsocketnotifier.cpp:266
#16 0x00007f26660dacc3 in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0x555882deccd0, receiver=receiver@entry=0x555882e22420, e=e@entry=0x7fff93079b00) at kernel/qapplication.cpp:3685
#17 0x00007f26660e3f40 in QApplication::notify(QObject*, QEvent*) (this=0x7fff93079e60, receiver=0x555882e22420, e=0x7fff93079b00) at kernel/qapplication.cpp:3431
#18 0x00007f266556d78a in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x555882e22420, event=0x7fff93079b00) at ../../include/QtCore/../../src/corelib/kernel/qobject.h:153
#19 0x00007f26655c6de5 in socketNotifierSourceDispatch(GSource*, GSourceFunc, gpointer) (source=0x555882e0e100) at kernel/qeventdispatcher_glib.cpp:107
#20 0x00007f266394afbd in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007f266394b240 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x00007f266394b2e3 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x00007f26655c61e2 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x555882e19620, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#24 0x00007f266556c24b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7fff93079d10, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136
#25 0x00007f2665574296 in QCoreApplication::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:118
#26 0x00005558821edcbc in main(int, char**) (argc=<optimized out>, argv=<optimized out>) at ./shell/main.cpp:242
[Inferior 1 (process 53602) detached]

Possible duplicates by query: bug 424923, bug 424922, bug 424921, bug 424911, bug 424879.

Reported using DrKonqi
Comment 1 Méven Car 2020-08-20 15:12:15 UTC
Seems like a QtWayland issue:

#6  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#7  0x00007f2664f16859 in __GI_abort () at abort.c:79
#8  0x00007f2665355b69 in qt_message_fatal (context=..., message=<synthetic pointer>...) at global/qlogging.cpp:1914
#9  QMessageLogger::fatal(char const*, ...) const (this=this@entry=0x7fff93079700, msg=msg@entry=0x7f26611241c0 "The Wayland connection experienced a fatal error: %s") at global/qlogging.cpp:893
#10 0x00007f2661082084 in QtWaylandClient::QWaylandDisplay::checkError() const (this=<optimized out>) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qlogging.h:90
#11 0x00007f26610820de in QtWaylandClient::QWaylandDisplay::flushRequests() (this=0x555882df3fc0) at qwaylanddisplay.cpp:209
#12 0x00007f26655a3550 in doActivate<false>(QObject*, int, void**) (sender=0x555882e22420, signal_index=3, argv=0x7fff93079840) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:395
#13 0x00007f266559daf7 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x555882e22420, m=m@entry=0x7f2665849ba0 <QSocketNotifier::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff93079840) at kernel/qobject.cpp:3930
Comment 2 Tony 2020-11-29 22:44:48 UTC
*** Bug 426368 has been marked as a duplicate of this bug. ***
Comment 3 k2c6l3m8l 2021-02-19 23:37:06 UTC
Created attachment 135923 [details]
New crash information added by DrKonqi

plasmashell (5.21.0) using Qt 5.15.2

- What I was doing when the application crashed:
I was changing the global theme to "Open Suse" theme
- Custom settings of the application:
"Open Suse" global theme

-- Backtrace (Reduced):
#6  0x00007f3348caf0e7 in qt_message_fatal (message=<synthetic pointer>..., context=...) at global/qlogging.cpp:1914
#7  QMessageLogger::fatal(char const*, ...) const (this=this@entry=0x7ffe1543fbc0, msg=msg@entry=0x7f3346f780f8 "The Wayland connection experienced a fatal error: %s") at global/qlogging.cpp:893
#8  0x00007f3346f01df0 in QtWaylandClient::QWaylandDisplay::checkError() const (this=<optimized out>) at qwaylanddisplay.cpp:211
#9  0x00007f3346f02e0a in QtWaylandClient::QWaylandDisplay::flushRequests() (this=0x55bcb339fad0) at qwaylanddisplay.cpp:222
#10 0x00007f3348f01980 in doActivate<false>(QObject*, int, void**) (sender=0x55bcb33b2650, signal_index=4, argv=0x7ffe1543fcd0, argv@entry=0x0) at kernel/qobject.cpp:3898
Comment 4 Patrick Silva 2023-11-19 13:18:11 UTC
Cannot reproduce. Let's consider this crash fixed.

Operating System: Arch Linux 
KDE Plasma Version: 5.27.80
KDE Frameworks Version: 5.245.0
Qt Version: 6.6.0
Graphics Platform: Wayland