snap mounts seem to be left behind
ptocca opened this issue · 1 comments
snap mounts seem to be left behind
To Reproduce
On Ubuntu 22.04, I executed the generated scripts. Some snap applications were reported as not having flatpak counterpart.
I installed via apt gnome-software. I then restarted Linux.
At the console pgrep snapd confirmed snapd was not running anymore.
Then I inspected the list of mounts with mount. The mounts are still polluted by the snap entries.
Example:
/var/lib/snapd/snaps/gnome-42-2204_141.snap on /snap/gnome-42-2204/141 type squashfs (ro,nodev,relatime,errors=continue,x-gdu.hide)
It would seem that systemd mount units are left behind. Indeed
/etc/systemd/system/snapd.mounts.target.wants contains lots of *.mount files. Example: snap-gnome\x2d42\x2d2204-141.mount.
Did I do anything wrong? Is it perhaps because some snap applications were reported as not having flatpak counterpart?
Even though I was not 100% sure of what I was doing, I deleted that directory and all other entries starting with snap under ``/etc/systemd/system/`.
After a restart, the snap-related "spurious" mounts were gone.
Expected behaviour
I expected everything snap-related to disappear.
Desktop (please complete the following information):
- OS: Ubuntu
- Version: 22.04
Additional context
I noticed that under /etc/systemd/user there is an entry called snap.snapd-desktop-integration.snapd-desktop-integration.service. Also, there seem to be other remnants of snap around.
By the way, thanks for writing this utility! I had put off getting rid of snap for so long :-)
Hello there 👋
Thanks for submitting your first issue to the unsnap project 🐛 We'll try and take a look at your issue soon ⏲
In the meantime you might want to join the popey's home Discord 🗣 where we discuss this project