I believe that this is a duplicate of bug 1884299.
A few questions to people affected by this bug:
1) are you using autofs?
2) can you please try running "sudo systemctl restart snapd" after
logging in into your $HOME, and then try running a snap again?
3) If that still fails, can you paste the journal logs here (from the
time that snapd was restarted)?
** Changed in: snapd (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1784774
Title:
snapd is not autofs aware and fails with nfs home dir
Status in snapd:
Fix Released
Status in firefox package in Ubuntu:
Confirmed
Status in snapd package in Ubuntu:
Incomplete
Bug description:
This is similar to bugs 1662552 and 1782873. In 1782873, jdstrand
asked me to open a new bug for this specific issue.
In 1662552, snapd fails for nfs mounted home directories as network
permissions are not enabled. A work around was implemented that works
if the mount is done via a /home mount at boot. However this does not
work if people mount home directories via autofs. This is probably the
fundamental problem for 1782873 although there may be other issues.
[ Why use autofs? If some but not all of users want to use nfs homes.
In particular, I have a local user on all my accounts that does not
require the nfs server to be up or the kerberos server to be up, or
kerberos working on the client machines, etc. It is very useful when
something goes wrong. It means I mount /home/user rather than /home
(for several users). ]
To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1784774/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
