Noticed today that a box I had previously purged of the snapd infestation was reinfected when doing some updates... and it brought in FF100 snap and snapd!
Checked my /etc/apt/preferences.d/snapd file, yep still there, with blocks on snapd
Ok. ... repurge snapd, and FF 100 snap, reinstall my FF DEB package...
Did several tries on using differing file names, and pin priorities in there, and even reboots... snapd will still attempt to be installed!
Pick a package at random, I picked 2ping... cp the snapd block file over, edit it to 2ping for the package, sudo apt-get update... and FAILURE can not install 2ping! as I would expect...
Same pin/block files, in 20.04,. and still fails on any attempts to infect with snapd....
See similar post here about 2 months ago.... https://askubuntu.com/questions/1404...nored-in-22-04
Any one else seeing apt ignore the block on snapd/? I smell a rat!
Checked my /etc/apt/preferences.d/snapd file, yep still there, with blocks on snapd
Ok. ... repurge snapd, and FF 100 snap, reinstall my FF DEB package...
Did several tries on using differing file names, and pin priorities in there, and even reboots... snapd will still attempt to be installed!
Pick a package at random, I picked 2ping... cp the snapd block file over, edit it to 2ping for the package, sudo apt-get update... and FAILURE can not install 2ping! as I would expect...
Same pin/block files, in 20.04,. and still fails on any attempts to infect with snapd....
See similar post here about 2 months ago.... https://askubuntu.com/questions/1404...nored-in-22-04
Any one else seeing apt ignore the block on snapd/? I smell a rat!
Comment