Bug 500154

Summary:	Plasma browser integration keeps creating $HOME/.var
Product:	[Plasma] plasma-browser-integration	Reporter:	Shmerl <shtetldik>
Component:	Firefox	Assignee:	Kai Uwe Broulik <kde>
Status:	RESOLVED INTENTIONAL
Severity:	normal	CC:	remindful7560, sitter
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Debian testing
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Shmerl 2025-02-15 23:51:54 UTC

Looks like since switching to Plasma 6.3 something related to plasma-browser-integration keeps creating $HOME/.var location which looks like related to Flatpak + Firefox, but in my case it's clutter since I'm not using Flatpak (and why can't Flatpak avoid cluttering $HOME anyway and use $HOME/.local/var or something).

That hasn't happened with Plasma 6.2.x. Is there some configuration to turn that behavior off? If not, please add the ability to to do it.

Comment 1 Shmerl 2025-02-15 23:56:42 UTC

For the reference:

* https://github.com/flatpak/flatpak/issues/46
* https://github.com/flatpak/flatpak/issues/1651

Looks like Flatpak developers don't want to fix it. Good reason for me not to use it.

Comment 2 Harald Sitter 2025-02-16 12:18:30 UTC

We are not going to add code for this.

Comment 3 Antonio Rojas 2025-02-20 15:08:20 UTC

*** Bug 500460 has been marked as a duplicate of this bug. ***

Comment 4 Shmerl 2025-02-24 02:41:47 UTC

(In reply to Harald Sitter from comment #2)
> We are not going to add code for this.

Since KDE developers are listed on the XDG base directory specification:
https://specifications.freedesktop.org/basedir-spec/latest/
can you please comment if usage of $HOME/.var is intended to be compliant with it?

One comment in that Flatpak issue mentioned that it seems to have been the intent, but it was never updated. What is KDE's stance on this?