Bug 474795 - [X11] xsettingsd's Plasma-started instance has no effect on Flatpak'd GTK applications
Summary: [X11] xsettingsd's Plasma-started instance has no effect on Flatpak'd GTK app...
Status: REOPENED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Startup process (show other bugs)
Version: 5.27.5
Platform: Other Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-09-23 02:40 UTC by The Feren OS Dev
Modified: 2023-10-09 20:07 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Bug in effect (267.63 KB, image/png)
2023-10-09 20:06 UTC, The Feren OS Dev 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description The Feren OS Dev 2023-09-23 02:40:33 UTC 
SUMMARY
After logging in, KDE Plasma successfully launches xsettingsd as expected. However, this same instance of xsettingsd appears to do literally nothing to Flatpak applications.

Starting xsettingsd by yourself fixes this issue... until the next time you log in with no prior running xsettingsd instances.

STEPS TO REPRODUCE
1. Log in
2. See xsettingsd running in System Activity
3. Open a Flatpak'd GTK application like Mozilla Firefox

OBSERVED RESULT
Those applications use their fallback font, whatever that may be in your context, as one example of the notable consequences of being unaffected.

EXPECTED RESULT
The outcome of launching xsettingsd manually.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: KDE neon 5.27.5
(available in About System)
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.106.0
Qt Version: 5.15.9

ADDITIONAL INFORMATION
May be the same bug as https://bugs.kde.org/show_bug.cgi?id=426788, but the issue's too vague to be sure.

Will test on KDE neon 5.27.8 in the coming hours.
Comment 1 The Feren OS Dev 2023-09-23 02:41:12 UTC 
Additional note:
The parent process of the troubled xsettingsd is systemd.
Comment 2 The Feren OS Dev 2023-09-24 00:03:06 UTC 
Nevermind, can no longer reproduce on 5.27.8, so given how frequently it happened in 5.27.5 meaning it couldn't have been an unlucky occurrence, I'm gonna assume this was indeed a bug that accidentally got fixed.

Still,
Comment 3 The Feren OS Dev 2023-10-09 20:05:44 UTC 
Nevermind, managed to reproduce it on 5.27.8
Comment 4 The Feren OS Dev 2023-10-09 20:06:23 UTC 
Created attachment 162180 [details]
Bug in effect
Comment 5 The Feren OS Dev 2023-10-09 20:07:26 UTC 
(In reply to The Feren OS Dev from comment #4)
> Created attachment 162180 [details]
> Bug in effect

Weirdly enough, it seems to be inconsistent - race condition perhaps?