Bug 1889436

Summary: Subpixel font rendering option is stuck in "RGB" value in kcm_fonts
Product: [Fedora] Fedora Reporter: Mikhail Shchemelev <mikhail.schemelev>
Component: plasma-desktopAssignee: KDE SIG <kde-sig>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: 33CC: hygorhernane, jgrulich, kde-sig, me, rdieter, than
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-11-30 16:28:50 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Mikhail Shchemelev 2020-10-19 16:31:08 UTC
Description of problem:

Plasma uses subpixel RGB font rendering by default. You can disable it in plasma font settings by selecting "None" option in subpixel rendering section.
However, while doing that correctly disables subpixel rendering, option itself is stuck and if you go to font settings after that it will show "RGB"

Version-Release number of selected component (if applicable):

Fedora 32, 33
Plasma versions 5.18, 5.19, 5.20 (through copr)

Steps to Reproduce:

1. Open font settings in kde control center
2. Change subpixel rendering option from RGB to None and click Apply
3. Close control center and repeat step 1

Actual results: subpixel font rendering section will show "RGB" value

Expected results: subpixel font rendering section should show previously selected None value

Additional info:

This looks like this bug, reported to KDE bugzilla: https://bugs.kde.org/show_bug.cgi?id=416140
However i have reasons to believe this is Fedora specific, because:
1) Font rendering options is actually applied correctly in my case
2) I can not reproduce the same behaviour on other distributions with KDE  (OpenSUSE, Manjaro, Kubuntu) for specified versions
Could it be some fedora specific static configuration file (in etc?) that makes kcm go haywire?

Comment 1 Ben Cotton 2021-11-04 17:28:05 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Ben Cotton 2021-11-30 16:28:50 UTC
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.