Bug 419762 - kactivitymanagerd crashed on Wayland when I swtiched to "Extend to left" multi-monitor mode
Summary: kactivitymanagerd crashed on Wayland when I swtiched to "Extend to left" mult...
Status: RESOLVED DUPLICATE of bug 419749
Alias: None
Product: kactivitymanagerd
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Neon Linux
: NOR crash
Target Milestone: ---
Assignee: Ivan Čukić
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-04-06 20:54 UTC by Patrick Silva
Modified: 2020-04-06 21:04 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick Silva 2020-04-06 20:54:37 UTC
I was using Wayland session with an external monitor connected to hdmi port, then I switched from "Swith to external monitor" to "Extend to left" multi-monitor mode and plasma shown 4 crash notifications at the same time: power devil, discover notifier, policykit kde agent and this one.

EXPECTED RESULT
no crash

SOFTWARE/OS VERSIONS
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.18.80
KDE Frameworks Version: 5.69.0
Qt Version: 5.14.1

Application: kactivitymanagerd (kactivitymanagerd), signal: Segmentation fault
Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7f7d3015cc80 (LWP 1206))]
[KCrash Handler]
#7  QtWayland::wl_output::handle_geometry (data=0x55796b555c30, object=0x55796b555cd0, x=1920, y=0, physical_width=310, physical_height=170, subpixel=0, make=0x55796b569e20 "LG Display", model=0x55796b569e30 "LVDS-1-desconhecido", transform=0) at qwayland-wayland.cpp:2212
#8  0x00007f7d24d4bdae in ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
#9  0x00007f7d24d4b71f in ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
#10 0x00007f7d253dae24 in wl_closure_invoke (closure=closure@entry=0x55796b569d30, flags=flags@entry=1, target=<optimized out>, target@entry=0x55796b555cd0, opcode=opcode@entry=0, data=<optimized out>) at ../src/connection.c:1006
#11 0x00007f7d253d7659 in dispatch_event (display=display@entry=0x55796b54e560, queue=<optimized out>) at ../src/wayland-client.c:1427
#12 0x00007f7d253d8b24 in dispatch_queue (queue=0x55796b54e628, display=0x55796b54e560) at ../src/wayland-client.c:1573
#13 wl_display_dispatch_queue_pending (display=0x55796b54e560, queue=0x55796b54e628) at ../src/wayland-client.c:1815
#14 0x00007f7d253d8b7c in wl_display_dispatch_pending (display=<optimized out>) at ../src/wayland-client.c:1878
#15 0x00007f7d2584f642 in QtWaylandClient::QWaylandDisplay::flushRequests (this=0x55796b54e3c0) at qwaylanddisplay.cpp:208
#16 0x00007f7d2d75edc9 in doActivate<false> (sender=0x55796b57aec0, signal_index=3, argv=0x7ffd02fd6e90) at kernel/qobject.cpp:3882
#17 0x00007f7d2d7598a2 in QMetaObject::activate (sender=sender@entry=0x55796b57aec0, m=m@entry=0x7f7d2dbf1bc0 <QSocketNotifier::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffd02fd6e90) at kernel/qobject.cpp:3930
#18 0x00007f7d2d7625c8 in QSocketNotifier::activated (this=this@entry=0x55796b57aec0, _t1=<optimized out>, _t2=...) at .moc/moc_qsocketnotifier.cpp:141
#19 0x00007f7d2d762982 in QSocketNotifier::event (this=0x55796b57aec0, e=0x7ffd02fd7160) at kernel/qsocketnotifier.cpp:266
#20 0x00007f7d2eda28bc in QApplicationPrivate::notify_helper (this=this@entry=0x55796b5456e0, receiver=receiver@entry=0x55796b57aec0, e=e@entry=0x7ffd02fd7160) at kernel/qapplication.cpp:3684
#21 0x00007f7d2eda9ac0 in QApplication::notify (this=0x7ffd02fd73f0, receiver=0x55796b57aec0, e=0x7ffd02fd7160) at kernel/qapplication.cpp:3430
#22 0x00007f7d2d723db8 in QCoreApplication::notifyInternal2 (receiver=0x55796b57aec0, event=0x7ffd02fd7160) at kernel/qcoreapplication.cpp:1092
#23 0x00007f7d2d723f8e in QCoreApplication::sendEvent (receiver=<optimized out>, event=event@entry=0x7ffd02fd7160) at kernel/qcoreapplication.cpp:1487
#24 0x00007f7d2d783c88 in socketNotifierSourceDispatch (source=0x55796b5ac7f0) at kernel/qeventdispatcher_glib.cpp:107
#25 0x00007f7d29c4c417 in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#26 0x00007f7d29c4c650 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#27 0x00007f7d29c4c6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#28 0x00007f7d2d7830bc in QEventDispatcherGlib::processEvents (this=0x55796b55d270, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#29 0x00007f7d2d72263a in QEventLoop::exec (this=this@entry=0x7ffd02fd7380, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225
#30 0x00007f7d2d72bdb0 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1400
#31 0x000055796af0bc95 in ?? ()
#32 0x00007f7d2cd29b97 in __libc_start_main (main=0x55796af0bbf0, argc=1, argv=0x7ffd02fd7528, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffd02fd7518) at ../csu/libc-start.c:310
#33 0x000055796af0bd8a in _start ()
Comment 1 David Edmundson 2020-04-06 21:04:20 UTC
It's in QtWayland, lets just have the one bug report

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