> The chromium snap is strictly confined, and that means that it cannot
read/write to hidden directories inside the user's home folder (such as
$HOME/.config or $HOME/.cache).
Change the folder it's confined to.
> That one is stored in $HOME/chromium/common/.cache/
No, not really. The profile folder contains gigabytes of cache files.
> The default profile directory is stored in
$HOME/chromium/common/chromium/.
No, not really. Copying it over resulted in a utterly broken profile,
some vital files are not in the common folder.
> Given all this, I'm not really sure what the bug really is about? Can
you share concrete use cases?
I'm not sure what's unclear, XDG base directory specification is NOT
followed, my environment variables are ignored and the wrong folder is
used for everything. That has multiple negative effects, as I listed.
** Changed in: chromium-browser (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887804
Title:
chromium-browser does not follow XDG base directory specification
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1887804/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
