Bug 500460 - At login, a .var folder is created in home directory even when Flatpak isn't installed
Summary: At login, a .var folder is created in home directory even when Flatpak isn't ...
Status: RESOLVED DUPLICATE of bug 500154
Alias: None
Product: plasma-browser-integration
Classification: Plasma
Component: Firefox (other bugs)
Version First Reported In: unspecified
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Kai Uwe Broulik
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-02-20 13:44 UTC by remindful7560
Modified: 2025-02-20 15:08 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description remindful7560 2025-02-20 13:44:56 UTC
SUMMARY
At login, the ~/.var folder is populated with data for the Firefox Flatpak integration, and it creates the ~/.var folder even if Flatpak isn't installed.

This would be perfectly acceptable if it was somewhere more obscure, but creating a folder in my home directory for compatibility with software I don't use is very unfortunate. It being hidden doesn't improve the situation.

This is partially an upstream issue due to Flatpak's hardcoded use of the path, but support for changing it there is very low.

The behavior was introduced in this commit: https://invent.kde.org/plasma/plasma-browser-integration/-/commit/ebf6606463d73e7dd0a658340b369ab495da9b4a

STEPS TO REPRODUCE
1. Have plasma-browser-integration installed
2. Login

OBSERVED RESULT
A `.var` folder (along with contents) is present in home directory

EXPECTED RESULT
No folder generated unless Flatpak is installed (or at least, it would only populate the folder if it already existed)

SOFTWARE/OS VERSIONS
(available in the Info Center app, or by running `kinfo` in a terminal window)
Operating System: Arch Linux 
KDE Plasma Version: 6.3.1
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2

ADDITIONAL INFORMATION
Comment 1 Antonio Rojas 2025-02-20 15:08:20 UTC

*** This bug has been marked as a duplicate of bug 500154 ***