Bug 424593 - Crash on log in with wayland session
Summary: Crash on log in with wayland session
Status: RESOLVED DUPLICATE of bug 423179
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: 5.19.3
Platform: openSUSE Linux
: NOR crash
Target Milestone: 1.0
Assignee: David Edmundson
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2020-07-24 00:38 UTC by Carl Morgan
Modified: 2020-11-29 22:30 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Carl Morgan 2020-07-24 00:38:38 UTC
Application: plasmashell (5.19.3)

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

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

Logged in to a wayland session.  The desktop seems to be still fully usable just with a crash notice.

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

[KCrash Handler]
#4  0x00007f4bc23734b1 in raise () from /lib64/libc.so.6
#5  0x00007f4bc235c539 in abort () from /lib64/libc.so.6
#6  0x00007f4bc2774c27 in qt_message_fatal (message=<synthetic pointer>..., context=...) at global/qlogging.cpp:1914
#7  QMessageLogger::fatal (this=this@entry=0x7ffcefa56ee0, msg=msg@entry=0x7f4bbe4e50b8 "The Wayland connection broke. Did the Wayland compositor die?") at global/qlogging.cpp:893
#8  0x00007f4bbe460ef9 in QtWaylandClient::QWaylandDisplay::checkError (this=<optimized out>) at /usr/include/qt5/QtCore/qlogging.h:90
#9  QtWaylandClient::QWaylandDisplay::checkError (this=<optimized out>) at qwaylanddisplay.cpp:204
#10 0x00007f4bbe46edee in QtWaylandClient::QWaylandDisplay::flushRequests (this=0x556a7c790490) at qwaylanddisplay.cpp:222
#11 0x00007f4bc29c4130 in doActivate<false> (sender=0x556a7c7feb10, signal_index=4, argv=0x7ffcefa56fc0, argv@entry=0x0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:395
#12 0x00007f4bc29bd450 in QMetaObject::activate (sender=sender@entry=0x556a7c7feb10, m=m@entry=0x7f4bc2c6f180 <QAbstractEventDispatcher::staticMetaObject>, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at kernel/qobject.cpp:3946
#13 0x00007f4bc298a7d3 in QAbstractEventDispatcher::awake (this=this@entry=0x556a7c7feb10) at .moc/moc_qabstracteventdispatcher.cpp:149
#14 0x00007f4bc29e509c in QEventDispatcherGlib::processEvents (this=0x556a7c7feb10, flags=...) at kernel/qeventdispatcher_glib.cpp:430
#15 0x00007f4bc298c5db in QEventLoop::exec (this=this@entry=0x556a7e3a72b0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141
#16 0x00007f4b3430a9d5 in KScreen::WaylandConfig::WaylandConfig (parent=0x556a7e371bb0, this=0x556a7e3a7260) at /usr/include/qt5/QtCore/qflags.h:121
#17 KScreen::WaylandBackend::WaylandBackend (this=0x556a7e371bb0) at /usr/src/debug/libkscreen2-5.19.3-1.1.x86_64/backends/kwayland/waylandbackend.cpp:38
#18 qt_plugin_instance () at /usr/src/debug/libkscreen2-5.19.3-1.1.x86_64/build/backends/kwayland/KSC_KWayland_autogen/EWIEGA46WW/moc_waylandbackend.cpp:114
#19 0x00007f4bc2983dc7 in QLibraryPrivate::pluginInstance (this=0x556a7d84aeb0) at plugin/qlibrary.cpp:557
#20 0x00007f4bc2974f13 in QPluginLoader::instance (this=this@entry=0x556a7ddc25c0) at plugin/qpluginloader.cpp:199
#21 0x00007f4b6814ab3b in KScreen::BackendManager::loadBackendPlugin (loader=0x556a7ddc25c0, name=..., arguments=...) at /usr/src/debug/libkscreen2-5.19.3-1.1.x86_64/src/backendmanager.cpp:198
#22 0x00007f4b68150160 in KScreen::BackendManager::loadBackendInProcess (this=0x556a7e0f5a00, name=...) at /usr/src/debug/libkscreen2-5.19.3-1.1.x86_64/src/backendmanager.cpp:243
#23 0x00007f4b681506b1 in KScreen::ConfigOperationPrivate::loadBackend (this=<optimized out>) at /usr/src/debug/libkscreen2-5.19.3-1.1.x86_64/src/configoperation.cpp:138
#24 0x00007f4b681569a2 in KScreen::GetConfigOperation::start (this=0x556a7de11db0) at /usr/src/debug/libkscreen2-5.19.3-1.1.x86_64/src/getconfigoperation.cpp:173
#25 0x00007f4bc29b9b41 in QObject::event (this=0x556a7de11db0, e=0x556a7de05ed0) at kernel/qobject.cpp:1314
#26 0x00007f4bc353b0cf in QApplicationPrivate::notify_helper (this=<optimized out>, receiver=0x556a7de11db0, e=0x556a7de05ed0) at kernel/qapplication.cpp:3671
#27 0x00007f4bc298dc1a in QCoreApplication::notifyInternal2 (receiver=0x556a7de11db0, event=0x556a7de05ed0) at ../../include/QtCore/5.15.0/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:325
#28 0x00007f4bc2990641 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x556a7c778560) at kernel/qcoreapplication.cpp:1815
#29 0x00007f4bc29e59d3 in postEventSourceDispatch (s=0x556a7c7ff200) at kernel/qeventdispatcher_glib.cpp:277
#30 0x00007f4bc0e142b7 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#31 0x00007f4bc0e14638 in ?? () from /usr/lib64/libglib-2.0.so.0
#32 0x00007f4bc0e146ef in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#33 0x00007f4bc29e505f in QEventDispatcherGlib::processEvents (this=0x556a7c7feb10, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#34 0x00007f4bc298c5db in QEventLoop::exec (this=this@entry=0x7ffcefa577b0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141
#35 0x00007f4bc2994840 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121
#36 0x0000556a7abf6c87 in main (argc=<optimized out>, argv=0x7ffcefa579d0) at /usr/src/debug/plasma5-workspace-5.19.3-1.1.x86_64/shell/main.cpp:224
[Inferior 1 (process 6032) detached]

The reporter indicates this bug may be a duplicate of or related to bug 423179.

Possible duplicates by query: bug 424009, bug 423951, bug 423179, bug 423132, bug 423075.

Reported using DrKonqi
Comment 1 Patrick Silva 2020-08-17 14:55:45 UTC
Sometimes the same occurs on my Arch Lnux.

Qt Version: 5.15.0
Frameworks Version: 5.73.0
Windowing system: Wayland
Distribution: Arch Linux
Comment 2 Tony 2020-11-29 22:30:25 UTC

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