[kwin] [Bug 509377] Kwin crash after sleep/suspend

TraceyC bugzilla_noreply at kde.org
Tue Sep 16 01:51:37 BST 2025


https://bugs.kde.org/show_bug.cgi?id=509377

TraceyC <kdedev at tlcnet.info> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kdedev at tlcnet.info
          Component|general                     |generic-crash
            Product|kde                         |kwin
      Version First|unspecified                 |6.4.4
        Reported In|                            |
           Assignee|unassigned-bugs at kde.org     |kwin-bugs-null at kde.org

--- Comment #2 from TraceyC <kdedev at tlcnet.info> ---
Searchable backtrace

Thread 1 (Thread 0x7f43bd176b80 (LWP 153169)):
[KCrash Handler]
#5  0x00007f43c6598569 in
KWin::ColorManagementOutputV1::ColorManagementOutputV1 (this=0x56449e8462e0,
client=<optimized out>, id=<optimized out>, version=<optimized out>,
output=0x0) at
/usr/src/debug/kwin-6.4.4-1.fc42.x86_64/src/wayland/colormanagement_v1.cpp:580
#6  KWin::ColorManagerV1::wp_color_manager_v1_get_output (this=<optimized out>,
resource=<optimized out>, id=<optimized out>, output=<optimized out>) at
/usr/src/debug/kwin-6.4.4-1.fc42.x86_64/src/wayland/colormanagement_v1.cpp:63
#7  0x00007f43c0f8b056 in ffi_call_unix64 () at ../src/x86/unix64.S:104
#8  0x00007f43c0f86d08 in ffi_call_int (cif=cif at entry=0x7ffebc2db730,
fn=fn at entry=0x7f43c66afd30
<QtWaylandServer::wp_color_manager_v1::handle_get_output(wl_client*,
wl_resource*, unsigned int, wl_resource*)>, rvalue=<optimized out>,
rvalue at entry=0x0, avalue=avalue at entry=0x7ffebc2db800,
closure=closure at entry=0x0) at ../src/x86/ffi64.c:673
#9  0x00007f43c0f8970e in ffi_call (cif=cif at entry=0x7ffebc2db730,
fn=0x7f43c66afd30
<QtWaylandServer::wp_color_manager_v1::handle_get_output(wl_client*,
wl_resource*, unsigned int, wl_resource*)>, rvalue=rvalue at entry=0x0,
avalue=avalue at entry=0x7ffebc2db800) at ../src/x86/ffi64.c:710
#10 0x00007f43c2d88440 in wl_closure_invoke
(closure=closure at entry=0x5644a02990f0, target=<optimized out>,
target at entry=0x5644a01917a0, opcode=opcode at entry=1, data=<optimized out>,
data at entry=0x5644a01edf60, flags=2) at ../src/connection.c:1241
#11 0x00007f43c2d8daa0 in wl_client_connection_data (fd=<optimized out>,
mask=<optimized out>, data=<optimized out>) at ../src/wayland-server.c:483
#12 0x00007f43c2d8bf42 in wl_event_loop_dispatch (loop=0x56449e614e20,
timeout=<optimized out>) at ../src/event-loop.c:1059
#13 0x00007f43c65a4c29 in KWin::Display::dispatchEvents (this=<optimized out>)
at /usr/src/debug/kwin-6.4.4-1.fc42.x86_64/src/wayland/display.cpp:138
#14 0x00007f43c36217ba in QtPrivate::QSlotObjectBase::call
(this=0x56449f8161c0, r=0x56449e619780, a=0x7ffebc2dbe10) at
/usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/kernel/qobjectdefs_impl.h:461
#15 doActivate<false> (sender=0x56449f86d190, signal_index=3,
argv=argv at entry=0x7ffebc2dbe10) at
/usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/kernel/qobject.cpp:4146
#16 0x00007f43c3618089 in QMetaObject::activate
(sender=sender at entry=0x56449e5b6990, m=m at entry=0x7f43c3b5ff00,
local_signal_index=local_signal_index at entry=0, argv=argv at entry=0x7ffebc2dbe10)
at
/usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/kernel/qobject.cpp:4206
#17 0x00007f43c3630593 in QMetaObject::activate<void, QSocketDescriptor,
QSocketNotifier::Type, QSocketNotifier::QPrivateSignal> (sender=0x56449e5b6990,
mo=0x7f43c3b5ff00, local_signal_index=0, ret=0x0) at
/usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/kernel/qobjectdefs.h:306
#18 QSocketNotifier::activated (this=this at entry=0x56449f86d190, _t1=...,
_t2=<optimized out>, _t3=...) at
/usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/redhat-linux-build/src/corelib/Core_autogen/include/moc_qsocketnotifier.cpp:161
#19 0x00007f43c3630d6b in QSocketNotifier::event (this=0x56449f86d190,
e=<optimized out>) at
/usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/kernel/qsocketnotifier.cpp:327
#20 0x00007f43c487297f in QApplicationPrivate::notify_helper (this=<optimized
out>, receiver=0x56449f86d190, e=0x7ffebc2dbf60) at
/usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/widgets/kernel/qapplication.cpp:3303
#21 0x00007f43c35b5f38 in QCoreApplication::notifyInternal2
(receiver=0x56449f86d190, event=0x7ffebc2dbf60) at
/usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/kernel/qcoreapplication.cpp:1106
#22 0x00007f43c35b619d in QCoreApplication::sendEvent (receiver=<optimized
out>, event=<optimized out>) at
/usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/kernel/qcoreapplication.cpp:1546
#23 0x00007f43c3784447 in QEventDispatcherUNIXPrivate::activateSocketNotifiers
(this=this at entry=0x56449e5b68f0) at
/usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/kernel/qeventdispatcher_unix.cpp:254
#24 0x00007f43c3784d79 in QEventDispatcherUNIX::processEvents (this=<optimized
out>, flags=...) at
/usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/kernel/qeventdispatcher_unix.cpp:470
#25 0x00007f43c4330442 in QUnixEventDispatcherQPA::processEvents
(this=<optimized out>, flags=...) at
/usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/gui/platform/unix/qunixeventdispatcher.cpp:27
#26 0x00007f43c35c3b03 in QEventLoop::exec (this=this at entry=0x7ffebc2dc130,
flags=..., flags at entry=...) at
/usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/global/qflags.h:77
#27 0x00007f43c35bf419 in QCoreApplication::exec () at
/usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/kernel/qcoreapplication.cpp:1449
#28 0x00007f43c3d2dbad in QGuiApplication::exec () at
/usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/gui/kernel/qguiapplication.cpp:1986
#29 0x00007f43c48728e9 in QApplication::exec () at
/usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/widgets/kernel/qapplication.cpp:2570
#30 0x000056447546f6db in main (argc=<optimized out>, argv=<optimized out>) at
/usr/src/debug/kwin-6.4.4-1.fc42.x86_64/src/main_wayland.cpp:635

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the Unassigned-bugs mailing list