Also, I chmod -x snapd and that seems to work as we intended. I do get some errors in log about systemd couldn't start snap daemon (permission denied
as expected). Snap apps seem to run fine. And when I ran the Software Upgrade, it went through to where it says "Updating snaps" and then just hung there until I did a force quit. So it wouldn't let the snaps update. And if I want to update them, I can manually chmod +x and update away. Hmmm could I/should I disable the snapd service as well?
on the apt side, however:
I removed unattended upgrades yesterday, and this morning, not long after booting, I'm prompted by Software Updater to update Thunderbird - a non security related application! 
There is still an unattended-upgrades service listed in systemctl :
Code:
$systemctl status unattended-upgrades
● unattended-upgrades.service
Loaded: masked (Reason: Unit unattended-upgrades.service is masked.)
Active: inactive (dead)
but I don't think that could be it. Even if it ran, it would try run a command from a package that's no longer installed, and would fail anyways?
I started to poke around. There was nothing in my Startup Applications, but /etc/cron.daily/apt-compat looks suspicious! This runs /usr/lib/apt/apt.systemd.daily. I don't really follow everything going on in there, but it looks to me that it tries to observe the options in the Software & Updates and runs update/upgrade and unattended-updates.
If my guess is correct, this might be the culprit and removing the cron entry would stop the mystery update?
Bookmarks