nathanpainchaud The problem on my system with reappearing /dev/loop device and /snap directory after reboot was caused because I forgot remove a /var/lib/snap after removing a /snap. After reboot, the snap's systemd services just restore a core snap from /var/lib/snap on /snap.
But... I'm really puzzled here too, why sudo eopkg rmf snapd
doesn't remove snapd properly even with --purge
option if it does it on fresh install. I can assume that on fresh install no one snap is loaded (even core), but if you install some snap, delete it by sudo snap remove
- the core snap will be still exist (if you try delete it - snapd create a new one) and you can only manually delete it after stopping snapd and removing a snapd by eopkg.
It can be funny, but I find a thread about same problem on SolusProject Reddit.
The Linuxllc user suggest to use this script https://github.com/zyga/devtools/blob/master/reset-state , which do the same things that I did manually.
nathanpainchaud Maybe once some snaps (e.g. core) are downloaded snap itself becomes entangled with the system?
Hmm, I don't think so, because after removing snapd by eopkg any related with snap daemons are not exist on system.