Bug 436981

Summary: kwin_wayland crashed while reconnecting a screen connected by a thunderbolt dock
Product: [Plasma] kwin Reporter: John Doe <sgalecki>
Component: wayland-genericAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: crash CC: kde, matteovillata, nicolas.fella, skierpage
Priority: NOR Keywords: drkonqi
Version: 5.21.5   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description John Doe 2021-05-12 14:55:29 UTC
Application: konsole (21.04.0)

Qt Version: 5.15.2
Frameworks Version: 5.82.0
Operating System: Linux 5.12.2-zen2-1-zen x86_64
Windowing System: Wayland
Drkonqi Version: 5.21.5
Distribution: Arch Linux

-- Information about the crash:
- What I was doing when the application crashed:
Connecting the dock and trying to force the secondary screen to work, by disabling and reenabling it in the systemsettings

- Unusual behavior I noticed:
The screen was supposedly detected by linux, and yet it stayed off

The crash can be reproduced sometimes.

-- Backtrace:
Application: Konsole (konsole), signal: Segmentation fault

[KCrash Handler]
#4  std::__atomic_base<int>::load (__m=std::memory_order_relaxed, this=0x700050006000b) at /usr/include/c++/10.2.0/bits/atomic_base.h:102
#5  QAtomicOps<int>::loadRelaxed<int> (_q_value=...) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:239
#6  QBasicAtomicInteger<int>::loadRelaxed (this=0x700050006000b) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:107
#7  QWeakPointer<QObject>::internalData (this=0x55c6217a4010) at ../../include/QtCore/../../src/corelib/tools/qsharedpointer_impl.h:698
#8  QPointer<QScreen>::data (this=0x55c6217a4010) at ../../include/QtCore/../../src/corelib/kernel/qpointer.h:77
#9  QPointer<QScreen>::operator QScreen* (this=0x55c6217a4010) at ../../include/QtCore/../../src/corelib/kernel/qpointer.h:83
#10 QPlatformScreen::screen (this=0x7f2204043d50) at kernel/qplatformscreen.cpp:154
#11 0x00007f220dd3ccaa in QtWaylandClient::QWaylandScreen::updateOutputProperties() () from /usr/lib/libQt5WaylandClient.so.5
#12 0x00007f220dd3d2f5 in QtWaylandClient::QWaylandScreen::output_done() () from /usr/lib/libQt5WaylandClient.so.5
#13 0x00007f220d535acd in ?? () from /usr/lib/libffi.so.7
#14 0x00007f220d53503a in ?? () from /usr/lib/libffi.so.7
#15 0x00007f220dcb7fe4 in ?? () from /usr/lib/libwayland-client.so.0
#16 0x00007f220dcb4563 in ?? () from /usr/lib/libwayland-client.so.0
#17 0x00007f220dcb5cac in wl_display_dispatch_queue_pending () from /usr/lib/libwayland-client.so.0
#18 0x00007f220dd3341d in QtWaylandClient::QWaylandDisplay::flushRequests() () from /usr/lib/libQt5WaylandClient.so.5
#19 0x00007f22132157d0 in doActivate<false> (sender=0x55c6217ff590, signal_index=3, argv=argv@entry=0x7ffdf999e2b0) at kernel/qobject.cpp:3898
#20 0x00007f221320e7a8 in QMetaObject::activate (sender=sender@entry=0x55c6217ff590, m=m@entry=0x7f221347b780 <QSocketNotifier::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffdf999e2b0) at kernel/qobject.cpp:3946
#21 0x00007f2213218e54 in QSocketNotifier::activated (this=this@entry=0x55c6217ff590, _t1=..., _t2=<optimized out>, _t3=...) at .moc/moc_qsocketnotifier.cpp:178
#22 0x00007f22132196a5 in QSocketNotifier::event (this=0x55c6217ff590, e=0x7ffdf999e3c0) at kernel/qsocketnotifier.cpp:302
#23 0x00007f22121489f6 in QApplicationPrivate::notify_helper (this=<optimized out>, receiver=0x55c6217ff590, e=0x7ffdf999e3c0) at kernel/qapplication.cpp:3632
#24 0x00007f22131dd3ba in QCoreApplication::notifyInternal2 (receiver=0x55c6217ff590, event=0x7ffdf999e3c0) at kernel/qcoreapplication.cpp:1064
#25 0x00007f221323867e in socketNotifierSourceDispatch (source=0x55c621808f10) at kernel/qeventdispatcher_glib.cpp:107
#26 0x00007f2210d6202c in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#27 0x00007f2210db5b59 in ?? () from /usr/lib/libglib-2.0.so.0
#28 0x00007f2210d5f781 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#29 0x00007f2213237a15 in QEventDispatcherGlib::processEvents (this=0x55c6217de540, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#30 0x00007f22131dbc3c in QEventLoop::exec (this=this@entry=0x7ffdf999e5d0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69
#31 0x00007f22131e4428 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121
#32 0x00007f2213544d50 in kdemain () from /usr/lib/libkdeinit5_konsole.so
#33 0x00007f2212d77b25 in __libc_start_main () from /usr/lib/libc.so.6
#34 0x000055c61f83705e in ?? ()
[Inferior 1 (process 287413) detached]

Possible duplicates by query: bug 435992, bug 434725, bug 434205, bug 433252, bug 429420.

Reported using DrKonqi
Comment 1 Nicolas Fella 2021-12-14 00:28:54 UTC
*** Bug 438838 has been marked as a duplicate of this bug. ***
Comment 2 Nicolas Fella 2021-12-14 00:29:47 UTC
Sounds like https://bugs.kde.org/show_bug.cgi?id=426293
Comment 3 Nicolas Fella 2021-12-14 00:31:37 UTC
*** Bug 438801 has been marked as a duplicate of this bug. ***
Comment 4 John Doe 2021-12-26 16:17:45 UTC
(In reply to Nicolas Fella from comment #1)
> *** Bug 438838 has been marked as a duplicate of this bug. ***

Actually now i think it might have been an issue related to a substandard physical connection 🤔 once i have upgraded from samsung 226BW, connected with a dp-dvi cable, to a BenQ EW3270UE, connected with dp over usb-c this exact problem has ceased to persist
Comment 5 David Edmundson 2022-01-11 15:14:48 UTC

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