https://bugs.kde.org/show_bug.cgi?id=417534
--- Comment #6 from Guilherme Silva <oguilhe...@protonmail.com> --- Created attachment 129153 --> https://bugs.kde.org/attachment.cgi?id=129153&action=edit Patch for kde-gtk-config 5.18.5 Actually, never mind my last e-mail. The real culprit is the kde-gtk-config daemon. Once I: - Disable its service ("Plasma GTKd") in Plasma's Background Services manager - Remove the empty ~/.gtkrc-2.0 file - And, finally, re-login, the file isn't created anymore. So, brand new steps to reproduce: 1. Open the Background Services manager: $ kcmshell5 kcmkded 2. Search and disable "Plasma GTKd", hit OK. 3. Make sure there's no .gtkrc-2.0 file in your home folder. 4. Open the Background Services again, but now with GTK2_RC_FILES set: $ env GTK2_RC_FILES=/tmp/gtkrc kcmshell5 kcmkded 5. Re-enable the "Plasma GTKd" service, hit Apply. 6. There should be an empty .gtkrc-2.0 in your home now: $ file ~/.gtkrc-2.0 /home/gui/.gtkrc-2.0: empty I've fixed it locally (without any heavy testing, however) by removing some duplicated code and creating a method that will either respect GTK2_RC_FILES or fallback to ~/.gtkrc-2.0, if GTK2_RC_FILES isn't set or if it's empty. I'm attaching two patches (they accomplish the same): The first one I made for kde-gtk-config v5.18.5 (the latest version on Arch), and the other one which I just rebased against commit 380bff1f (v5.19.80). KDE Devs: Feel free to use it (or not), modify it, whatever. I'm reluctant to submit it for review, because I _really_ don't program in C++. So if did that and you guys' asked for modifications, I'd be wasting your time. If the patch is ready to merge, awesome! If it's not, then I'm sorry. And thank you for making Plasma so awesome. :) -- You are receiving this mail because: You are watching all bug changes.
