Although it seems the list of Snaps got cleared as a result
$ snap list
Name Version Rev Tracking Publisher Notes
bare 1.0 5 latest/stable canonical✓ base
core24 20250829 1196 latest/stable canonical✓ base
gaming-graphics-core24 25.2.2~kisak1~n 13 kisak-fresh/stable canonical✓ -
gtk-common-themes 0.1-81-g442e511 1535 latest/stable canonical✓ -
snapd 2.71 25202 latest/stable canonical✓ snapd
steam 1.0.0.84 224 latest/stable/… canonical✓ -
Trying to install some of them
$ sudo snap install firefox --channel beta/core24
error: cannot perform the following tasks:
- Mount snap "gnome-46-2404" (125) (cannot proceed, expected snap "gnome-46-2404" revision 125 to be mounted but is not)
$ sudo snap install gnome-46-2404
gnome-46-2404 0+git.4ca00c0-sdk0+git.df43897 from Canonical✓ installed
Some worked, like Firefox & Bitwarden
Shotwell, however, didn’t (EDIT: re-running works)
$ sudo snap install shotwell
error: cannot perform the following tasks:
- Mount snap "shotwell" (20) (cannot proceed, expected snap "shotwell" revision 20 to be mounted but is not)
$ sudo snap remove shotwell
snap "shotwell" is not installed
That wiped all info snapd has about any snaps on your system without actually removing the mount units, the systemd service units, the apparmor profiles and whatever else gets generated on the fly by snapd/systemd interaction when installing a snap …
so you created a very broken state for your system now where snapd does not know what is installed and what is not (and thanks to things still being mounted or in case of services even still being running, you might hit many issues when trying to re-install any snaps) …
For snaps like Steam you can use snap remove steam --purge to skip the backup process thats likely contributing to the delay, on the assumption most the data can be easily downloaded again later.
I wouldn’t recommend people do this generally, those backups can be handy. --purge doesn’t delete more than what would otherwise happen, it just deletes it instantly, without a cooldown.
yep. That is probably why I refrained to remove the state.json file. I was afraid something would go wrong.
But HOW DO YOU FIX THE PROBLEM?
Note that ‘snap abort’ does not do anything, after all of this was caused by a ‘snap remove’ that just hanged with no clear reasons whatsoever.
I followed several threads at this point looking for a solution with no proper answer. Even the question “how do I remove snap from Ubuntu” had unclear (and scary) answers.
So the question is: what is the clear and safe fix?
I have the same problem.
losslesscut was not functioning (maybe because of Wayland).
snap remove losslesscut took ages and seemed to hang
I aborted the command session, and now whatever I want to do (install, refresh, remove), I have the message : errorr : snap “losslesscut” has “remove-snap” change in progress
So that I no longer have the programm, and cannot remove or reinstall it.
There was a bug in undoing failed removals that could cause the change to hang. This was fixed in 2.73 which is currently in beta. If your remove change has a “Run remove hook …” task that is stuck in “Undo”, please follow the steps in Comment #16 : Bug #2130315 : Bugs : snapd package : Ubuntu to unblock it and move to 2.73.