Application: org_kde_powerdevil (5.24.1) Qt Version: 5.15.2 Frameworks Version: 5.90.0 Operating System: Linux 5.16.8-1-default x86_64 Windowing System: Wayland Distribution: "openSUSE Tumbleweed" DrKonqi: 5.24.1 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: After i turn my Main (Primary) Monitor off, then back on again, i get the small KDE window 'KDE - Devil Power Management' has crahsed The crash can be reproduced every time. -- Backtrace: Application: KDE Power Management System (org_kde_powerdevil), signal: Segmentation fault Content of s_kcrashErrorMessage: std::unique_ptr<char []> = {get() = <optimized out>} [KCrash Handler] #6 0x00007f7e8fe3a54a in QtWayland::wl_output::handle_done(void*, wl_output*) (data=0x55c8f8d096e0, object=0x55c8f8d57ee0) at qwayland-wayland.cpp:2247 #7 0x00007f7e8fd8d572 in ffi_call_unix64 () at ../src/x86/unix64.S:105 #8 0x00007f7e8fd8a296 in ffi_call_int (cif=<optimized out>, fn=<optimized out>, rvalue=<optimized out>, avalue=<optimized out>, closure=<optimized out>) at ../src/x86/ffi64.c:672 #9 0x00007f7e912c09c0 in wl_closure_invoke (closure=closure@entry=0x7f7e8000c760, target=<optimized out>, target@entry=0x55c8f8d57ee0, opcode=opcode@entry=2, data=<optimized out>, flags=<optimized out>) at ../src/connection.c:1025 #10 0x00007f7e912c1103 in dispatch_event (display=display@entry=0x55c8f8cc4c50, queue=0x55c8f8cc4d20, queue=<optimized out>) at ../src/wayland-client.c:1583 #11 0x00007f7e912c12dc in dispatch_queue (queue=0x55c8f8cc4d20, display=0x55c8f8cc4c50) at ../src/wayland-client.c:1729 #12 wl_display_dispatch_queue_pending (display=0x55c8f8cc4c50, queue=0x55c8f8cc4d20) at ../src/wayland-client.c:1971 #13 0x00007f7e8fe12caa in QtWaylandClient::QWaylandDisplay::flushRequests() (this=<optimized out>) at qwaylanddisplay.cpp:253 #14 0x00007f7e93a8c48e in QObject::event(QEvent*) (this=0x55c8f8cc0800, e=0x7f7e88008380) at kernel/qobject.cpp:1314 #15 0x00007f7e93a5fe1a in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x55c8f8cc0800, event=0x7f7e88008380) at kernel/qcoreapplication.cpp:1064 #16 0x00007f7e93a62e57 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (receiver=0x0, event_type=0, data=0x55c8f8cb8e30) at kernel/qcoreapplication.cpp:1821 #17 0x00007f7e93ab7cd3 in postEventSourceDispatch(GSource*, GSourceFunc, gpointer) (s=s@entry=0x55c8f8cc3460) at kernel/qeventdispatcher_glib.cpp:277 #18 0x00007f7e918f2d5f in g_main_dispatch (context=0x55c8f8ccf730) at ../glib/gmain.c:3381 #19 g_main_context_dispatch (context=0x55c8f8ccf730) at ../glib/gmain.c:4099 #20 0x00007f7e918f30e8 in g_main_context_iterate (context=context@entry=0x55c8f8ccf730, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../glib/gmain.c:4175 #21 0x00007f7e918f319f in g_main_context_iteration (context=0x55c8f8ccf730, may_block=1) at ../glib/gmain.c:4240 #22 0x00007f7e93ab7354 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x55c8f8cc6620, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #23 0x00007f7e93a5e81b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7ffc18e9a810, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #24 0x00007f7e93a66af0 in QCoreApplication::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #25 0x00007f7e93f4625c in QGuiApplication::exec() () at kernel/qguiapplication.cpp:1867 #26 0x000055c8f7416fec in main(int, char**) (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/powerdevil5-5.24.1-1.1.x86_64/daemon/powerdevilapp.cpp:178 [Inferior 1 (process 1805) detached] Possible duplicates by query: bug 419756, bug 419749, bug 391109, bug 386166, bug 345618. Reported using DrKonqi
This is for an Intel Desktop PC, not a laptop
*** This bug has been marked as a duplicate of bug 431388 ***
(In reply to Nicolas Fella from comment #2) > > *** This bug has been marked as a duplicate of bug 431388 *** Isn't this rather a duplicate of bug #451028 and isn't also bug #431388 rather a duplicate bug #451028, too, when comparing the stacktraces?