Application: (6.3.0) ApplicationNotResponding [ANR]: false Qt Version: 6.8.2 Frameworks Version: 6.10.0 Operating System: Linux 6.13.2 x86_64 Windowing System: Wayland Distribution: NixOS 25.05 (Warbler) DrKonqi: 6.3.0 [CoredumpBackend] -- Information about the crash: When connecting an external display via my Dell dock (a WD19TBS) via the DisplayPort connector, KWin crashes. In the following cases, everything works fine: - The same setup with Plasma 6.2.5 works fine - The same dock with a screen connected via HDMI works fine - The same screen connected directly to the laptop (with usb-c) works fine I have reverted for now, but I can fairly easily switch back if more logs or diagnostics are required. The crash can be reproduced every time. -- Backtrace (Reduced): #5 KWin::DrmProperty::isValid (this=0x108) at /build/kwin-6.3.0/src/backends/drm/drm_property.cpp:153 #6 0x00007f728b7c38be in KWin::DrmPipeline::prepareAtomicPresentation (this=this@entry=0x7f7264006410, commit=commit@entry=0x7f72640031f0, frame=std::shared_ptr<KWin::OutputFrame> (use count 1, weak count 0) = {...}) at /build/kwin-6.3.0/src/backends/drm/drm_pipeline.cpp:182 #7 0x00007f728b7c853d in KWin::DrmPipeline::present (this=0x7f7264006410, frame=std::shared_ptr<KWin::OutputFrame> (use count 1, weak count 0) = {...}) at /nix/store/zs2gq6fkglrd28g1nxlb8waqq37cdc2z-gcc-14-20241116/include/c++/14-20241116/bits/unique_ptr.h:193 #8 0x00007f728b7bcb3e in KWin::DrmOutput::present (this=0x3e1773e0, frame=std::shared_ptr<KWin::OutputFrame> (use count 1, weak count 0) = {...}) at /build/kwin-6.3.0/src/backends/drm/drm_output.cpp:325 #9 0x00007f728b420294 in KWin::WaylandCompositor::composite (this=0x3c01caf0, renderLoop=<optimized out>) at /build/kwin-6.3.0/src/compositor_wayland.cpp:436 Reported using DrKonqi
Created attachment 178377 [details] New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace.
Thank you for the bug report! This issue is already being tracked; marking as a duplicate. *** This bug has been marked as a duplicate of bug 500031 ***
Are we sure this is the same bug as https://bugs.kde.org/show_bug.cgi?id=500031? I tested with version 6.3.2, which supposedly fixes this bug, but I still get the same problem, with exactly the same stacktrace.
You're right, there are two slightly different but related bug with essentially the same backtrace. If it still happens with 6.3.2.1, yours is likely the other one. I'm changing this to a duplicate of that one. It should be fixed in 6.3.3 next week. *** This bug has been marked as a duplicate of bug 500819 ***