Version: (using KDE 4.0.5) OS: Linux Installed from: Ubuntu Packages I'm on a ltsp setup, i can use different .desktop files depending of the user, i set XDG_DATA_DIRS to set desktop file to be used for the users. In my $HOME/.kde/config/kdeglobals i set BrowserApplication[$e]=firefox.desktop but kde doesn't use the environment variable XDG_DATA_DIRS to launch the right firefox.desktop. I think that kde should look at XDG_DATA_DIRS to launch the applications. https://bugs.launchpad.net/ubuntu/+source/kde4libs/+bug/379053
Unless this is still present in current versions, this should be closed.
Interestingly, Debian recently removed kde4libs, which was one of the lingering causes for usage of $HOME/.kde https://tracker.debian.org/pkg/kde4libs But something still creates $HOME/.kde/config/kdeglobals for me (it's the only file remaining there now). KDE Plasma 5.14.5.
(In reply to Shmerl from comment #2) > But something still creates $HOME/.kde/config/kdeglobals for me (it's the > only file remaining there now). See Bug 405750. (This is off-topic for this bug.)
(In reply to Erik Quaeghebeur from comment #3) > (In reply to Shmerl from comment #2) > > But something still creates $HOME/.kde/config/kdeglobals for me (it's the > > only file remaining there now). > See Bug 405750. > (This is off-topic for this bug.) Ah, I see. Thanks. I commented there. Not sure why there is some resistance to actually fixing this for good.
Bug 405750 is the cause, and the issue here has been fixed in Frameworks 5.
(In reply to Nate Graham from comment #5) > Bug 405750 is the cause, and the issue here has been fixed in Frameworks 5. I meant I was wondering, why there is some resistance to fix #405750 for good. Or you mean that one was actually fixed in latest Frameworks 5?
Bug 405750 cannot be fixed because then it would break the remaining KDE4 apps that some people are still using (believe it or not). Once nobody is using any KDE4-era apps anymore, then the issue will finally go away. But until that time, we can't change the config file path without breaking old apps.
(In reply to Nate Graham from comment #7) > Bug 405750 cannot be fixed because then it would break the remaining KDE4 > apps that some people are still using (believe it or not). Once nobody is > using any KDE4-era apps anymore, then the issue will finally go away. But > until that time, we can't change the config file path without breaking old > apps. I got that part, but I commented how that can be handled without breaking them, while allowing users to avoid cluttering $HOME. I.e. make it a runtime switch. Those who need such old applications (few users likely), will flip the switch, while the rest (majority) can avoid cluttering $HOME by default.
And if you really think the majority is using such old KDE4 applications, and only minority is not, you can make the opposite - by default it will be enabled, and those who don't want to clutter $HOME can opt out by flipping the switch.
Making it a user-facing option doesn't make sense IMO. No regular user cares about a hidden file created by obsolete software not being in the correct hidden folder. This is the kind of option that adds visual clutter to the UI and mental clutter to people trying to find things that are more useful. Let's just wait until Qt 6 rolls around and then we can put this long national nightmare behind us. :)