Summary: | "Preffer color accuracy" Freezes plasma when set and bricks it | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Greeniac <quarro> |
Component: | colour-management | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | develop, kitt997, xaver.hugl |
Priority: | NOR | ||
Version First Reported In: | git-stable-Plasma/6.3 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Greeniac
2025-02-12 21:27:07 UTC
Can confirm since a recent Plasma update to 6.3.0 The following gets spat out in journalctl. ``` Feb 12 23:10:26 Arch kwin_wayland[1563]: kwin_wayland_drm: Atomic modeset commit failed! Invalid argument Feb 12 23:10:26 Arch kwin_wayland[1563]: kwin_core: Applying output config failed! Feb 12 23:10:26 Arch kwin_wayland[1563]: kwin_core: Applying output config failed! ``` Operating System: Arch Linux KDE Plasma Version: 6.3.0 KDE Frameworks Version: 6.10.0 Qt Version: 6.8.2 Kernel Version: 6.13.2-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 580 Series Could you please get a drm debug log for the issue? How to do that is explained at https://invent.kde.org/plasma/kwin/-/wikis/Debugging/Debugging-DRM-issues Most likely this is the GPU driver not handling the increased resolution properly, but I'd like to be sure. I can also confirm this. Just updated plasma to 6.3, on Fedora 41, and setting color accuracy to "prefer accuracy" completely breaks DE rendering. A pile of pixels is randomly layed out on the screen, depending on the specific moment I can spot some parts of the UI. Also, luckily for me I had a second screen to plug in and revert the setting, otherwise I would have been cooked. - I wasn't able to find where this settings is stored, in order to revert it from tty - the auto revert functionality is not active for this setting, even though it would have been crucial. *** This bug has been marked as a duplicate of bug 499789 *** |