Bug 511289

Summary: Crash after unlocking screen
Product: [Plasma] kwin Reporter: dino
Component: generic-crashAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: crash CC: kdedev
Priority: NOR Keywords: drkonqi
Version First Reported In: 6.5.0   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report: https://crash-reports.kde.org/organizations/kde/issues/281430/events/408efdba8d02403f813d1d13f69fa4ca/
Attachments: New crash information added by DrKonqi

Description dino 2025-10-28 20:11:33 UTC
Application: kwin_wayland (6.5.0)

ApplicationNotResponding [ANR]: false
Qt Version: 6.10.0
Frameworks Version: 6.19.0
Operating System: Linux 6.17.5-zen1-1-zen x86_64
Windowing System: Wayland
Distribution: "Arch Linux"
DrKonqi: 6.5.0 [CoredumpBackend]

-- Information about the crash:
This crash happens often after unlocking the screen. After unlock, all I get is error messages from all the crashed programs, probably caused by kwin crashing.
The crash might actually while the screen is locked. From previous logs it seemed like it has something to do with something in powerdevil trying to reference a monitor that isn't there (because it's turned off while I lock the screen?).
One of my monitors starts slow and I also sometimes had an issue with one of the screens being blank after initial startup. This is solved by turning the slower monitor off and then back on.

The crash can be reproduced sometimes.

-- Backtrace (Reduced):
#5  __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#6  0x00007fe6d7698a13 in __pthread_kill_internal (threadid=<optimized out>, signo=6) at pthread_kill.c:89
#7  0x00007fe6d763e410 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#8  0x00007fe6d762557a in __GI_abort () at abort.c:77
#9  0x00007fe6d7e9348c in qAbort () at /usr/src/debug/qt6-base/qtbase/src/corelib/global/qassert.cpp:46
#10 qt_maybe_message_fatal<QString&> (msgType=QtFatalMsg, context=<optimized out>, message=...) at /usr/src/debug/qt6-base/qtbase/src/corelib/global/qlogging.cpp:2165
[...]
#12 0x00007fe6d7e94250 in QMessageLogger::fatal (this=this@entry=0x7fff1c32e9d0, msg=msg@entry=0x7fe6dae7de86 "unknown active output") at /usr/src/debug/qt6-base/qtbase/src/corelib/global/qlogging.cpp:901
#13 0x00007fe6da95c8fa in KWin::Workspace::setActiveOutput (this=<optimized out>, output=<optimized out>) at /usr/src/debug/kwin/kwin-6.5.0/src/workspace.cpp:2441
#14 KWin::Workspace::setActiveOutput (this=<optimized out>, output=<optimized out>) at /usr/src/debug/kwin/kwin-6.5.0/src/workspace.cpp:2438
#15 0x00007fe6da97b5ce in KWin::Workspace::takeActivity (this=0x56260b0fc100, window=<optimized out>, flags=...) at /usr/src/debug/kwin/kwin-6.5.0/src/activation.cpp:423
#16 0x00007fe6da97b865 in KWin::Workspace::requestFocus (this=<optimized out>, window=<optimized out>, force=<optimized out>) at /usr/include/qt6/QtCore/qflags.h:77
#17 0x00007fe6da97bbdb in KWin::Workspace::activateNextWindow (this=0x56260b0fc100, window=0x56260bd213c0) at /usr/src/debug/kwin/kwin-6.5.0/src/activation.cpp:516
#18 0x00007fe6dac106aa in KWin::Workspace::removeWaylandWindow (this=0x56260b0fc100, window=0x56260bd213c0) at /usr/src/debug/kwin/kwin-6.5.0/src/workspace.cpp:813
#19 0x00007fe6d7fd716f in QtPrivate::QSlotObjectBase::call (this=0x56260b206890, r=0x56260b0fc100, a=0x7fff1c32ec50, this=<optimized out>, r=<optimized out>, a=<optimized out>) at /usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qobjectdefs_impl.h:461
#20 doActivate<false> (sender=<optimized out>, signal_index=<optimized out>, argv=<optimized out>) at /usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qobject.cpp:4255
[...]
#22 KWin::WaylandServer::windowRemoved (this=<optimized out>, _t1=<optimized out>) at /usr/src/debug/kwin/build/src/kwin_autogen/include/moc_wayland_server.cpp:155


Reported using DrKonqi
Comment 1 dino 2025-10-28 20:11:34 UTC
Created attachment 186269 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 TraceyC 2025-10-28 21:52:57 UTC
Thank you for the bug report. Based on the backtrace this looks like a duplicate of bug 495702. Please follow that report if you would like updates on the progress of this issue.

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