Bug 417587 - Font Setting cannot be saved and font size are defaulted to 6 without any ability to change it.
Summary: Font Setting cannot be saved and font size are defaulted to 6 without any abi...
Status: RESOLVED DUPLICATE of bug 416358
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_fonts (show other bugs)
Version: 5.18.0
Platform: Arch Linux Linux
: NOR major
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-02-13 18:49 UTC by Tyler
Modified: 2020-02-13 20:38 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tyler 2020-02-13 18:49:19 UTC
SUMMARY
The font size on KDE Plasma desktop is shrunk to font size 6 which is barely readable and when entering into Plasma Desktop Setting for Font management to adjust both the force DPI and font size for all fonts, it does not save the settings. The apply button is greyed out when font settings are changed. When re-opening the setting, the settings are back to the original state without any of my modification to the settings. I've also tried restarting the machine upon modifying the setting. I am essentially stuck on font size 6 without any way to change it.

STEPS TO REPRODUCE
1. Open Plasma Desktop Setting
2. Go to Font Management in Setting
3. Adjust Font Size or Forced DPI Setting

OBSERVED RESULT
Apply button greyed out and nothing in the setting is saved.

EXPECTED RESULT
Apply button should not be greyed out and should save the settings upon clicking on apply and the effect should be seen after restarting Plasma Desktop.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux (Latest today) 5.18-1 plasma-meta package
KDE Plasma Version: 5.18
KDE Frameworks Version: 5.67.0
Qt Version: 5.14.1

ADDITIONAL INFORMATION
Prior version 5.17.90 does not have this regression.
Comment 1 Tyler 2020-02-13 19:12:28 UTC
Someone just pointed out that a bug report is already made for this: 416358
Comment 2 Christoph Feck 2020-02-13 20:38:27 UTC

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