Yes, you can restart specific snap by using snap restart nameOfTheSnap command.
1 Like
Thanks â back then I have given up on this and just tried using the apt-repository of firefox instead, but this was also annoying because even after pinning the apt version, after every automatic update ubuntu would enable the snap version which does not work, requiring a manual apt update to make it work again 
Anyways, because more snap-only programs have the same problem I wanted to re-try fixing this problem with snap itself. My home directory is really in /data (/data/johann) where /data is a different device than where /home is mounted. However /home/johann is still configured as my $HOME but /home/johann is just a symbolic link to /data/johann.
So I tried to solve the problem using: sudo snap set system homedirs=/data/ (tried both with and withou sudo), but after this, when I try to run e.g. firefox I get the error:
cannot perform operation: mount --rbind /data/ /tmp/snap.rootfs_fgX5Wd//data/: Permission denied
My snapd version is 2.67.1+24.04
Have you tried using a bind mount instead of a symlink?
I have given up again and went back to manually configuring installation from an apt repo, since I discovered that on top of all those problems snap installations of Firefox also make the settings show the message âYour browser is being managed by your organizationâ preventing some changes which is absurd.
I cannot express how much I hate the way how Canonical forces snap on their users.
Some suggestions
- I hate that Canonical does not provide any current full browser (i.e. chromium/firefox based) via apt
- I hate how badly the firefox snap on Ubuntu is usable (with my workflows)
which ones are currently not working due to that message?
I cannot remember but I had several occasions where the only available option is snap (if the problem with the home directory exists, it prevents all snap apps from working, apparently), or where the apt version is MUCH older than the snap version. With Firefox there is the additional problem that even IF one jumps through all the hops of manually working around the snap limitations still in place, the Firefox profile looks like an âorganizational profileâ where it is not possible for the user to change all settings. It is also not possible to user separate profiles with snap Firefox using the ââprofileâ option. I did manage to get snap going using the bind mount workaround but I still decided not to use the snap version of firefox for these reasons. It feels just like on MS Windows getting limited like that and having things forced on users like that. If the whole snap fiasco continues like that I am really considering switching to a distro which does not force their users to use limiting and flawed solutions like that.
That message should only be shown when /etc/firefox has policies at the system level. Most people using the Firefox snap do not see that, so it could be worth looking there to see whats going on.