Bug 510917 - Crash on standby
Summary: Crash on standby
Status: RESOLVED DUPLICATE of bug 495702
Alias: None
Product: kwin
Classification: Plasma
Component: general (other bugs)
Version First Reported In: 6.5.0
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2025-10-22 12:49 UTC by Steve Cossette
Modified: 2025-10-22 12:54 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report: https://crash-reports.kde.org/organizations/kde/issues/276762/events/c5112a0641ab44d3b25362f96cc3a016/


Attachments
New crash information added by DrKonqi (96.98 KB, text/plain)
2025-10-22 12:49 UTC, Steve Cossette
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Steve Cossette 2025-10-22 12:49:12 UTC
Application: kwin_wayland (6.5.0)

ApplicationNotResponding [ANR]: false
Qt Version: 6.9.2
Frameworks Version: 6.19.0
Operating System: Linux 6.17.1-300.fc43.x86_64 x86_64
Windowing System: Wayland
Distribution: "Fedora Linux 43 (KDE Plasma Desktop Edition)"
DrKonqi: 6.5.0 [CoredumpBackend]

-- Information about the crash:
To be completely honest, all I did was walk away from the computer for a bit, and when I came back, I got a message from drkonqi that kwin crashed. My computer did go on standby (The screen turned off).

Also note: this is on 6.5.0 using a build on copr, not on official repositories. But the spec files (aka the "recipe" for building the packages) are the same as what they will be in final.

The reporter is unsure if this crash is reproducible.

-- 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  0x00007f5cda480493 in __pthread_kill_internal (threadid=<optimized out>, signo=6) at pthread_kill.c:89
#7  0x00007f5cda42618e in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#8  0x00007f5cda40d6d0 in __GI_abort () at abort.c:77
#9  0x00007f5cdaa1ad5c in qAbort () at /usr/src/debug/qt6-qtbase-6.9.2-1.fc43.x86_64/src/corelib/global/qassert.cpp:46
#10 0x00007f5cdaa6e2f8 in qt_message_fatal<QString&> (context=<optimized out>, message=...) at /usr/src/debug/qt6-qtbase-6.9.2-1.fc43.x86_64/src/corelib/global/qlogging.cpp:2122
[...]
#12 0x00007f5cdaa1c35c in QMessageLogger::fatal (this=<optimized out>, msg=0x7f5cddeab909 "unknown active output") at /usr/src/debug/qt6-qtbase-6.9.2-1.fc43.x86_64/src/corelib/global/qlogging.cpp:883
#14 0x00007f5cdd8627cd in KWin::Workspace::takeActivity(KWin::Window*, QFlags<KWin::Workspace::ActivityFlag>) () at /lib64/libkwin.so.6
#15 0x00007f5cdd86314a in KWin::Workspace::activateNextWindow(KWin::Window*) () at /lib64/libkwin.so.6
#16 0x00007f5cddae6129 in KWin::Workspace::removeWaylandWindow(KWin::Window*) () at /lib64/libkwin.so.6
#17 0x00007f5cdab65bba in QtPrivate::QSlotObjectBase::call (this=0x5621ec47a5f0, r=0x5621eb8b5270, a=0x7ffe435c8e00) at /usr/src/debug/qt6-qtbase-6.9.2-1.fc43.x86_64/src/corelib/kernel/qobjectdefs_impl.h:461
#18 doActivate<false> (sender=0x5621eb59af20, signal_index=4, argv=0x7ffe435c8e00) at /usr/src/debug/qt6-qtbase-6.9.2-1.fc43.x86_64/src/corelib/kernel/qobject.cpp:4157
#19 0x00007f5cddab1eea in KWin::WaylandServer::windowRemoved(KWin::Window*) () at /lib64/libkwin.so.6
#20 0x00007f5cdd9787bd in KWin::LayerShellV1Window::destroyWindow() () at /lib64/libkwin.so.6
#21 0x00007f5cdab65bba in QtPrivate::QSlotObjectBase::call (this=0x5621ecce67f0, r=0x5621edc4e540, a=0x7ffe435c8f70) at /usr/src/debug/qt6-qtbase-6.9.2-1.fc43.x86_64/src/corelib/kernel/qobjectdefs_impl.h:461
#22 doActivate<false> (sender=0x5621eb8b5270, signal_index=19, argv=0x7ffe435c8f70) at /usr/src/debug/qt6-qtbase-6.9.2-1.fc43.x86_64/src/corelib/kernel/qobject.cpp:4157


Reported using DrKonqi
Comment 1 Steve Cossette 2025-10-22 12:49:13 UTC
Created attachment 186002 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 Steve Cossette 2025-10-22 12:51:36 UTC
FYI this does seem to happen everytime I turn off my screens (META+L). Or at least, it shows on resume.
Comment 3 Zamundaaa 2025-10-22 12:54:15 UTC

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