linux-traipu team mailing list archive
-
linux-traipu team
-
Mailing list archive
-
Message #15471
[Bug 1887804] Re: chromium-browser does not follow XDG base directory specification
As previously discussed, this issue is twofold:
- upstream chromium stores parts of its cache in the profile folder
(that's https://bugs.chromium.org/p/chromium/issues/detail?id=1106754)
- the snap format enforces that apps' cache folder is under
$HOME/snap/$SNAP_NAME/common/.cache
The first point equally affects all packaging formats (including deb).
The second one is a design decision for improved security that has its
downsides, particularly (as pointed out in the last few comments) with
regards to backup solutions that want to exclude one single cache folder
in the user's home directory. As a mitigation, can your backup tool
exclude folders including wildcards, e.g. -$HOME/snap/*/common/.cache ?
--
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Chromium Browser.
https://bugs.launchpad.net/bugs/1887804
Title:
chromium-browser does not follow XDG base directory specification
Status in Chromium Browser:
Invalid
Status in chromium-browser package in Ubuntu:
Opinion
Bug description:
Currently Chromium does not follow the XDG base directory
specification which means that the cache and configuration folder
aren't properly used.
This causes the issue that it's nearly impossible to properly migrate
or back up Chromium configuration (between computers) and it makes for
example mounting cache as tmpfs or wiping it very very difficult.
I felt those both immensely when trying to migrate my home folder,
gigabytes of cache in ~/snap/chromium/[id]/.config/chromium/[folder]
(and ~/snap itself is also not XDG base directory specification
compliant, shame!).
There's also the issue that the previous configuration that is located
properly, isn't migrated by the migrational package.
In order to fix this bug, it would require making the snap package
follow the XDG base directory specification.
To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/1887804/+subscriptions