How I delete snap and all traces of it

Antoine

Hi I don't like snap I've remove it but when I check my fdisk -l a lot of snap or mount how to remove this ? And why snap made this shit ?

Harvey

Antoine I check my fdisk -l a lot of snap or mount how to remove this ? And why snap made this shit ?

That's how it works. A LOT of mount points that can slow down your boot time. Removing all traces of snap can be... annoying. But this is the proper way.

sudo snap list

Name               Version               Rev    Tracking       Publisher   Notes
bare               1.0                   5      latest/stable  canonical✓  base
core               16-2.58.3             14946  latest/stable  canonical✓  core
core20             20230503              1891   latest/stable  canonical✓  base
core22             20230503              634    latest/stable  canonical✓  base
gnome-3-38-2004    0+git.6f39565         140    latest/stable  canonical✓  -
gnome-42-2204      0+git.587e965         102    latest/stable  canonical✓  -
gtk-common-themes  0.1-81-g442e511       1535   latest/stable  canonical✓  -
hello-world        6.4                   29     latest/stable  canonical✓  -
snap-store         41.3-71-g709398e      959    latest/stable  canonical✓  -
spotify            1.2.11.916.geb595a67  67     latest/stable  spotify✓    -

snap is stupid. There are bare and core* containers that are protected until everything using them is removed first. They can not be removed as part of the same command, so lets remove what we can.
sudo snap remove spotify snap-store hello-world gnome-3-38-2004 gnome-42-2204 gtk-common-themes

Now we can remove some more...
sudo snap remove core22 core20 bare

Based on my example I only have core left. An guess what? It will not let you disable it or remove it. Unless we unmount it first.
lsblk

NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
loop0    7:0    0 116.8M  1 loop /snap/core/14946
sda      8:0    0   3.6T  0 disk
└─sda1   8:1    0   3.6T  0 part
sdb      8:16   0   2.7T  0 disk
└─sdb1   8:17   0   2.7T  0 part
sdc      8:32   0 931.5G  0 disk
├─sdc1   8:33   0   300M  0 part
└─sdc2   8:34   0 931.2G  0 part
sdd      8:48   0   7.3T  0 disk
└─sdd1   8:49   0   7.3T  0 part
sde      8:64   0 232.9G  0 disk
├─sde1   8:65   0   489M  0 part
├─sde2   8:66   0   3.7G  0 part [SWAP]
└─sde3   8:67   0 228.7G  0 part /
zram0  252:0    0     8G  0 disk [SWAP]

As you can see I have 1 loop mount point belonging to snap remaining. So lets umount it and remove core.
sudo umount /snap/core/14946
sudo snap remove core

For my example all snap containers have been removed and as I never want to touch snap again.
sudo eopkg rm snapd

Finally remove the directory it creates in your home directory:
rm -rf ~/snap/

All gone.

riffer

I don't know if this is much help, but this will completely remove snap from ubuntu:

snap list
sudo snap remove --purge package-name
sudo rm -rf /var/cache/snapd/
sudo apt autoremove --purge snapd gnome-software-plugin-snap
rm -fr ~/snap
sudo apt-mark hold snapd

So basically purge each package and then I am not sure what the rest of the commands are or the Solus equivalents.

Personally, I just leave snap alone.

brent

Harvey . There are bare and core* containers that are protected until everything using them is removed first.

Key ^^.
Great tutorial.
Snap tangles itself up in the squashfs if I'm not mistaken? and removing it may free up a gig of ram if I recall right.

I got nothing against Canonical. Linux has riches of packages. Repo doesn't have the package? Then compile it. Don't want to build? Then Snap or FP or appimage. Or a standalone ('portable') binary.
Removal of snap seems to get rid of a single way to get packages leaving 3-4 more. To embed it in an OS seems an outdated concept now.

Antoine

Sorry for the late anwser but. when I do a

sudo snap list
[sudo] password for saturne:
No snaps are installed yet. Try 'snap install hello-world'.
WARNING: There is 1 new warning. See 'snap warnings'.
Disque /dev/ram1 : 64 MiB, 67108864 octets, 131072 secteurs
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 4096 octets
taille d'E/S (minimale / optimale) : 4096 octets / 4096 octets


Disque /dev/ram2 : 64 MiB, 67108864 octets, 131072 secteurs
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 4096 octets
taille d'E/S (minimale / optimale) : 4096 octets / 4096 octets


Disque /dev/ram3 : 64 MiB, 67108864 octets, 131072 secteurs
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 4096 octets
taille d'E/S (minimale / optimale) : 4096 octets / 4096 octets


Disque /dev/ram4 : 64 MiB, 67108864 octets, 131072 secteurs
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 4096 octets
taille d'E/S (minimale / optimale) : 4096 octets / 4096 octets


