That's been a long standing issue, going back at least 5 years, with Snap
and NFS home directories or home directories not under /home. I quit using
snaps on the desktop because of that.
Their recent Firefox snap doesn't work under those conditions, so obviously
it's still a problem.
As far as I can tell there's zero interest in fixing this issue.
Philippe
------
The trouble with common sense is that it is so uncommon.
<Anonymous>
On Wed, Jul 6, 2022, 16:25 Rowland Penny via samba <samba at
lists.samba.org>
wrote:
> On Wed, 2022-07-06 at 20:10 +0000, samba-ml-en via samba wrote:
> > Dear list members,
> >
> > I have met yet another issue with Ubuntu and what is considered a
> > standard with Samba.
> >
> > Ubuntu is now mainly using snap for many apps. After joining my
> > domain, I realised no snaps could run, and found out that snaps
> > cannot run outside of the /home/$USER directory. Meaning they will
> > NOT run in /home/$DOMAIN/$USER.
> >
> > So you have to do the following in smb.conf
> >
> > # template homedir = /home/%D/%U
> > template homedir = /home/%U
> >
> > Otherwise, snaps will not start due to apparmor blocking them, I
> > could not not find a workaround so far.
>
> I think you need to log a bug on Ubuntu, As standard
> '/home/$DOMAIN/$USER' is the default.
>
> Let them fix their problem :-)
>
> Rowland
>
>
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions: https://lists.samba.org/mailman/options/samba
>