Bug 503396 - KDE GTK configuration isn't fully initialized on first login, resulting in theming not taking effect for ABRT and Anaconda
Summary: KDE GTK configuration isn't fully initialized on first login, resulting in th...
Status: RESOLVED DUPLICATE of bug 509515
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_style (other bugs)
Version First Reported In: 6.3.4
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-04-26 15:43 UTC by Neal Gompa
Modified: 2025-09-19 02:37 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Diff of the gtk3 and gtk4 config from initial config to manually set config (1.26 KB, text/plain)
2025-04-26 15:44 UTC, Neal Gompa
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Neal Gompa 2025-04-26 15:43:32 UTC
SUMMARY
It appears that the GTK configuration Plasma sets on first login is not complete, because it's not enough to make Anaconda and ABRT ("Problem reporting") use Breeze instead of Adwaita.

It's possible to see it work properly by setting the GTK style to Default and then to Breeze again.

STEPS TO REPRODUCE
1. Boot Fedora KDE Plasma Desktop Edition 42 live ISO
2. Start Anaconda

OBSERVED RESULT
Anaconda uses Adwaita.

EXPECTED RESULT
Anaconda uses Breeze.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora Linux 42 (KDE Plasma Desktop Edition)
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.12.0
Qt Version: 6.8.2
Comment 1 Neal Gompa 2025-04-26 15:44:33 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.
Comment 2 Neal Gompa 2025-04-26 16:37:05 UTC
Note that in the diff, there are files created that don't exist during initial user login settings creation.
Comment 3 Nate Graham 2025-08-19 21:07:31 UTC
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.
Comment 4 Nate Graham 2025-09-19 02:37:50 UTC

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