Summary: | KDE GTK configuration isn't fully initialized on first login, resulting in theming not taking effect for ABRT and Anaconda | ||
---|---|---|---|
Product: | [Applications] systemsettings | Reporter: | Neal Gompa <ngompa13> |
Component: | kcm_style | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | adamw, awilliam, kde, mail, nate |
Priority: | NOR | ||
Version First Reported In: | 6.3.4 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | Diff of the gtk3 and gtk4 config from initial config to manually set config |
Description
Neal Gompa
2025-04-26 15:43:32 UTC
Created attachment 180687 [details]
Diff of the gtk3 and gtk4 config from initial config to manually set config
I've attached a diff of the configuration for GTK3 and GTK4 to observe.
Note that in the diff, there are files created that don't exist during initial user login settings creation. I looked into this a bit, and the repo doesn't ship a default .ini config file. So one of two things is happening here: 1. Someone else is shipping a default .config file, and it doesn't match what this software will output when run 2. This software is running automatically and creating a .ini config file, but for some reason the first time it runs, it doesn't do the same thing that it does on all subsequent runs. *** This bug has been marked as a duplicate of bug 509515 *** |