Snap-Chromium cannot be run by a daemon

Posted Jul 9, 2020 13:46 UTC (Thu) by evgeny (subscriber, #774)
In reply to: Snap-Chromium cannot be run by a daemon by Richard_J_Neill
Parent article: Linux Mint drops Ubuntu Snap packages

... and doesn't work with NFS-based home directories: <https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1884299>.

Snap-Chromium cannot be run by a daemon

Posted Jul 15, 2020 17:29 UTC (Wed) by smoogen (subscriber, #97) [Link] (3 responses)

I was looking at this and realized this is a 20/80-80/20 problem.

20 years ago 80% of the user population were on NFS home directories and these problems would get fixed. Now much less than 20% of the user population are using NFS home directories and so it not going to get fixed unless the people running into it do the fix themselves... usually the fix is to stop using NFS :(.

Snap-Chromium cannot be run by a daemon

Posted Jul 15, 2020 22:22 UTC (Wed) by zlynx (guest, #2285) [Link] (1 responses)

I've seen some dire replacements for the lack of NFS.

How does a Windows style roaming profile sound? Rsync on login and rsync back on logout. Kind of ick, but not super bad on gigabit Ethernet.

Snap-Chromium cannot be run by a daemon

Posted Jul 15, 2020 23:35 UTC (Wed) by Wol (subscriber, #4433) [Link]

Very ick when you've got a small disk in your workstation, and a network home that's larger than your local hard disk ...

Cheers,
Wol

Snap-Chromium cannot be run by a daemon

Posted Jul 16, 2020 7:55 UTC (Thu) by evgeny (subscriber, #774) [Link]

> usually the fix is to stop using NFS :(

Well, for me the fix was to stop using snap :)