Bug 503381

Summary: Plasma Shell and various QML/Qt Quick parts force RGB Subpixel Rendering for fonts, regardless of user-specified Subpixel Rendering setting
Product: [I don't know] kde Reporter: cyangalaxy <skygalaxy19>
Component: generalAssignee: Unassigned bugs <unassigned-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: john.kizer
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: plasma-shell clock with forced RGB anti aliasing, resulting in colour-fringing

Description cyangalaxy 2025-04-26 11:08:31 UTC
Created attachment 180678 [details]
plasma-shell clock with forced RGB anti aliasing, resulting in colour-fringing

SUMMARY
At any UI-scale, except 100%!, various QML-written parts of KDE Plasma (shell, System Settings, KDE apps & third party Qt Quick apps such as Fedora Media Writer) exhibit forced RGB subpixel rendering, regardless of user-specified Subpixel setting.

This is noticable on my BGR monitor as colour-fringing/chromatic abberation.

I've had this issue for at least over a year (Sorry for not creating an issue earlier!). Reproducible on Fedora KDE, OpenSUSE TW, KDE Neon, Kubuntu. Plasma 5 doesn't have this issue.

STEPS TO REPRODUCE
1. Set UI-scale over 100%
2. Adjust Subpixel Rendering (e.g. Off or BGR) and reboot

OBSERVED RESULT
Observe the fact that RGB subpixel rendering is still applied to plasma-shell, Discover & System Settings, etc. Causing colour-fringing/chromatic abberation on Non-RGB monitors, such as BGR or OLED monitors.

EXPECTED RESULT
Qt Quick QML parts & apps also acknowledging the user-specified subpixel font rendering setting.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora KDE, Kubuntu, KDE Neon, OpenSUSE TW
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.13
Qt Version: 6.9

ADDITIONAL INFORMATION
I use a 4K TV with BGR subpixels at 200%. Plasma Wayland with amdgpu driver (RX 6800)
Comment 1 John Kizer 2025-04-27 18:56:36 UTC
Hi - merging this in with an existing bug report for the underlying issue. Thanks!

*** This bug has been marked as a duplicate of bug 501715 ***