| Summary: | On the fonts settings page, the Apply button is enabled, even if there were no changes | ||
|---|---|---|---|
| Product: | [Applications] systemsettings | Reporter: | popov895 <popov895> |
| Component: | kcm_fonts | Assignee: | Plasma Bugs List <plasma-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | bugseforuns, cyril.rossi, hexclover, med.medin.2014, nate, popov895, pveax, signal17, strangealmond |
| Priority: | NOR | Keywords: | regression |
| Version: | 5.18.5 | ||
| Target Milestone: | --- | ||
| Platform: | Neon | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 5.19 | |
| Sentry Crash Report: | |||
| Attachments: | non-default font settings of affected user account | ||
|
Description
popov895
2020-03-23 09:25:02 UTC
Created attachment 127173 [details]
non-default font settings of affected user account
Same problem here after update to Qt 5.14.2.
I have two user accounts on my system, only the one with non-default font settings is affected.
I'm attaching a screenshot showing the font settings of the affected user account.
Operating System: Arch Linux
KDE Plasma Version: 5.18.4
KDE Frameworks Version: 5.68.0
Qt Version: 5.14.2
Additional observations:
This is occurs after you change any of the default fonts.
Also I see in the system log when you navigate away from this setting page:
Warning org.kde.fontinst Connecting to session bus
Failed to register service!
If you hit the defaults button at the bottom of the page, you would think this would go away after it resets the fonts to all the defaults. It does not, the issue persists.
Seems to be caused by Bug 416140. *** This bug has been marked as a duplicate of bug 416140 *** Not actually a duplicate, but also fixed now in Plasma 5.19. *** Bug 420232 has been marked as a duplicate of this bug. *** *** Bug 421211 has been marked as a duplicate of this bug. *** *** Bug 421751 has been marked as a duplicate of this bug. *** Can be reproduced on Plasma 5.18.5 LTS It's fixed in 5.19 What about Plasma 5.18? Is it out of date? As I know, Plasma 5.18 has an LTS status and it will be supported for two years. This bug was reported for Plasma 5.18, so it should be fixed for Plasma 5.18 as well. The same applies to bug 421344 and bug 416510. Otherwise, I see no reason to report bugs and send patches, that will not get into the Plasma version, that I'm using. (In reply to popov895 from comment #11) > What about Plasma 5.18? Is it out of date? Yes, we just released Plasma 5.19. > As I know, Plasma 5.18 has an LTS status and it will be supported for two > years. This bug was reported for Plasma 5.18, so it should be fixed for > Plasma 5.18 as well. The same applies to bug 421344 and bug 416510. That's not really how this works, I'm afraid. Not all bugs are possible to fix in the LTS. For example sometimes fixing a bug requires implementing a new feature ore re-architecting the backend, neither of which are appropriates changes for an LTS release. > Otherwise, I see no reason to report bugs and > send patches, that will not get into the Plasma version, that I'm using. You should consider using the latest released version. :) IMO always using the newest one makes more sense than using the LTS version. In fact, yo already implicitly agree by using KDE Neon, which does not stick to the LTS version and already offers 5.19. Consider upgrading to that. "There is a Plasma 5.18 LTS that will be supported for two years and will have two bugfixes, but don't use it. Use the latest released version." It sounds very strange. I don't like some of the changes made in Plasma 5.19, so I decided to switch to the LTS version. If I send patches for the LTS version, will they be accepted? But of course! :) Please feel free. However you can't stay on 5.18 forever. If there's stuff you don't like in 5.19, please feel free to speak up and help fix the issues you've identified there. We're always open to changes. |