https://bugs.kde.org/show_bug.cgi?id=515129
Bug ID: 515129
Summary: Plasmashell Crashes With Monitor's KVM Switch
Classification: Plasma
Product: plasmashell
Version First 6.5.5
Reported In:
Platform: CachyOS
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: generic-crash
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: 1.0
Application: plasmashell (6.5.5)
ApplicationNotResponding [ANR]: false
Qt Version: 6.10.1
Frameworks Version: 6.22.0
Operating System: Linux 6.18.6-2-cachyos x86_64
Windowing System: Wayland
Distribution: CachyOS
DrKonqi: 6.5.5 [CoredumpBackend]
-- Information about the crash:
The monitor I have, an Asus PG32UCDM, has a built-in KVM switch with a keyboard
and mouse hooked up to it. Displayport is being used for my Linux desktop. When
I attach my work laptop running Windows 11 to the USB-C connection and work on
it for an extended period of time, switching back to displayport and my Linux
desktop causes the display to detect no signal from the RTX 4090. To remedy
this, I have to unplug the displayport cable from the monitor and then reinsert
it again to get it to detect a signal from the GPU. Doing so sometimes crashes
the Plasmashell.
System Details:
Operating System: CachyOS Linux
KDE Plasma Version: 6.5.5
KDE Frameworks Version: 6.22.0
Qt Version: 6.10.1
Kernel Version: 6.18.6-2-cachyos (64-bit)
Graphics Platform: Wayland
Processors: 32 × AMD Ryzen 9 5950X 16-Core Processor
Memory: 96 GiB of RAM (94.2 GiB usable)
Graphics Processor: NVIDIA GeForce RTX 4090
Manufacturer: ASUS
The crash can be reproduced sometimes.
-- Backtrace (Reduced):
#7 0x00007f51f569379f in qAbort () at
/usr/src/debug/qt6-base/qtbase/src/corelib/global/qassert.cpp:46
#8 qt_maybe_message_fatal<QString&> (msgType=QtFatalMsg, context=<optimized
out>, message=...) at
/usr/src/debug/qt6-base/qtbase/src/corelib/global/qlogging.cpp:2166
[...]
#10 0x00007f51f56946bb in QMessageLogger::fatal (this=<optimized out>,
msg=0x7f51c8049760 "KWaylandBackend: no output modes available anymore, this
seems like a compositor bug") at
/usr/src/debug/qt6-base/qtbase/src/corelib/global/qlogging.cpp:901
#11 0x00007f51c8037156 in operator() () at
/usr/src/debug/libkscreen/libkscreen-6.5.5/backends/kwayland/waylandoutputdevice.cpp:73
#12 operator() () at /usr/include/qt6/QtCore/qobjectdefs_impl.h:116
#14 call () at /usr/include/qt6/QtCore/qobjectdefs_impl.h:115
#15 call<QtPrivate::List<>, void> () at
/usr/include/qt6/QtCore/qobjectdefs_impl.h:337
#16 impl () at /usr/include/qt6/QtCore/qobjectdefs_impl.h:547
#17 0x00007f51f57eb3d6 in QtPrivate::QSlotObjectBase::call
(this=0x556af6960380, r=<optimized out>, a=0x7ffc9f2495a8, 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:4257
#19 0x00007f51f772d2ee in ffi_call_unix64 () at ../src/x86/unix64.S:104
#20 0x00007f51f77299f8 in ffi_call_int () at ../src/x86/ffi64.c:676
#21 0x00007f51f772c6ce in ffi_call () at ../src/x86/ffi64.c:713
#22 0x00007f51f844847a in wl_closure_invoke () at
../wayland-1.24.0/src/connection.c:1241
#23 0x00007f51f84492e9 in dispatch_event () at
../wayland-1.24.0/src/wayland-client.c:1707
#24 0x00007f51f84496bb in dispatch_queue () at
../wayland-1.24.0/src/wayland-client.c:1853
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
