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 Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1900429
Title:
[snap] Unable to access files owned by another user
Status in chromium-browser package in Ubuntu:
Invalid
Bug description:
The chromium snap cannot access files in my $HOME that have a
different owner, even though the files are world-readable.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900429/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
