5 ms·

Snap is auto-updating and you can't stop it [0]. I actually liked the idea of the snaps on paper, especially combined with Ubuntu Core for running lightweight

Snap is auto-updating and you can't stop it [0]. I actually liked the idea of the snaps on paper, especially combined with Ubuntu Core for running lightweight VMs (via LXD). But the tone on that exchange and the "we know best" attitude put me off it. I have an Ubuntu 20.04 installed for tests on one of my home machines, and from time to time I catch doing who knows what. What tips me off is seeing the drive light going crazy when I'm doing basically nothing. And for some reason it doesn't log anything while doing this... [0] https://forum.snapcraft.io/t/disabling-automatic-refresh-for-snap-from-store/707 https://forum.snapcraft.io/t/disabling-automatic-refresh-for...

Izkata 6y ago
> Snap is auto-updating and you can't stop it Kill the daemon and make it non-executable. Only restore it when you want to manually do an install.
- AnIdiotOnTheNet 6y ago
  What is this, Windows 10?
  - hansvm 6y ago
    I wish Windows 10 were that nice. First you need a nice race condition to break the updater's updater's unauthorized change prevention service....
    - a1369209993 6y ago
      Boot into your linux install, dd /dev/random onto the executables, done.
- xet7 6y ago
  Huh? I think it's easier to just add to /etc/hosts this line: 127.0.0.1 api.snapcraft.io
viraptor 6y ago
On paper snap is great, but at this point we've got better alternatives. If you want to use something snap-like either flatpak or appimage will likely work and be way less user-hostile.
- vladvasiliu 6y ago
  I didn't look closely into either flatpak nor appimage. But I get the advantages of such a system and I think it might actually help with the "Linux on the desktop situation". It's very easy to deploy something with restricted access to the file system, something that has all its dependencies in one place, that updates atomically, etc. It's also nice for random app vendors to be able to know that all their users are on the latest version, or not far behind. Could even push some devs to consider going back to desktop apps, as opposed to the web, knowing that they wouldn't have to deal with 1234 different, obsolete versions because someone's grandma didn't update her system in years. After spending some time reading the exchanges on the posted link, I've come to the conclusion that the actual problem with snaps might not be snapd nor the automatic updating in and of themselves. Rather, the problem seems to be a scope mismatch. This whole snap thing looks to me as something that should be aimed squarely at the "desktop user". I use that term as opposed to "system use". So distributing Spotify or whatever via snaps? Great! LXD for a home user to test? Sure! But as a way of managing low-level system components on production boxes? No way! So I have to say I don't necessarily take an issue with Ubuntu pushing this on the desktop version. Sure, it is a pain by certain aspects, main one being slow startup for apps. But pushing this on Ubuntu Core in its actual state is, to me, the real issue. Sure, apparently you can run your own "Snap Proxy" or whatever they call it, which allows you to manually approve upgrades, etc. But why go through this trouble? It seems easier to just run apt-get from a central location when you want and for the packages and versions that you want.

Izkata 6y ago

> Snap is auto-updating and you can't stop it Kill the daemon and make it non-executable. Only restore it when you want to manually do an install.

AnIdiotOnTheNet 6y ago
What is this, Windows 10?
- hansvm 6y ago
  I wish Windows 10 were that nice. First you need a nice race condition to break the updater's updater's unauthorized change prevention service....
  - a1369209993 6y ago
    Boot into your linux install, dd /dev/random onto the executables, done.
xet7 6y ago
Huh? I think it's easier to just add to /etc/hosts this line: 127.0.0.1 api.snapcraft.io

viraptor 6y ago

On paper snap is great, but at this point we've got better alternatives. If you want to use something snap-like either flatpak or appimage will likely work and be way less user-hostile.

vladvasiliu 6y ago
I didn't look closely into either flatpak nor appimage. But I get the advantages of such a system and I think it might actually help with the "Linux on the desktop situation". It's very easy to deploy something with restricted access to the file system, something that has all its dependencies in one place, that updates atomically, etc. It's also nice for random app vendors to be able to know that all their users are on the latest version, or not far behind. Could even push some devs to consider going back to desktop apps, as opposed to the web, knowing that they wouldn't have to deal with 1234 different, obsolete versions because someone's grandma didn't update her system in years. After spending some time reading the exchanges on the posted link, I've come to the conclusion that the actual problem with snaps might not be snapd nor the automatic updating in and of themselves. Rather, the problem seems to be a scope mismatch. This whole snap thing looks to me as something that should be aimed squarely at the "desktop user". I use that term as opposed to "system use". So distributing Spotify or whatever via snaps? Great! LXD for a home user to test? Sure! But as a way of managing low-level system components on production boxes? No way! So I have to say I don't necessarily take an issue with Ubuntu pushing this on the desktop version. Sure, it is a pain by certain aspects, main one being slow startup for apps. But pushing this on Ubuntu Core in its actual state is, to me, the real issue. Sure, apparently you can run your own "Snap Proxy" or whatever they call it, which allows you to manually approve upgrades, etc. But why go through this trouble? It seems easier to just run apt-get from a central location when you want and for the packages and versions that you want.