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). That's a security feature to prevent
snap applications from reading other applications' data.
Instead, as you've found out, the app gets its own home directory
located at $HOME/snap/chromium/current. The application itself does
respect the XDG base directory specification, but with a rewritten
$HOME.
Now, you mention the cache data. That one is stored in
$HOME/chromium/common/.cache/. The default profile directory is stored
in $HOME/chromium/common/chromium/.
The transitional package does copy over an existing profile from
$HOME/.config/chromium if it exists the first time the snap is being
run.
Given all this, I'm not really sure what the bug really is about? Can
you share concrete use cases?
** Changed in: chromium-browser (Ubuntu)
Status: Confirmed => Incomplete
--
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
