That's the intended behaviour, snapd's sandbox doesn't allow strictly
confined snaps (such as chromium) to access files owned by someone else.
Out of curiosity, what's the use case for files owned by a different
owner in your home directory?
** Changed in: chromium-browser (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900429
Title:
[snap] Unable to access files owned by another user
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900429/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
