Bug 420028

Summary: Plasma intermittently looses Gtk settings
Product: [Applications] systemsettings Reporter: Justin Time <atemch>
Component: kcm_styleAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED DOWNSTREAM    
Severity: normal CC: mail, nate, uhhadd
Priority: NOR    
Version First Reported In: 5.18.3   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Firefox without Gtk theme
Firefox with regular Gtl theme

Description Justin Time 2020-04-13 13:47:33 UTC
Created attachment 127502 [details]
Firefox without Gtk theme

SUMMARY

Once or twice a week the content of $HOME/.config/gtk-3.0/settings.ini file gets lost.  The file itself continues to exist, but becomes an empty, zero-sized (0B) file.   It happens randomly and apparently without a valid reason. 

As a result, Gtk apps (like Firefox, Thunderbird, LibreOffice suite) are opened as un-themed windows, with tiny, nano-sized interface fonts.


STEPS TO REPRODUCE

1. Empty existing $HOME/.config/gtk-3.0/settings.ini file:

$ > $HOME/.config/gtk-3.0/settings.ini

2. Launch Firefox

3. Observe Firefox window theme and decorations


OBSERVED RESULT

See attached "Firefox without Gtk theme" image.


EXPECTED RESULT

Currently cannot attach a second screenshot with normally themed Firefox window.


SOFTWARE/OS VERSIONS

Windows: <void>
macOS: <void>
Linux/KDE Plasma: Solus Kde Plasma
(available in About System)
KDE Plasma Version: 5.18.3
KDE Frameworks Version: 5.68.0
Qt Version: 5.13.2


ADDITIONAL INFORMATION

The content of $HOME/.config/gtk-3.0/settings.ini does not get lost in Arch Linux and Void Linux.  But the issue may be reproduced as described above.

Both Arch and Void are at higher software versions:

 - KDE Plasma Version: 5.18.4
 - KDE Frameworks Version: 5.69.0
 - Qt Version: 5.14.2
Comment 1 Justin Time 2020-04-13 13:51:38 UTC
Created attachment 127504 [details]
Firefox with regular Gtl theme
Comment 2 Mikhail Zolotukhin 2020-04-14 23:06:56 UTC
I don't use Solus, therefore I cannot reproduce this issue. However, if this only happens on Solus, you should probably report to Solus maintainers.