Disabling a systemd service won’t prevent it from starting. For example, if another service depends on it then it will start anyway.
You have to mask the service which redirects the service files to /dev/null so that the service effectively has zero directives.
systemctl mask --now snapd
It also means that anything which depends on snapd will likely fail. That is absolutely an improvement since we obviously don’t want anything that depends on snaps.
What’s wrong with just removing snap? When ever I am forced to install Ubuntu I will remove snap and the “advantage-tools” (the part trying to sell you support)
First I’ll snap remove —purge all snap packages
Then apt purge —auotoremove snapd ubuntu-advantage-tools
Leaves behind a bunch of stuff. You have to manually remove each Snap individually, plus the snapshots they take and then hide, and then use Snap to remove itself (it doesn’t let you), then you can apt purge snapd.
There’s several levels of “we know better than you so we’ll just keep this here for when you inevitably change your mind” and it is exhausting.
I don’t even know if the above would also clean up all the dev/loop cruft. It was an unpleasant surprise to discover that apt remove alone didn’t at least disable all the systemd .mount units.
