Bug 514138 - Plasmashell crashed after waking up
Summary: Plasmashell crashed after waking up
Status: RESOLVED DUPLICATE of bug 496589
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-crash (other bugs)
Version First Reported In: 6.5.4
Platform: unspecified Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2026-01-04 08:30 UTC by mwstudio4
Modified: 2026-01-05 11:53 UTC (History)
1 user (show)

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


Attachments
New crash information added by DrKonqi (117.46 KB, text/plain)
2026-01-04 08:30 UTC, mwstudio4
Details

Note You need to log in before you can comment on or make changes to this bug.
Description mwstudio4 2026-01-04 08:30:10 UTC
Application: plasmashell (6.5.4)

ApplicationNotResponding [ANR]: false
Qt Version: 6.10.1
Frameworks Version: 6.21.0
Operating System: Linux 6.8.0-90-generic x86_64
Windowing System: Wayland
Distribution: KDE neon User Edition
DrKonqi: 6.5.4 [CoredumpBackend]

-- Information about the crash:
Often crashes after automatically sleep after period of inactivity

The crash can be reproduced every time.

-- Backtrace (Reduced):
#6  __pthread_kill_implementation (no_tid=0, signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:44
#7  __pthread_kill_internal (signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:78
#8  __GI___pthread_kill (threadid=<optimized out>, signo=signo@entry=6) at ./nptl/pthread_kill.c:89
#9  0x000075878dc4527e in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#10 0x000075878dc288ff in __GI_abort () at ./stdlib/abort.c:79
#11 0x000075878e932891 in qAbort () at /usr/src/qt6-base-6.10.1-0zneon+24.04+noble+release+build144/src/corelib/global/qassert.cpp:46
#12 qt_maybe_message_fatal<QString&> (message=..., context=<optimized out>, msgType=QtFatalMsg) at /usr/src/qt6-base-6.10.1-0zneon+24.04+noble+release+build144/src/corelib/global/qlogging.cpp:2166
[...]
#14 0x000075878e933653 in QMessageLogger::fatal (this=this@entry=0x7ffc3028ad80, msg=msg@entry=0x758759bd7bc0 "KWaylandBackend: no output modes available anymore, this seems like a compositor bug") at /usr/src/qt6-base-6.10.1-0zneon+24.04+noble+release+build144/src/corelib/global/qlogging.cpp:901
#15 0x0000758759bc6731 in operator() (__closure=0x5bf69fb18ba0) at /usr/src/libkscreen-4:6.5.4-0zneon+24.04+noble+release+build33/backends/kwayland/waylandoutputdevice.cpp:73
#16 operator() (__closure=<optimized out>) at /usr/include/x86_64-linux-gnu/qt6/QtCore/qobjectdefs_impl.h:116
#20 QtPrivate::QCallableObject<KScreen::WaylandOutputDevice::kde_output_device_v2_mode(kde_output_device_mode_v2*)::<lambda()>, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=<optimized out>, this_=0x5bf69fb18b90, r=<optimized out>, a=<optimized out>, ret=<optimized out>) at /usr/include/x86_64-linux-gnu/qt6/QtCore/qobjectdefs_impl.h:547
#21 0x000075878e89fc89 in QtPrivate::QSlotObjectBase::call (a=0x7ffc3028ae58, r=<optimized out>, this=0x5bf69fb18b90, this=<optimized out>, r=<optimized out>, a=<optimized out>) at /usr/src/qt6-base-6.10.1-0zneon+24.04+noble+release+build144/src/corelib/kernel/qobjectdefs_impl.h:461
#22 doActivate<false> (sender=0x5bf69fb18aa0, signal_index=3, argv=0x7ffc3028ae58) at /usr/src/qt6-base-6.10.1-0zneon+24.04+noble+release+build144/src/corelib/kernel/qobject.cpp:4257
#23 0x000075878e2a8b16 in ffi_call_unix64 () at ../src/x86/unix64.S:104
#24 0x000075878e2a53ef in ffi_call_int (cif=cif@entry=0x7ffc3028b070, fn=<optimized out>, rvalue=<optimized out>, avalue=<optimized out>, closure=closure@entry=0x0) at ../src/x86/ffi64.c:673
#25 0x000075878e2a80be in ffi_call (cif=cif@entry=0x7ffc3028b070, fn=<optimized out>, rvalue=rvalue@entry=0x0, avalue=avalue@entry=0x7ffc3028b140) at ../src/x86/ffi64.c:710


Reported using DrKonqi
Comment 1 mwstudio4 2026-01-04 08:30:11 UTC
Created attachment 188206 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 David Edmundson 2026-01-05 11:53:36 UTC

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