Summary: | Changing the kms gamma lut causes synchronization issues on some PCs | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | kocelfc |
Component: | platform-drm | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | REPORTED --- | ||
Severity: | normal | CC: | benjaminesims, dougshaw77, josh, mattyhoffman7, me, nate, nigvul, paul, postix, powerdollkirby, public, sneslink, xaver.hugl |
Priority: | NOR | Keywords: | qt6, regression |
Version: | 6.2.1 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
See Also: | https://bugs.kde.org/show_bug.cgi?id=494959 | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
kocelfc
2024-02-03 19:33:48 UTC
I cannot reproduce, Nightlight is turning on and off smoothly and with no artifacts. Operating System: KDE neon Testing Edition KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.1 Kernel Version: 6.5.0-15-generic (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Core™ i7-9750H CPU @ 2.60GHz Memory: 15.4 GiB of RAM Graphics Processor: AMD Radeon Pro WX 3200 Series Manufacturer: Dell Inc. Product Name: Precision 7540 Same, works for me with my two screens both connected to an Intel HD620 iGPU. Could be a driver issue that is somehow getting exposed now. Also to note: it seems that it's only reproducible on Wayland. X11 is fine. Are you using an ICC profile or HDR? If not, does KWIN_DRM_FORCE_COLOR_MANAGEMENT=1 fix this? (In reply to Zamundaaa from comment #4) > Are you using an ICC profile or HDR? If not, does > KWIN_DRM_FORCE_COLOR_MANAGEMENT=1 fix this? No ICC profiles or HDR. Setting the environment variable seems to make it a lot less reproducible, and I think I can only sometimes see artifacting in the "Night Light on/off" pop up when it appears, but the variable also makes the colors of the taskbar and the applets more intense if "Background Contrast" is enabled in Window Management > Desktop Effects. Haven't noticed if any other areas appear different. Do the glitches go away if you disable blur and/or background contrast effects? (In reply to Zamundaaa from comment #6) > Do the glitches go away if you disable blur and/or background contrast > effects? Still there, I could make a bisect to maybe narrow it down to something. I've tried 5.91.0 and it's still artifacting there. Could you point me to an earlier commit which I can use as a starting point? You could try 5.90.0 first... If that doesn't work, you'd kind of have to bisect it down to 5.27.10. That would be painful though, to say the least.
One other thing you could try is an older kernel, and/or to force memory clocks of your GPU to the maximum with
>echo high > /sys/class/drm/card0/device/power_dpm_force_performance_level
. amdgpu has been plagued by memory clock bugs lately, so it could just be caused by that
Can you still reproduce this on Plasma 6.0.2? (In reply to Zamundaaa from comment #9) > Can you still reproduce this on Plasma 6.0.2? I can indeed. Even with KWIN_DRM_FORCE_COLOR_MANAGEMENT=1? (In reply to Zamundaaa from comment #11) > Even with KWIN_DRM_FORCE_COLOR_MANAGEMENT=1? Even with it. Forcing high memory clocks on the Graphics card is no help either. Can reproduce, went looking for this report since I've been seeing it here. Not reproducible on X11. Might be a radeon issue? Operating System: Artix Linux KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.1-artix1-1 (64-bit) Graphics Platform: X11 Processors: 32 × AMD Ryzen 9 5950X 16-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: AMD Radeon RX 6900 XT Manufacturer: EVGA Corp. Product Name: X570 FTW WIFI *** Bug 485058 has been marked as a duplicate of this bug. *** My bug was marked as a duplicate of this one, but to add, I also have multiple monitors, though I only see the issue when playing games. Can't seem to reproduce anymore with kernel 6.9.1. Can anyone else confirm it's gone for them too? . (In reply to kocelfc from comment #16) > Can't seem to reproduce anymore with kernel 6.9.1. Can anyone else confirm > it's gone for them too? Actually, it still appears when playing a fullscreen video, in games, and in the steam library. I can also confirm that this bug still happens on kernel 6.9.1. *** Bug 487487 has been marked as a duplicate of this bug. *** Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! Marking as retorted, as the bug still persists. I am also having a similar style of visual glitch. Although mine happens while interacting with various parts of the desktop environment. I'm using an ASUS TUF book with a Ryzen 7 7735HS. It has a dual graphics setup between the integrated GPU 680M and a discrete RX 7700S. I'm running Plasma 6.1.0 Let me know if you need more information. glitch/bug still present in 6.1.1/wayland Looks like this is a kernel bug I swapped back to 6.6.36 and seems to go away for me. There's a couple of bug reports in drm right now: https://gitlab.freedesktop.org/drm/amd/-/issues/3388 https://gitlab.freedesktop.org/drm/amd/-/issues/3264 (In reply to Matt from comment #25) > Looks like this is a kernel bug I swapped back to 6.6.36 and seems to go > away for me. There's a couple of bug reports in drm right now: > https://gitlab.freedesktop.org/drm/amd/-/issues/3388 > https://gitlab.freedesktop.org/drm/amd/-/issues/3264 nvm sorry everyone still happening on 6.6 and 6.1 but a lot less noticeable Hi QA/devs, After upgrading to 6.2.1 (Wayland, single screen), I experienced flickering and often a disappearing mouse, as described in: https://www.reddit.com/r/kde/comments/1g4ntqr/621_update_broke_cursor_behaviour/ I tried searching for the bug, but only found this one. Shall I also make a video recording and create a new bug? (Kernel 6.11.4, Arch Linux, Intel/Alder Lake integrated graphics) (In reply to Andrew Rembrandt from comment #27) > Hi QA/devs, > After upgrading to 6.2.1 (Wayland, single screen), I experienced flickering > and often a disappearing mouse, as described in: > https://www.reddit.com/r/kde/comments/1g4ntqr/ > 621_update_broke_cursor_behaviour/ > > I tried searching for the bug, but only found this one. Shall I also make a > video recording and create a new bug? > > (Kernel 6.11.4, Arch Linux, Intel/Alder Lake integrated graphics) This is bug #494829 or #494959 I don't get a smooth transition anymore (it's like three discrete temperature steps now) when enabling/disabling night light on this system: Operating System: Arch Linux KDE Plasma Version: 6.2.1 KDE Frameworks Version: 6.7.0 Qt Version: 6.8.0 Kernel Version: 6.11.4-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 22 × Intel® Core™ Ultra 7 155H Memory: 30.9 GiB of RAM Graphics Processor: Mesa Intel® Arc Manufacturer: LENOVO Product Name: 21KDS00600 System Version: ThinkPad X1 Carbon Gen 12 (In reply to Iyán Méndez Veiga from comment #29) > I don't get a smooth transition anymore (it's like three discrete > temperature steps now) when enabling/disabling night light on this system: That's a different problem from what this bug report is about, please make a separate bug report for that. *** Bug 495246 has been marked as a duplicate of this bug. *** The only possible causes I can see for this are that the kernel 1. presents a buffer before we're done rendering to it 2. tells us the pageflip is done while it's still presenting the buffer, and we end up rendering to it too early 1 is prevented by KWin never giving the kernel any buffer that's still being rendered to, but 2 is possible and would explain why not everyone experiences it - it depends very heavily on timing and GPU speed. *** Bug 495167 has been marked as a duplicate of this bug. *** |