*** This bug is a duplicate of bug 1620771 ***
https://bugs.launchpad.net/bugs/1620771
> Small update: we have now merged a change that allows snaps to work on
system where the users' home directories are not /home// but
/home/// If you are running such a system, you are welcome to try out
*** This bug is a duplicate of bug 1620771 ***
https://bugs.launchpad.net/bugs/1620771
** This bug has been marked a duplicate of bug 1620771
when /home is somewhere else, snaps don't work
** Changed in: snapd
Status: In Progress => Confirmed
** Changed in: snapd
Assignee:
It's 2023 now, and I just ran across this problem. What is the solution?
I searched on Google and found people having variations of this or
similar problems since 2018. That FIVE years.
The newest discussion I found on Google (and don't find anymore)
explained that this is an issue with the
Thanks Alberto, last update works for local users with local home directories.
Unfortunately keeps failing for nfs-mounted homes, even if the directories are
/home/users/.
The system tested is Ubuntu 22.04.
--
You received this bug notification because you are a member of Desktop
Packages,
Small update: we have now merged a change that allows snaps to work on
system where the users' home directories are not /home// but
/home///https://bugs.launchpad.net/snapd/+bug/1620771
instead.
--
You received this bug notification because you are a member of Desktop
Packages, which is
We are using Autofs/NFSv4 mounted homes on mountpoint /homes on 25+ multi-user
client computers. We decided to use a separate mountpoint to be able to use
both NFS mounted and local homes.
The bug blocks an update to 22.04 LTS on this computers.
--
You received this bug notification because
> You are being heard :-)
Really?
> But this is not an easy task
Alberto, it's not our fault that Ubuntu are having problems solving it.
Ubuntu created the problem, not us.
They should have got it right from the start, but I guess it was
difficult so they just chose to ignore it instead.
And
@Darko, we had the same blocking issues for an institutional deployment.
We ended up removing snapd and making modifications similar to this to
install a deb version https://www.omgubuntu.co.uk/2022/04/how-to-
install-firefox-deb-apt-ubuntu-22-04
--
You received this bug notification because you
this is a major showstopper at our institute. we have 60+ ubuntu
desktops with nfs-mounted homes and were postponing the switch from the
last lts to this one for a while. but this cannot go on forever while
availability of firefox is, obviously, crucial. i would classify this
bug as "critical" and
Hi Alberto, I'm glad to hear that there is some progress. Happy to test
patches if you need feedback on something.
--
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/1776800
Hi Jeffrey and Erik!
You are being heard :-) But this is not an easy task, and the amount of work
required to support the case of home directories nested somewhere deeper inside
/home is very different (read: lower) than that required to support home
directories located elsewhere in the
Any solution needs to work with multiple home folder locations that can
be located anywhere. We've got 540 users spread among four different
folders: /fac/, /grad/, /staff/, /visitor/.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Just to make sure the note is here, my home directory is not in /home at
all, but located under /u which is a mount point for an external volume
on another disk. I experienced the same problem trying to run a snap.
Whatever the solution, it should be generalized to any $HOME location.
--
You
** Changed in: snapd
Assignee: (unassigned) => Alberto Mardegan (mardy)
** Changed in: snapd
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
** Tags added: bionic focal jammy
--
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/1776800
Title:
Unable to start snap applications if user's home directory is not
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lxd (Ubuntu)
Status: New => Confirmed
--
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/1776800
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: firefox (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: chromium-browser (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
** Also affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: New
--
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/1776800
Title:
Unable to start snap applications
How can this be sitting around here for 3 years unassigned with *high*
priority? And then apparently it's not even considered a blocker for
replacing Firefox in Ubuntu 22.04 with the snap. Is it really that hard
to fix or is just nobody paying attention to it?
** Also affects: firefox (Ubuntu)
20 matches
Mail list logo