Disque /dev/ram5 : 64 MiB, 67108864 octets, 131072 secteurs
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 4096 octets
taille d'E/S (minimale / optimale) : 4096 octets / 4096 octets


Disque /dev/ram6 : 64 MiB, 67108864 octets, 131072 secteurs
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 4096 octets
taille d'E/S (minimale / optimale) : 4096 octets / 4096 octets


Disque /dev/ram7 : 64 MiB, 67108864 octets, 131072 secteurs
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 4096 octets
taille d'E/S (minimale / optimale) : 4096 octets / 4096 octets


Disque /dev/ram8 : 64 MiB, 67108864 octets, 131072 secteurs
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 4096 octets
taille d'E/S (minimale / optimale) : 4096 octets / 4096 octets


Disque /dev/ram9 : 64 MiB, 67108864 octets, 131072 secteurs
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 4096 octets
taille d'E/S (minimale / optimale) : 4096 octets / 4096 octets


Disque /dev/ram10 : 64 MiB, 67108864 octets, 131072 secteurs
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 4096 octets
taille d'E/S (minimale / optimale) : 4096 octets / 4096 octets


Disque /dev/ram11 : 64 MiB, 67108864 octets, 131072 secteurs
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 4096 octets
taille d'E/S (minimale / optimale) : 4096 octets / 4096 octets


Disque /dev/ram12 : 64 MiB, 67108864 octets, 131072 secteurs
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 4096 octets
taille d'E/S (minimale / optimale) : 4096 octets / 4096 octets


Disque /dev/ram13 : 64 MiB, 67108864 octets, 131072 secteurs
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 4096 octets
taille d'E/S (minimale / optimale) : 4096 octets / 4096 octets


Disque /dev/ram14 : 64 MiB, 67108864 octets, 131072 secteurs
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 4096 octets
taille d'E/S (minimale / optimale) : 4096 octets / 4096 octets

Mod edit: Enclosed the output in three backticks ( ``` ) for better formatting.
- Evan

Antoine

I don't understand why I have no snap package ... And i have this when I made a fresh install...

Staudey

Antoine I have no idea what you're asking here to be honest. Can you explain it in more detail?

brent

Antoine

sudo snap list
[sudo] password for saturne:
No snaps are installed yet. Try 'snap install hello-world'.

this means you haven't installed a snap package. use --all just for kicks.
sudo is not necessary here.

do this:
1 snap find brave

2 snap install brave

3 snap list

then you should see brave browser. "no snaps installed" in your output means no snaps installed, in my estimation (although I've been wrong before.)

and your post probably belonged in a new thread not this one (this is about getting rid of it not installing in it)

: Staudey I think that's what I'm seeng but can't be positive🙂

Antoine

Staudey I want to remove the mounting point about snap but when i list all my snap i've nothing...

Antoine

snap list all
error: no matching snaps installed

Staudey

Antoine Well, if you don't have any snaps installed then that command will of course show nothing. You should only follow the rest of the instructions then.

AmsterDan

Antoine
I've noticed the same and did not understand all the different loops either. I came across this thread which helped me understand more of it, including the removal of residual files/directories.

In particular this reply by @Dentraq

Check list of installed snaps: sudo snap list --all
Remove all of installed snaps: sudo snap remove snapname (for core snap also use a --revision revision_number option)
Remove a snapd by sudo eopkg rmf snapd
List all /dev/loop devices currently mounted by snap: sudo mount | grep snap | awk '{print $3}'
Unmount this devices by sudo umount device_name
Remove snap directory: sudo rm -rf /var/lib/snap && sudo rm -rf /snap
Remove all files that used to mount a snap packages from /var/lib/snapd/snaps to /snap on the boot:
sudo find /etc/systemd/system -name "snap-*.mount" -delete sudo find /etc/systemd/system -name "snap.*.service" -delete sudo find /etc/systemd/system/multi-user.target.wants -name "snap-*.mount" -delete sudo find /etc/systemd/system/multi-user.target.wants -name "snap.*.service" -delete
Reboot, and that's all. You're perfect.

Antoine

Staudey like i said before its on a fresh install...

Staudey

Antoine Then why are you surprised that listing the installed snaps lists nothing? Of course if you haven't installed any snaps that command will say exactly that. Just remove snapd, if you're so inclined, and be done with it.

bleh

Antoine Just continue with the last few commands.

"sudo eopkg rm snapd

Finally remove the directory it creates in your home directory:
rm -rf ~/snap/"

Antoine

Staudey i've no snap install but I've snap mounted point ? weird.
why i've /dev/loop if no snap is install ???

ReillyBrogan

Antoine You should really not be messing around in /dev. It doesn't sound like you understand what you're seeing in there, those are kernel interfaces and unrelated to snap.

Antoine

I was thinking /dev/ram was a think about snap.

Antoine

ReillyBrogan thank for your explication 🙂