https://bugs.kde.org/show_bug.cgi?id=459286
Zamundaaa <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |UPSTREAM Status|REPORTED |RESOLVED CC| |[email protected] --- Comment #3 from Zamundaaa <[email protected]> --- Relevant lines are: >[ 491.838731] amdgpu 0000:05:00.0: [drm:drm_atomic_check_only] checking >00000000bd3a0560 >[ 491.838737] amdgpu 0000:05:00.0: [drm:drm_atomic_helper_check_modeset] >[CRTC:67:crtc-0] mode changed >[ 491.838742] amdgpu 0000:05:00.0: [drm:drm_atomic_helper_check_modeset] >[CRTC:67:crtc-0] needs all connectors, enable: y, active: y >[ 491.838745] amdgpu 0000:05:00.0: [drm:drm_atomic_add_affected_connectors] >Adding all current connectors for [CRTC:67:crtc-0] to 00000000bd3a0560 >[...] >[ 491.839469] [drm:dm_update_crtc_state [amdgpu]] Mode change not required >for front porch change, setting mode_changed to 0 >[...] >[ 491.839946] amdgpu 0000:05:00.0: [drm:drm_atomic_nonblocking_commit] >committing 00000000bd3a0560 nonblocking amdgpu thinks it doesn't need a modeset to do the commit, and so KWin doesn't do one. Presumably it would actually need a modeset to make your display work properly. We could add a workaround in KWin (always do a modeset if it *might* be needed) but this is a really severe bug and needs to be fixed in amdgpu, so I'd rather not do that. You can put KWIN_DRM_NO_AMS=1 into /etc/environment as a temporary workaround though, with that KWin will always do a full modeset. Please report it at https://gitlab.freedesktop.org/drm/amd/-/issues and link the issue here; I'll add more information there as needed. -- You are receiving this mail because: You are watching all bug changes.
