Bug 419756 - crash when I tried to set "Unify outputs" multi-monitor mode on Wayland
Summary: crash when I tried to set "Unify outputs" multi-monitor mode on Wayland
Status: RESOLVED DUPLICATE of bug 419492
Alias: None
Product: Powerdevil
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
Keywords: drkonqi
Depends on:
Reported: 2020-04-06 19:37 UTC by Patrick Silva
Modified: 2021-02-25 20:58 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Note You need to log in before you can comment on or make changes to this bug.
Description Patrick Silva 2020-04-06 19:37:07 UTC
Application: org_kde_powerdevil (2.0.0)

Qt Version: 5.14.1
Frameworks Version: 5.69.0
Operating System: Linux 5.3.0-45-generic x86_64
Windowing system: Wayland
Distribution: KDE neon Unstable Edition

-- Information about the crash:
- What I was doing when the application crashed:
I was using Wayland session with an external monitor connected to hdmi port.
I tried to set monitor mode to "Unify outputs" mode then Plasma shown notification about powerdevil crash.
kded5 and DiscoverNotifier also crashed at the same time.

-- Backtrace:
Application: KDE Power Management System (org_kde_powerdevil), signal: Segmentation fault
Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7fad72e9bc80 (LWP 1222))]
[KCrash Handler]
#7  0x0000000000000041 in  ()
#8  0x00007fad62711dae in ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
#9  0x00007fad6271171f in ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
#10 0x00007fad62da0e24 in wl_closure_invoke (closure=closure@entry=0x7fad5000b0a0, flags=flags@entry=1, target=<optimized out>, target@entry=0x561bbaed5380, opcode=opcode@entry=1, data=<optimized out>) at ../src/connection.c:1006
#11 0x00007fad62d9d659 in dispatch_event (display=display@entry=0x561bbae33b50, queue=<optimized out>) at ../src/wayland-client.c:1427
#12 0x00007fad62d9eb24 in dispatch_queue (queue=0x561bbae33c18, display=0x561bbae33b50) at ../src/wayland-client.c:1573
#13 0x00007fad62d9eb24 in wl_display_dispatch_queue_pending (display=0x561bbae33b50, queue=0x561bbae33c18) at ../src/wayland-client.c:1815
#14 0x00007fad62d9eb7c in wl_display_dispatch_pending (display=<optimized out>) at ../src/wayland-client.c:1878
#15 0x00007fad63215642 in QtWaylandClient::QWaylandDisplay::flushRequests() (this=0x561bbae339b0) at qwaylanddisplay.cpp:208
#16 0x00007fad7024bdc9 in doActivate<false>(QObject*, int, void**) (sender=0x561bbae8d0d0, signal_index=3, argv=0x7ffc50ab7ee0) at kernel/qobject.cpp:3882
#17 0x00007fad702468a2 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x561bbae8d0d0, m=m@entry=0x7fad706debc0 <QSocketNotifier::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffc50ab7ee0) at kernel/qobject.cpp:3930
#18 0x00007fad7024f5c8 in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) (this=this@entry=0x561bbae8d0d0, _t1=<optimized out>, _t2=...) at .moc/moc_qsocketnotifier.cpp:141
#19 0x00007fad7024f982 in QSocketNotifier::event(QEvent*) (this=0x561bbae8d0d0, e=0x7ffc50ab7fc0) at kernel/qsocketnotifier.cpp:266
#20 0x00007fad70210db8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x561bbae8d0d0, event=0x7ffc50ab7fc0) at kernel/qcoreapplication.cpp:1092
#21 0x00007fad70210f8e in QCoreApplication::sendEvent(QObject*, QEvent*) (receiver=<optimized out>, event=event@entry=0x7ffc50ab7fc0) at kernel/qcoreapplication.cpp:1487
#22 0x00007fad70270c88 in socketNotifierSourceDispatch(GSource*, GSourceFunc, gpointer) (source=0x561bbae91730) at kernel/qeventdispatcher_glib.cpp:107
#23 0x00007fad6a8f7417 in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x00007fad6a8f7650 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x00007fad6a8f76dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#26 0x00007fad702700bc in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x561bbae421b0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#27 0x00007fad7020f63a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7ffc50ab81e0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225
#28 0x00007fad70218db0 in QCoreApplication::exec() () at kernel/qcoreapplication.cpp:1400
#29 0x0000561bba2547ff in  ()
#30 0x00007fad6f816b97 in __libc_start_main (main=0x561bba254640, argc=1, argv=0x7ffc50ab83d8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffc50ab83c8) at ../csu/libc-start.c:310
#31 0x0000561bba25486a in _start ()

Possible duplicates by query: bug 419749, bug 391109, bug 386166, bug 377347, bug 377346.

Reported using DrKonqi
Comment 1 Nate Graham 2021-02-25 20:58:01 UTC

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