Bug 511280 - Crash after sleep mode when display configuration changed
Summary: Crash after sleep mode when display configuration changed
Status: RESOLVED DUPLICATE of bug 511230
Alias: None
Product: kwin
Classification: Plasma
Component: generic-crash (other bugs)
Version First Reported In: 6.5.0
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2025-10-28 18:47 UTC by Fernando
Modified: 2025-10-28 19:37 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
New crash information added by DrKonqi (77.98 KB, text/plain)
2025-10-28 18:47 UTC, Fernando
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Fernando 2025-10-28 18:47:19 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-arch1-1 x86_64
Windowing System: Wayland
Distribution: Arch Linux
DrKonqi: 6.5.0 [CoredumpBackend]

-- Information about the crash:
After my day, I left my laptop to go to sleep mode by inactivity. After doing some chores, I got back to my laptop and unplugged HDMI, power and my USB 1.0 keyboard. After doing some more tasks I opened my laptop, ready to resume some tasks again. It presented me this crash reporter and a firefox crash reporter. The firefox crash reporter showed a message from that the grapics card went away. Maybe during unplugging of the laptop I bumped a key, so it tried to start without any screens to display on, and such applications that required the graphics card crashed

The crash does not seem to be 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  0x00007f485f298a13 in __pthread_kill_internal (threadid=<optimized out>, signo=6) at pthread_kill.c:89
#7  0x00007f485f23e410 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#8  0x00007f485f22557a in __GI_abort () at abort.c:77
#9  0x00007f485fa9348c 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 0x00007f485fa94250 in QMessageLogger::fatal (this=<optimized out>, msg=0x7f4862a7de86 "unknown active output") at /usr/src/debug/qt6-base/qtbase/src/corelib/global/qlogging.cpp:901
#13 0x00007f486255c8fa in ??? () at /usr/lib/libkwin.so.6
#14 0x00007f486257b5ce in KWin::Workspace::takeActivity(KWin::Window*, QFlags<KWin::Workspace::ActivityFlag>) () at /usr/lib/libkwin.so.6
#15 0x00007f486257bbdb in KWin::Workspace::activateNextWindow(KWin::Window*) () at /usr/lib/libkwin.so.6
#16 0x00007f48628106aa in KWin::Workspace::removeWaylandWindow(KWin::Window*) () at /usr/lib/libkwin.so.6
#17 0x00007f485fbd716f in QtPrivate::QSlotObjectBase::call (this=0x5559c35c8ec0, r=0x5559c34856e0, a=0x7ffc2ef64220, this=<optimized out>, r=<optimized out>, a=<optimized out>) at /usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qobjectdefs_impl.h:461
#18 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
#19 0x00007f48627d9e0b in KWin::WaylandServer::windowRemoved(KWin::Window*) () at /usr/lib/libkwin.so.6
#20 0x00007f486269bd67 in ??? () at /usr/lib/libkwin.so.6
#21 0x00007f485fbd716f in QtPrivate::QSlotObjectBase::call (this=0x5559c3ce4270, r=0x5559c3f13f40, a=0x7ffc2ef64390, this=<optimized out>, r=<optimized out>, a=<optimized out>) at /usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qobjectdefs_impl.h:461


Reported using DrKonqi
This report was filed against 'kde' because the product 'kwin' could not be located in Bugzilla. Add it to drkonqi's mappings file!
Comment 1 Fernando 2025-10-28 18:47:20 UTC
Created attachment 186266 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 TraceyC 2025-10-28 19:37:00 UTC
Thank you for the bug report. Based on the backtrace this looks like a duplicate of bug 511230. 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 511230 ***