https://bugs.kde.org/show_bug.cgi?id=502216
Bug ID: 502216
Summary: Content on DP-connected display freezes when twiddling
with Night Light
Classification: Plasma
Product: kwin
Version: 6.3.3
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: kwin-bugs-n...@kde.org
Reporter: sir.ferdek+...@gmail.com
Target Milestone: ---
Application: kwin_wayland (6.3.3)
ApplicationNotResponding [ANR]: false
Qt Version: 6.8.2
Frameworks Version: 6.12.0
Operating System: Linux 6.13.5-200.fc41.x86_64 x86_64
Windowing System: Wayland
Distribution: "Aurora (Version: 41.20250323.1 / FROM Fedora Kinoite 41)"
DrKonqi: 6.3.3 [CoredumpBackend]
-- Information about the crash:
Content on DisplayPort-connected display freezes when twiddling with Night
Light. At the same time the system remains responsive (music plays etc) and I
can move my mouse over to another display connected through HDMI.
But let's start from the beginning.
Distribution is Aurora (Fedora immutable based), latest stable as of writing
this report.
GPU is Nvidia GTX970 with Legacy drivers. AFAIK this setup uses Wayland.
I have two monitors connected, one over Display Port with adaptive sync enabled
("legacy" G-Sync, not this latest one) running at 165Hz refresh rate, second
one an old 1080p HDMI monitor with refresh 65Hz.
I wanted to setup Night Light. When changing colour shift through the settings
menu or changing brightness through the taskbar, very soon (like 1-2 seconds
soon) a content on the DP-connected monitor will freeze. System is still
responsive, I am able to move the mouse over to the 2nd HDMI monitor. Even if I
start the NightLight menu on the HDMI monitor and start changing settings, the
DP one will freeze. And by freeze I literally mean freeze - no glitches.
In this state, if I now physically disconnect the DP monitor from the GPU by
unplugging the DP cable, an attached crashdump is produced, plasma restarts and
I get back controll over my PC.
The crash can be reproduced every time.
-- Backtrace (Reduced):
#5 KWin::DrmPipeline::pageFlipped (this=0x564fa6c76c20, timestamp=...) at
/usr/src/debug/kwin-6.3.3-1.fc41.x86_64/src/backends/drm/drm_pipeline.cpp:420
#6 0x00007fe1e80f27d0 in KWin::DrmAtomicCommit::pageFlipped
(this=0x7fe1c0003360, timestamp=...) at
/usr/src/debug/kwin-6.3.3-1.fc41.x86_64/src/backends/drm/drm_commit.cpp:176
#7 0x00007fe1e47ae580 in drmHandleEvent (fd=21, evctx=0x7fffdea5d2c0) at
../xf86drmMode.c:1070
#8 0x00007fe1e80ecb04 in KWin::DrmGpu::dispatchEvents (this=<optimized out>)
at /usr/src/debug/kwin-6.3.3-1.fc41.x86_64/src/backends/drm/drm_gpu.cpp:577
#9 KWin::DrmCommitThread::handlePing (this=0x564fa6d3d0c0) at
/usr/src/debug/kwin-6.3.3-1.fc41.x86_64/src/backends/drm/drm_commit_thread.cpp:399
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
