Bug 507540

Summary: systemsettings long startup time
Product: [Applications] systemsettings Reporter: Marius Kaufmann <dasug>
Component: generalAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED UPSTREAM    
Severity: normal CC: nate
Priority: NOR    
Version First Reported In: 6.4.3   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: terminal output when starting systemsettings

Description Marius Kaufmann 2025-07-27 12:45:08 UTC
Created attachment 183563 [details]
terminal output when starting systemsettings

SUMMARY
systemsettings takes several minutes to start up every time I try to open the application

STEPS TO REPRODUCE
1. Start systemsettings (via .desktop file or directly in terminal)
2. Wait

OBSERVED RESULT
Nothing happens for about 2 minutes, then the systemsettings application opens up.

EXPECTED RESULT
systemsettings opens up within a few seconds after starting as it used to do.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux (Kernel 6.15.8-zen1-1-zen (64-bit)), packages up-to-date as of time of report
KDE Plasma Version: 6.4.3
KDE Frameworks Version: 6.16.0
Qt Version: 6.9.1
Wayland

ADDITIONAL INFORMATION
I think it got introduced somewhere in 6.4 but I don't remember when exactly. Before that the application used to open in a few seconds or so.
Comment 1 Marius Kaufmann 2025-07-31 10:57:20 UTC
Somehow today systemsettings started opening pretty much immediately again. I don't think there was any KDE update in the meantime as none of the version numbers changed. So either it was somehow caused by some other package that did update in the meantime or some other weird thing was going on that somehow fixed itself?
Anyways, should I mark the bug as RESOLVED and reopen should it re-appear or should I leave it open for now?
Comment 2 Nate Graham 2025-09-23 18:12:13 UTC
> Using fontconfig file: "/home/dasug/.config/fontconfig/fonts.conf"
This would suggests something deep in the font code was causing a slowdown. If it stopped happening, it could be that you were experiencing a bug in 3rd-party font code and it got fixed.

I'm glad the issue has stopped happening!