Bug 505433

Summary:	kwin_wayland crash after dell dock connecting/disconnecting
Product:	[Plasma] kwin	Reporter:	kevinleroy
Component:	general	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	nate
Priority:	NOR	Keywords:	drkonqi
Version First Reported In:	6.3.5
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	New crash information added by DrKonqi

Description kevinleroy 2025-06-10 14:35:14 UTC

Application: kwin_wayland (6.3.5)

ApplicationNotResponding [ANR]: false
Qt Version: 6.9.0
Frameworks Version: 6.14.0
Operating System: Linux 6.14.9-300.fc42.x86_64 x86_64
Windowing System: Wayland
Distribution: "Fedora Linux 42 (KDE Plasma Desktop Edition)"
DrKonqi: 6.3.5 [CoredumpBackend]

-- Information about the crash:
Regullary crash from kwin_wayland after dell dock connecting/disconnecting with some screens.
All xwayland apps crash with sig_segv error.

The crash can be reproduced every time.

-- Backtrace (Reduced):
#5  0x00007ffa4f35d0eb in KWin::DrmOutput::cursorLayer() const () from /lib64/libkwin.so.6
#7  0x00007ffa4c36033a in QtPrivate::QSlotObjectBase::call (this=0x5600568ab170, r=0x560056ea7f90, a=0x7ffffbfed2f0) at /usr/src/debug/qt6-qtbase-6.9.0-2.fc42.x86_64/src/corelib/kernel/qobjectdefs_impl.h:461
#8  doActivate<false> (sender=0x560054d7f050, signal_index=3, argv=0x7ffffbfed2f0) at /usr/src/debug/qt6-qtbase-6.9.0-2.fc42.x86_64/src/corelib/kernel/qobject.cpp:4138
#9  0x00007ffa4f08e7f7 in KWin::Cursors::currentCursorChanged(KWin::Cursor*) () from /lib64/libkwin.so.6
#10 0x00007ffa4c36033a in QtPrivate::QSlotObjectBase::call (this=0x560054cacbe0, r=0x560054d7f050, a=0x7ffffbfed398) at /usr/src/debug/qt6-qtbase-6.9.0-2.fc42.x86_64/src/corelib/kernel/qobjectdefs_impl.h:461


Reported using DrKonqi

Comment 1 kevinleroy 2025-06-10 14:35:15 UTC

Created attachment 182146 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.

Comment 2 Nate Graham 2025-06-10 14:45:29 UTC


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