** Tags removed: eoan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849371
Title:
[snap] Cannot run chromium as user www-data because home directory is
/var/www
To manage notifications about
> * Webmail - if I receive an attachment of certain types (libreoffice
> is broken; pdf is OK), then I get a "please confirm you want to allow
> chromium to open this file" dialog every single time.
This is working as intended. This may seem a bit annoying, but strict
confinement means it is
+1 we're willing to pledge €500 (upon invoice) if either snap is
repaired or standard packages managed through a system that isn't broken
(dpkg/apt).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The snap confinement also seems to create a number of other problems.
I've also observed:
* Webmail - if I receive an attachment of certain types (libreoffice is
broken; pdf is OK), then I get a "please confirm you want to allow
chromium to open this file" dialog every single time.
* password
The limitation on HOME is well known and for now has no workaround other
than to bind mount whatever custom home directory to /home/$LOGNAME.
I'm marking this as confirmed but I think it's going to be de-duplicated
in another pass. There's already a bug for this.
** Also affects: snapd
Snapd team: this is admittedly a corner case, but users with a home
directory outside of /home might want to run snaps (especially CLI tools
as e.g. user www-data). Would it be feasible to add support for this in
snapd?
--
You received this bug notification because you are a member of Ubuntu
