*** This bug is a duplicate of bug 1849371 ***
https://bugs.launchpad.net/bugs/1849371
Thanks Olivier,
I could imagine that you'll get several other bug reports where people
do not see how the underlying problem relates to "Cannot run chromium as
user www-data because home directory is /var/www" - but I guess the
issue is the same.
Btw, I've been using Linux for over 25 years and I don't understand the
quote you mention and why snapd would be chosen to manage standard
packages, if it (apparently) is broken (at least somebody is working on
a fix, according to "Zygmunt's quote", mentioning "_for now_ has no
workaround"). Home directories commonly are mounted (at least in
professional environments) and quite commonly linked into /home/, and
there never has been any problem with this, to the contrary, it solves
many a headache (until now, as it seems). Feel free to send me back to
old-fart-country where I came from, I'm just bothered by update-routines
that break (standard!) environments.
If snap is broken and cannot deal with standard setups (this much I
understand from the other bug and what I find in relation to "Zygmunt's
quote"), may be it should be fixed before being included in the handling
of standard packages?
OTOH, may be Ubuntu doesn't target professional environments. The
solution of course is fine if the target audience are people who setup
every new laptop from scratch and never work in networked environments
(*scnr*).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849729
Title:
chromium-browser fails to start after upgrade to eoan
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849729/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
