I have a similar behaviour, as mentioned in comment #1 - that is not (I think) covered by the limitations linked just above (#36).
The homedirs is standard (/home), but for certain users, their home dir is a symlink to another folder: /home/user1 -> /accounts/user1. In this case, /home/user1/snap is "standard" layout, but snap keeps pretending that e.g. "/home/user1/snap/spotify/36" is not a directory - which is not true.
Comment #34 is not correct for me - even though the argument is logical, it is unfortunately not true. It may come from the facts that I'm using BTRFS volumes (I've already seen specific behaviours with containers and BTRFS, but I'm not technical enough to draw a conclusion). So, no, it's not "all".
Also, adding /accounts to apparmor homedirs is without effect here.
Hello,
I have a similar behaviour, as mentioned in comment #1 - that is not (I think) covered by the limitations linked just above (#36).
The homedirs is standard (/home), but for certain users, their home dir is a symlink to another folder: /home/user1 -> /accounts/user1. In this case, /home/user1/snap is "standard" layout, but snap keeps pretending that e.g. "/home/ user1/snap/ spotify/ 36" is not a directory - which is not true.
Comment #34 is not correct for me - even though the argument is logical, it is unfortunately not true. It may come from the facts that I'm using BTRFS volumes (I've already seen specific behaviours with containers and BTRFS, but I'm not technical enough to draw a conclusion). So, no, it's not "all".
Also, adding /accounts to apparmor homedirs is without effect here.