15 ms·

Snap updates happen without user consent

274 points by smallerfish 4y ago

exabrial 4y ago
This a "feature not a bug".
- JohnFen 4y ago
  Then it's Broken As Designed?
Moissanite 4y ago
Snaps continue to puzzle me. I have shifted away from Ubuntu (partially because of the attitude attached to pushing snaps) and so I pay less attention than I might have done previously - but I've never seen anyone from Canonical offer a compelling argument for what benefits snaps offer. Most of the notional benefits of bundled app tools like snap and flatpak have either been refuted or have balancing downsides, so what is left? Just continuing to do it out of stubbornness is a really sad but seemingly quite likely possibility.
- geekbird 4y ago
  IMO it's just new for the sake of newness. Apt and dpkg work fine, but some folks feel they have to reinvent the wheel, I guess to beef up their resume or be more like MS or Apple. If they want to write MS or Apple style software, they need to just go and work for those companies. Apparently some people think that Linux should be just as deterministic and user limiting as proprietary software. I don't understand it, personally.
- matkoniecz 4y ago
  Snap is a proprietary system owned by Canonical. The server is not open source, only they can run Snap Store. That is why Canonical pushes it. And `sudo apt update && sudo apt upgrade` CLI log now includes an ad: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1992026 https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-t...
  - rightbyte 4y ago
    We saw this coming as soon as they included the Amazon ads in the start menu. As they are remotely breaking users' systems too I see no need to recommend Ubuntu as a newbie friendly distro anymore either.
fake-name 4y ago
My ubuntu setup script includes: # Goddammit ubuntu sudo apt-get purge snapd -y; sudo apt-get autoremove -y; echo "Package: snapd" | sudo tee /etc/apt/preferences.d/block-snap echo "Pin: release *" | sudo tee -a /etc/apt/preferences.d/block-snap echo "Pin-Priority: -1" | sudo tee -a /etc/apt/preferences.d/block-snap Uninstalls and permanently blocks the underlying `snapd` package so it will not be reinistalled. It might "break" some packages that depend on snapd, but as far as I'm concerned they're already broken by virtue of being snap packages. Realistically, with ubuntu dropping the old (text-mode) installer for ubuntu server, I'll probably basically stop using it altogether after 20.04. I've tried the Ubiquity (gui) installer several times across several virtualization hosts (Xen, KVM), and somehow I've never had it /actually work/. It always managed to crash or loop at some point.
jerome-jh 4y ago
"Close the app to avoid disruptions" is just laughingly stupid. This is a bit harsh to say it this way ... but it is. Yet another point, which is related to all the valid remarks already done: it is quite painful to have this notification seconds after Firefox had been launched. Why the update system did not notice Firefox required an update before it launches it? Technical points left aside: when an application requires an update (Chrome, IE), it performs it before launching, not after it has launched.
avnigo 4y ago
Every time I get those notifications now, I have to remember to close down the application, and go run `snap refresh`. There's literally no other way to make sure the update won't quit my application other than hope it's not running when the update will be applied in 2 weeks. A better—although arguably still horrible—notification would be to tell you when the application is actually scheduled to be updated so you know when to have it closed. Telling you that you need to have it closed at an indeterminate time 2 weeks from now or else fear "disruption" is clearly not good enough. Who thought this was an acceptable process for a user to follow and not an utter dealbreaker? Should we still call this snap growing pains? Updates should always only be applied when the application is starting. If there's a new update, a notification would just tell me to restart the application to have the update applied.
LinAGKar 4y ago
Why does it even need to stop the application before updating, that seems like a deficiency in snapd. Shouldn't it keep the application running from the old image, and install the new image side by side with it, so it launches from the new image when you restart the application. I think that works for flatpak.
sneak 4y ago
This means that they enable RCE, technically speaking, if the user is not involved in the upgrade. Uninstalling Snap is the first thing I do on Ubuntu these days.
moffkalast 4y ago
Oh snap
SQueeeeeL 4y ago
This is a very narrow perspective coming from someone who gets forced to use snap to install very specific packages, but snap always kind of gives off... I'm not sure how to verbalize this other than "bad vibes", especially compared to it's package management competition in aptitude. Is this a common experience or am I crazy?
- kelnos 4y ago
  I think the bad vibes come from the fact that Snap is a proprietary, walled-garden system owned by Canonical. The server is not open source, so no one else can run their own Snap Store. It's antithetical to pretty much everything about what we think of as a "Linux distro". I would absolutely never run Ubuntu or install Snap because of this. I'll stick with Debian, thanks.
  - Darmody 4y ago
    I think it's not only that. In my opinion is also about how Canonical handles everything. Everyday they look and act more like Microsoft. Empty words to sell you something, to convince you they're better. You can't really act like Microsoft with people that are using your OS because they ran away from Microsoft and expect them to shut up.
    - matkoniecz 4y ago
      For example `sudo apt update && sudo apt upgrade` CLI log now includes an ad see https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1992026 https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-t... It advertises some Commercial product by Canonical and /r/linux subreddit.
      - rpgmaker 4y ago
        Didn't know it had gotten that bad. I stopped using it when it was clear the desktop was no longer a priority for them. Not blaming them since they're a private company but with so many alternatives there's no need to use a second class Linux "desktop". Fedora is more than great imho.
psanford 4y ago
This is one of the main reasons I've switched from Ubuntu to NixOS.
- wging 4y ago
  PopOS also doesn’t use Snap — that’s one of the reasons I like it.
Barrin92 4y ago
Personally I don't have an issue with the auto-updates and like them quite a lot. It automates something away that I do by routine anyway. If the default switched to making holding updates back explicit that would be a big improvement in my book. In particular from a security perspective.
- mikro2nd 4y ago
  But everybody's not you. Sometimes we're on expensive, metered bandwidth. Sometimes we're in an online business meeting. Sometimes we're giving/about to give a presentation. Sometimes we're under deadline pressure and can't afford the additional time and stress of a potentially-breaking upgrade. We have lot's of times when we'd really rather postpone an upgrade, for perfectly legitimate reasons. We get the security issue, we'll upgrade when the timing is better. Just don't take that decision out of our hands. Totally automated upgrades are an evil (unless there's an explicit opt-in) and must die.
avg_dev 4y ago
hmm... https://snapcraft.io/docs/keeping-snaps-up-to-date https://snapcraft.io/docs/keeping-snaps-up-to-date > Snaps update automatically, and by default, the snapd daemon checks for updates 4 times a day. Each update check is called a refresh. i don't know when that line made it into the docs. i could be wrong but i actually thought that being evergreen was one of the selling points of snaps, and was advertised early on. an edit: sorry upvoters - i went ahead and read the article now. i actually believe now that the article author has a point. to summarize: while it will display a notification to the user about two weeks ahead of time, announcing that an update is scheduled and that the user should close the app to avoid disruptions (the author has some valid complaints about this notification, i think), at the end of the period, the app will be killed - potentially causing unsaved data to be lost - and updated. i believe in many cases this behavior is undesirable. it probably should be discussed and a better alternative proposed. i do take issue with the author's vehemence against (and manner of expressing such for) the notification, but i suspect i would be quite angry too if i were either an application maintainer fielding complaints about something that i didn't break, or a user who was angry to have lost some data.
- tonto 4y ago
  the repeated notifixation message from snapd that i need to close the app is really bad IMO...and e.g.closing firefox does not make the message go away(??), its very confusing
  - avg_dev 4y ago
    https://news.ycombinator.com/item?id=33854332 https://news.ycombinator.com/item?id=33854332 applies here too
- sgc 4y ago
  That notification is antithetical to most everything involved in my choice of Linux over Windows or macOS. It is invasive and takes away user control.
  - avg_dev 4y ago
kelnos 4y ago
I don't really have a problem with this in general, if a few rules are followed (that Canonical/Snap have apparently not even remotely bothered to address): 0. First off, the user should have to opt in to automatic updates. This should never be forced. 1. The update should never cause unsaved work to be lost. This means that the auto-updater should never kill the application unless it knows that it can start back up in exactly the same state before it was killed. Some apps will do this normally (some requiring configuration first), like Firefox, but others cannot. That's actually something I think apps should be required to have: there should be a standardized "snapshot-kill-restart" interface (perhaps some DBus thing) that allows for this. The old X11 session management system was designed for this, but in practice implementations are always buggy to some extent. 2. The app should be restarted after being updated, especially if it's happening in the background outside of user control. 3. The app should never be killed while the user is present and doing something. It should only happen while the machine is idle. If there's never an opportunity for that (say, the user always puts the computer to sleep rather than leaving it idle), then the update mechanism must resort to popups that ask for consent to do the update right then. The consent should only last for that single instance. 4. Updates can't ever break things. Auto updates should be reserved for security and critical (like data-loss) bugfixes only. All other updates should be voluntary. (I'd reluctantly make an exception for the case where there are security issues that need to be fixed, but it's not possible to backport those fixes, so a "security update" becomes a straight version update. Nothing is perfect.) A big part of why users don't like automatic updates is because they break things or remove features too often. Stop doing that, and users will start to trust the auto-update mechanism again. (And point #0 will stop being an issue: users will be happy to enable auto-updates. And maybe at some point I'd even drop #0 and think it's ok for vendors to enable auto-updates by default.) Regarding killing apps that need to be updated, most do not need to be killed at all, and can be safely updated underneath the running instance. Yes, there would need to be some mechanism to ensure the OS has paged all of the executable into memory (don't want "Text file busy" errors when trying to overwrite binaries), but this doesn't feel like a huge deal. Some apps do need to be restarted, as they dynamically load and unload UI resources from disk as the user uses the app, and those files changing underneath a running instance would cause problems. If this was an unpaid, volunteer project, I could certainly understand that the auto-update process would be unpolished and not the best. But Snap is owned by Canonical, and if they're serious about this, they need to get their shit together and actually focus on UX... ironic, since that was originally the entire point of the company in the first place: make a Linux distro with a polished UX that non-techie people would feel comfortable using.
bvhvhfcgxfdf 4y ago
How is it different from Google forcing everyone to upgrade Chrome?
- kelnos 4y ago
  Do they, though? I use Firefox, but my understanding is that Chrome just puts a button in the corner of the window that you can click to restart and install the updates, but it doesn't ever force you to do it, and you could conceivably continue running that way for as long as you want (well, until you end up rebooting the computer for whatever reason). I could be wrong, though.
- deleted 4y ago
  [deleted]
- signaru 4y ago
  I use both browsers on Ubuntu and Chrome never caused me any unpleasant update interruptions. The Firefox binary from mozilla.org is far less invasive, btw.
loloquwowndueo 4y ago
The UX can definitely be improved but the vitriol against this snap feature is puzzling, since the core of it (what in snap jargon is called “refresh awareness”) was implemented specifically because the alternative (silently updating the app from under the user which resulted in strange bugs, crashes and other problems) was pretty undesirable. In essence refresh awareness was added at users’ behest :)
- quercusa 4y ago
  As mentioned in the article, the instructions are just plain misleading/wrong. Shutting down the app does not cause a refresh. Shut down and restart and you'll get another pop-up in 6 hours.
- asdajksah2123 4y ago
  Neither approach is necessary. There are other approaches which work just fine. Ubuntu does not get credit from going from the worst option possible to the next worst option possible.
streptomycin 4y ago
Third, the notification has one call to action: shut down the application. This application will be updated, so shut it down. If the user closes the application, presumably that then triggers it to be updated, right? But no: the snap updater runs on a schedule, and it could take 6 hours for it to run again, check whether the application is running, and then apply the update if it’s not. Is the user supposed to leave the application shut down for up to 6 hours? How could they possibly know to do that? You could see a user getting into a cycle (for 13 days!) where they restart the application, and then 6 hours later the intrusive (and apparently not suppressible) notification pops up again. I thought the same thing the first time I saw it. The only solutions are to either close Firefox and wait for several hours for something to silently happen in the background, or Google for the CLI command to run to update it. Really bizarre UX, I would love to hear someone from Canonical explain why they thought that was a good idea. Is there something I'm missing?
- pull_my_finger 4y ago
  What you're supposed to do is close the application then run "snap refresh", but there is absolutely no hint that this is what you have to do. I had to look it up online as well. A sane person, in 202X would assuming closing the application would immediately trigger the update, as you said.
- xahrepap 4y ago
  I’ve also been annoyed by this. I don’t have it handy but I did find the ticket where their conversation to implement this first happened. I guess before it would just update without notifying the user. The idea in that conversation was, at least what I took away from it, that the user gets the notification and now knows at the end of the day they should close the app and in the morning it’ll be updated! Seems fine on paper. But the messaging in the notification doesn’t tell me that at all. And it turns out despite all the nagging I always forget to close things before I step away. I hate the execution of this feature. So much. All the nagging. All the confusing messaging. On top of it all, I don’t feel like snap gives me any qol improvements in exchange.
  - 4y ago
wging 4y ago
Another reason I hated snap, when I used Ubuntu, was the performance problems. Opening a url from the snap version of Slack took multiple seconds! The solution to this was to nuke it and install the .deb version. Just completely unacceptable and embarrassing.
protoster 4y ago
It's a mystery to me how Firefox updates on Ubuntu. Sometimes it goes through auto updates, but sometimes I'll try to open a new tab and it tells me that it will NOT allow me to do that until I restart. This is exceptionally annoying and not something that happens on Windows. What is this related to?
- BeefWellington 4y ago
  IME Firefox does this when the OS updates packages that Firefox depends on and/or changes FF version. I can't speak to Ubuntu specifically but I've seen the same behavior on Arch and Fedora and it's always around OS updates that I've triggered manually.
  - Izkata 4y ago
    Ubuntu (at least pre-snap) has Firefox in unattended-upgrades so apt can update Firefox in the background even if the user never runs updates themselves.
- mlvljr 4y ago
- pxc 4y ago
  On Windows, Firefox can't be updated while it's running because the files that comprise it are locked by the running application. On Linux, you can delete or replace open files, and even running applications. Instead of updates being handled by dozens of individual updaters that coordinate closely with each app so that updates happen between restarts, updates happen in the background without really coordinating with running apps. Sometimes, after Firefox has been updated, there's some kind of incompatibility between the old running binary and the new assets (internal JS, CSS, and idk what else). In that case, Firefox can't open new tabs because you're still running the old binary, which doesn't work with the new assets which have been installed, or which is looking for old assets that it opens dynamically at runtime that are simply no longer present on your disk.
  - 4y ago
stillkicking 4y ago
One thing I find funny is the problem of data loss. On macOS, it's been the norm for years that applications retain their state when quit and re-opened, including unsaved documents. While weird when introduced, in hindsight this is exactly the right behavior, because it is the most user-friendly and it makes e.g. software updates a non-issue. Even apps like iTerm can be updated and restarted in-place, retaining all the sessions. It's a testament to how bad Linux UX still is that this sort of idea is not only utterly alien, but instead some developers thought it was acceptable to kill running apps outright.
- pxc 4y ago
  > Even apps like iTerm can be updated and restarted in-place, retaining all the sessions. iTerm doesn't retain sessions at all. It just presents a facade resembling preserved sessions. Close iTerm2 while you have a tmux session open, or some SSH connections, or any long-running command. Those sessions and their processes die when you close iTerm. Maybe iTerm can approximate some of those things if iTerm is actually running the whole show, i.e., iTerm mediates launching your tmux sessions and your SSH connections. But imo those features are underwhelming and oversold.
  - iggldiggl 4y ago
    And browsers, too, are only semi-reliable at restoring any sort of more complex page with significant dynamic contents, because that requires the cooperation of the website itself and in practice relying on that is a crapshoot.
robertelder 4y ago
Since we're on the topic of snap updates: A couple weeks ago I was working away in the terminal when all of a sudden, my USB camera turned on and its light started flashing at me indicating something had just started interacting with my webcam. I immediately assumed "Oh, that's probably just some hackers watching me through my web-cam.", so I looked through /var/log a bit and noticed that it had just re-detected all USB devices and two new users had just been added to my system: snapd-range-12345-root:x:12345:12345::/nonexistent:/usr/bin/false snap_daemon:x:12345:12345::/nonexistent:/usr/bin/false Does anyone know what these new users are for, and why they were added just now instead of at install time? I googled a bit, but couldn't find any recent news about it.
- JonChesterfield 4y ago
  Seems totally legitimate for a proprietary package manager to take control over your webcam.
  - forgotpwd16 4y ago
    >proprietary package manager The client is foss. The store is proprietary. The store isn't required to install or/and distribute snaps.
- fulafel 4y ago
  Ubuntu system user accounts use the <1000 range of user ID numbers which you can see looking at /etc/passwd. Unlike this 12345 uid listed above. On the other hand this username is mentioned in a snap dev forum: https://forum.snapcraft.io/t/system-usernames/13386 https://forum.snapcraft.io/t/system-usernames/13386 - but there it says it should be using the 524288-589823 uid range...
- numeromancer 4y ago
  It was the hacker known as "Canonical".
matkoniecz 4y ago
Snaps also create extreme litter in filesystem, some programs like Firefox are broken in confusing way by updates (new tabs are crashing without explanation, part of old tabs crashes), some programs like Telegram were completely broken at some pint in highly confusing ways... Also, as mentioned by others - Snap is a proprietary, walled-garden system owned by Canonical.
- dstein9 4y ago
  What made me drop snaps is it wouldn’t let me access files outside of $HOME no matter what I tried, and the snap decided I was running Gnome instead of KDE no matter what I tried, going back to the .deb worked perfectly.
deleted 4y ago
[deleted]
chazeon 4y ago
This sounds exactly like Canonical's doing these days. Recently found I was asked to teach a workshop to help student use Kenya's KENET vlab, it is a vm platform from Kenya's education network, to run our program. Their system have some prebuild image for us to use including Ubuntu. Probably because of lacking of fund, their vms are low-performance QEMU-based machines. I fired up Ubuntu vm and find: 1. `snapd` running constantly in the background and eating up a lot of memory. So the first thing I have to do is to stop snapd. 2. `unattended-upgrades` keep running. I guess is their internet not good so it seems it runs for a long time and keep eating bandwidth and cpu. Things like these keep making me loosing faith on Ubuntu. I remember the name Ubuntu borrowed its root from African language, but it seems their system are not so friendly to the users (including students, educators) from African countries.
- user3939382 4y ago
  I've been away from Linux for a while and was looking at Ubuntu the other day. Huge download size, huge minimum resources, background processes phoning home constantly. IMHO this is what Linux is there to fight. The system should be reasonably knowable and controllable by the user, especially a technical one like myself. If I want a byzantine labyrinth of processes phoning home and eating up all my system resources I'll use macOS or Windows.
- JonChesterfield 4y ago
  Unattended upgrades holds a lock that apt uses while downloading. Shouldn't, does. So a really common experience is turn on a machine, apt install foo, blocked by the updates, anger. Helps a little that apt now tells me what is holding the lock, but it's always unattended upgrades. Which somehow has come back to life after attempts to disable it.
- rightbyte 4y ago
  This is the problem with user hostile systems that think they know better than the user. You have no control and can't get a stable system. And since things change automatically you have no clue what made stuff broken. I can vision the condescending and smug guy on Canonical forcing auto updates (remote code execution) by default as some "security" measure.
xkcd-sucks 4y ago
Shortly after the push to manage everything through snap, I set up ubuntu server and installed docker, to support a client facing demo involving a few containers. A few hours before the demo snap updated docker to a version that was totally broken and there was much embarrassment. That day I gave up on Ubuntu completely and never looked back.
- avg_dev 4y ago
  what do you use now?
  - xkcd-sucks 4y ago
    Mostly....... PopOS with KDE, lol, the 3rd party driver installation convenience is really nice. Or plain old debian for server stuff.
  - jetbalsa 4y ago
    Debian, Debian all the way
- remram 4y ago
  On a friend's machine, Ubuntu had somehow managed to install both the APT docker and the Snap docker. This caused the entire disk to fill with log messages from the snap docker trying and failing to start, since another docker was already running. Removing snapd is the first thing I do on any Ubuntu machine now, whether mine or my friends'. This now requires adding a PPA for Firefox since 22.04 but otherwise I have never had to deal with snap again.
jrm4 4y ago
I don't like Ubuntu anymore, but not because of "how it operates." More because of "how it operates, without being forthcoming about what its new purpose is, which is not 'everybody's Linux.'" You're trying to be a tool to support big corporate IT. That is absolutely fine, good even. Getting more Linux in that space, under Ubuntu's name, seems pretty cool. But you're no longer "the people's choice" when you behave that way. They're putting in big grown up restrictions and ideas and methods of doing things, and they just need to be honest about that.
boppo1 4y ago
I use Xubuntu and snap just gets in my way. With Apt everything is transparent and 'just werks' or at least indicates what to fix. Snap has been the opposite in my experience and especially seems to make program interop more difficult. It seems like Canonical said "Apple and Microsoft have (painful) app stores that cater to the non-technical, we need one too!"
noasaservice 4y ago
Reminder for you Ubuntu(and XUbuntu and KUbuntu) people: Snap is closed source garbage ware, with MS Windows forced updating and the terribleness of being 10x slower.... So here's how to "Snap-Off" your system https://haydenjames.io/remove-snap-ubuntu-22-04-lts/ https://haydenjames.io/remove-snap-ubuntu-22-04-lts/
- INeedMoreRam 4y ago
  I desnapped my Kubuntu machine successfully per those instructions.
gjsman-1000 4y ago
I used Ubuntu since 11.04. I abandoned it for Fedora. Everything about Ubuntu now is seemingly defined by a spirit of defiance from Fedora. They borrow PipeWire and SystemD, but uglify GNOME, replace Flatpak with Snap, and use *.deb instead of *.rpm. Otherwise it feels mostly the same. I looked at the Fedora ecosystem and... it's basically just like Ubuntu's point versions, and instead of an LTS every 2 years, you get one every 5 years and it's called Rocky Linux / AlmaLinux. Why pick Ubuntu instead of (basically) upstream? I'll pick the same thing with prettier GNOME and Flatpak instead of the weird mystery lump Ubuntu is now.
- macksd 4y ago
  >> Why pick Ubuntu instead of (basically) upstream? "Upstream" for Ubuntu is more like Debian, which is the basis for MANY distros (much like Red Hat - founded around the same time as Debian - and the .rpm ecosystem is a significant core component of many systems including current versions of SuSE, etc.). Ubuntu has traditionally been a slightly more newbie-friendly / commercial-friendly version of Debian. I don't think many of the changes you're describing were really trying to defy Fedora, especially not the choice to use .deb over .rpm. That said, I did use Fedora for a while when Ubuntu started messing with Gnome a lot and I found it very refreshing, easy and reliable. It's a great distro, but the relationship between the two is absolutely not "upstream" and "downstream".
  - pxc 4y ago
    What they mean is not 'upstream' with respect to distro tooling, but Fedora's closer relationship to the upstream components of the stack desktop stack (GNOME, PipeWire, SystemD, etc.), which are often entirely or in part maintained by Fedora contributors or Red Hat employees, etc. The 'defiance' they're talking about are the projects that Canonical has developed, often in secret, which are or were essentially alternatives/competitors to the components of the Linux free desktop stack which have been developed in the open, often at Red Hat and developed on Fedora. The cases that come to mind are: - Unity vs. GNOME 3 - Upstart vs. Systemd - Mir vs. Wayland - Snap vs. Flatpak The Canonical entries all appear as sort of NIH latecomers, whereas their competitors have generally been developed in an upstream-first, 'release early' kind of way. In each case, the tech opposite Canonical's has been shipped on Fedora, before eventually becoming the default in Ubuntu anyway. (Snap has yet to go.)
mkasberg 4y ago
The way Snap updates packages caused some problems with Firefox on recent versions of Ubuntu - I wrote a blog about it: https://www.mikekasberg.com/blog/2022/03/21/how-to-fix-firefox-crashes-on-ubuntu-21-10.html https://www.mikekasberg.com/blog/2022/03/21/how-to-fix-firef... Perhaps this update mechanism was part of the solution to some of those problems...
edgyquant 4y ago
Yet another sketchy and unprofitable company that has been subsidized so that it can act as the intermediary for human (teenage really) discussion.
- 83 4y ago
  Ubuntu Snap (package management). Not Snapchat
  - smallerfish 4y ago
    I had "Ubuntu" in the title of my HN submission originally for this reason, but HN admins changed it (I guess to line it up with the blog post).
jgneff 4y ago
You can now completely disable automatic updates of Snap packages. [1] [1] https://snapcraft.io/blog/hold-your-horses-i-mean-snaps-new-feature-lets-you-stop-snap-updates-for-as-long-as-you-need https://snapcraft.io/blog/hold-your-horses-i-mean-snaps-new-...
- jacquesm 4y ago
  Give this man a medal. Thank you. To update to this version use: snap refresh --channel=edge snapd snap refresh --hold to get rid of automatic updates.
  - smallerfish 4y ago
    Yeah I mention this towards the end of my rant (in the article) but it's a) not available yet and b) not clear whether it'll actually notify you when there are updates to be made. I'm guessing it expects you to unhold at some point to get "refreshes".
    - jacquesm 4y ago
      I'm fine with that. Nothing drives me more mad than to be in the middle of an interview taking notes and then suddenly land in an endless loop of being forced to restart my browser. It's not like some of us don't have work to do while we're in the browser and the utter disrespect by the designers of this crap to the detriment of their users is baffling. This is one thing where commercial software has something of an edge over FOSS: you can't even threaten to withhold your $ if they misbehave. Power to the user.
- AnIdiotOnTheNet 4y ago
  Canonical watched this exact same shit play out with Microsoft and Windows yet decided to do the exact same thing. Mind boggling.
  - curt15 4y ago
    Maybe they were trying to take a page from Microsoft's business model; take control away from users only to sell it back as an "enterprise edition" brand store.
danbmil99 4y ago
I struggled mightily with Firefox's tendency (on Ubuntu) to suddenly and (at least until recently without any notice) tell me "Firefox must restart right now, and will make a feeble/futile attempt to restore your pages". Terrible, terrible UX. Finally, I just uninstalled the snap version and downloaded/installed the .deb manually. So far so good -- I guess some day I might get hit with a security problem or some must-have feature, but at least I don't randomly have to restart Firefox every few weeks without prior notification.
- Izkata 4y ago
  Firefox has a built-in upgrade mechanism that doesn't rely on a package manager. I don't know if the .deb has it active, but it's worth checking, so if it is active you wouldn't have to worry about it.
- 0cf8612b2e1e 4y ago
  I think you can point a direct line to that behavior and me installing PopOS. A web browser is my most used application and Ubuntu thinks they have the right to effectively crash it unexpectedly.
  - ilyt 4y ago
    They took thing people hated in windows update and ported it to ubuntu lmao
- asddubs 4y ago
  you can use this ppa to keep it updated https://launchpad.net/~mozillateam/+archive/ubuntu/ppa https://launchpad.net/~mozillateam/+archive/ubuntu/ppa
  - FullyFunctional 4y ago
    Thanks, but personally I don't want a workaround. I want a distribution that does the right thing. I have used Ubuntu for decades and use it everywhere. I hate to have to change, but as always, good things don't last.
signaru 4y ago
For those who are getting their Firefox messed up, the binary from the Mozilla site works just fine and is far more respectful. I'm using Mate 22.04 LTS. A few settings has to be done to disable updates behind your back, but at least these settings persist, unlike when I was using Snap or whatever it was I managed to install via apt (I think it still eventually reverted to Snap). There was also the issue that the Snap version disables some extensions (sure they are potentially dangerous, but that risk is for me to take). Now, I just manually update Firefox at convenient times via the Help -> About menu.
- mxmlnkn 4y ago
  That's also the solution I use. Especially because I have multi-rows set up in Firefox and each update breaks this. Plus, when installing the binaries manually, you can also apply some "hidden" settings by creating a distribution/policies.json file inside the firefox installation folder. This is what mine contains: { "policies": { "DisableAppUpdate": true, "DisableFeedbackCommands": true, "DisableFirefoxAccounts": true, "DisableFirefoxStudies": true, "DisablePocket": true, "DisableSetDesktopBackground": true, "DisableTelemetry": true, "NoDefaultBookmarks": true } } It's kinda sad how many settings you have to configure not only here in order to not be nagged constantly. It's like you are fighting against your tools.
  - geekbird 4y ago
    That's why I hate Snap. In Linux, unlike Windows or Mac, I should not have to fight my tools in order to configure a system the way I want it. Yet Ubuntu makes me do it every goddamn time for anything on the desktop, between snap and their nasty "Unity" desktop.
sockaddr 4y ago
I was struggling with this annoyance recently and today decided to finally uninstall the snap. The “close now” is super annoying. I ran “sudo apt install firefox” and it installed a freaking snap! Today I learned that Ubuntu just decides to install snaps instead of the apt package. What the hell.
- cybrexalpha 4y ago
  I moved from Ubuntu to Debian because of snaps. I keep apt and the majority of my knowledge of how to run the system, but no snap.
- dublinben 4y ago
  You might prefer Pop! OS, which is based on Ubuntu, but uses flatpak instead of snaps.
  - poszlem 4y ago
    Just to add a data point, I recently went back to Linux after spending years in the MacOS world. Installed Ubuntu out of habit, got the exact same thing happen to me (removed snap, installed firefox through apt, got snap back) and went to Pop OS. Could not be happier with the overall system and still very much disgusted by what Ubuntu decided to do.
    - alpaca128 4y ago
      I've had bad luck with PopOS, but it defniitely has one of the most reasonable and user friendly configurations out of the box.
    - brainchild-adam 4y ago
      Welcome back to Linux! What made you switch from macOS?
      - petre 4y ago
        Not OP but the desktop is super annoying for advanced users with too much mouse usage and things that are super easy in Linux to install from packages require Macports or brew pulling out N squared dependencies.
alkonaut 4y ago
Why would Snap kill the running application when the update is pushed? Any system for self-updating applications needs to install the new version side by side with the existing one anyway. So what’s the reason for terminating the running instance?
- userbinator 4y ago
  They've adopted Microsoft's approach of trying to hold users on a leash and beat them into submission.
  - alkonaut 4y ago
    Microsoft’s self updating desktop apps (Teams etc) switch silently on restart. Unsure about their store apps but I imagine it’s the same thing. With older windows desktop apps which install to privileged locations like %programfiles% it’s more complex. But that’s the point: snap is a new system. It should be well designed because of it, and be on par with “modern” install systems. It feels strange if they restart for no reason. And it feels equally strange if they have a design that requires it.
compsciphd 4y ago
I'll just reference my rant from a month and a half ago - https://news.ycombinator.com/item?id=33275206#33277156 https://news.ycombinator.com/item?id=33275206#33277156
azornathogron 4y ago
The article mentions Snap, AppImage and FlatPak, but there is also a much older system called 0install (zero install) that was started in 2003 or so [1]. I wonder why that never took off. [1] https://zero-install.sourceforge.net/roadmap.html https://zero-install.sourceforge.net/roadmap.html (note this is the old website; the new website is https://0install.net https://0install.net - looks like it's still getting releases in October this year)
Animats 4y ago
The restart notification system is so lame that I get notifications that the snap daemon needs to update itself and I should close the snap daemon. Which is not something I opened. What am I supposed to do, kill the process?
xg15 4y ago
Apparently forcing updates is sort of the core of Snap's philosophy. To the point that they rather added a whole host of config options that lets you specify various "work periods", "postponements" and other temporarily exceptions than just give you the ability not to update. See the discussion here: https://forum.snapcraft.io/t/disabling-automatic-refresh-for-snap-from-store/707 https://forum.snapcraft.io/t/disabling-automatic-refresh-for... Edit: ...or not anymore: https://news.ycombinator.com/item?id=33836216 https://news.ycombinator.com/item?id=33836216
- Taniwha 4y ago
  Can I tell it what I consider my "home directory" is because snaps seem to limit me to what some bozo at canonical thinks is my home directory (rather the multiple volumes and symbolic links I've used for a couple of decades now)
dessant 4y ago
It's also alarming that GNOME extensions are updated in the background without user interaction, and the feature cannot be disabled. These extensions are not sandboxed, can run arbitrary commands, and have access to the entire system. Extensions are practically a backdoor for the entire GNOME user base that can be accessed by compromising the update server. https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2514 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2514
- forgotpwd16 4y ago
  I really hope the solution won't be GNOME purging extensions alltogether.
- Spivak 4y ago
  > access to the entire system It is bad but it’s not that bad, they are still running as your unprivileged user.
  - cprecioso 4y ago
    Relevant xkcd https://xkcd.com/1200/ https://xkcd.com/1200/
kkfx 4y ago
Snaps, Flatpacks etc are tools needed to push commercial CRAP in FLOSS systems. Period. The present "sorry state of packaging", largely due to the sorry state of storage (filesystems) stuck in the '80s in the bad sense of being simply largely obsolete for today's needs can be partially surpassed by NixOS/Guix model, witch is a FLOSS packaging model. Snaps and co on contrary are needed to push distro to irrelevance and allow closed source crapware, mostly filled up with outdated dependencies and horrendous hacks to speed up delivery times by some underpaid and under-competent developer, still fail to prove ANY other realistic purpose. Really: try to honestly weight their ideas and tell different conclusions if you can find something else. At first they say "we do compartmentalize anything for safety", than "ah, yes, we can't really isolate stuff because if you want just to open a damn pdf downloaded from a modern WebVM improperly named browser for legacy reasons you can't, so we start punching holes here and there" and thereafter even the effectiveness of formal isolation was depicted as not really safe. Then/aside another justification came up: pushing fresh software to distros who do not have manpower for quick enough maintainers. The actual snap store prove the contrary: most snaps are outdated and full of outdated deps, with potentially unpatched security vulnerabilities, of course. Oh, of course they can't package anything than apps, since kernel/userland can't be in a snap, so they need anyway a secondary packaging systems.
nanna 4y ago
Installed Ubuntu on a friend's laptop last weekend. Today her Firefox wouldn't open because snap was reporting it couldn't update it because it was already running. She restarted computer, same problem. She asked if she can "delete" snap. I'm a debian person, so not sure. Can she?
- matkoniecz 4y ago
  Why not install Debian on her laptop?
  - nanna 4y ago
    I was running out of time and the Debian installer needed non-free driver packages to be added. If I had more time I would've gone that route.
- usr1106 4y ago
  snap can be uninstalled. But then she needs Firefox from another source, there is no official .deb package any more. There is also the risk that some update or package installation will pull in snap again. Doable for a technical user who only runs apt from command line and always reads the dependencies before answering yes. Not suitable for non-technical users.
tgsovlerkhgsel 4y ago
What's the minimum effort way (i.e. without switching to another distro) to a) receive timely updates for Firefox b) without this bullshit? Sure, I can kill firefox, run the updater manually, then restart it, every time I see this popup, but that's pretty tiring.
- sph 4y ago
  Install Firefox from Flatpak. It comes straight from Mozilla, and it gets updates immediately.
- spiznnx 4y ago
  Go to firefox.com, download the tar.bz2, extract to /opt/firefox, and give yourself recursive ownership. Firefox will update itself.
crtasm 4y ago
I had been wondering about this new notification warning there's 12 days left to close snap-store. I don't have snap-store running!

274 points by smallerfish 4y ago

exabrial 4y ago

This a "feature not a bug".

JohnFen 4y ago
Then it's Broken As Designed?

Moissanite 4y ago

Snaps continue to puzzle me. I have shifted away from Ubuntu (partially because of the attitude attached to pushing snaps) and so I pay less attention than I might have done previously - but I've never seen anyone from Canonical offer a compelling argument for what benefits snaps offer. Most of the notional benefits of bundled app tools like snap and flatpak have either been refuted or have balancing downsides, so what is left? Just continuing to do it out of stubbornness is a really sad but seemingly quite likely possibility.

geekbird 4y ago
IMO it's just new for the sake of newness. Apt and dpkg work fine, but some folks feel they have to reinvent the wheel, I guess to beef up their resume or be more like MS or Apple. If they want to write MS or Apple style software, they need to just go and work for those companies. Apparently some people think that Linux should be just as deterministic and user limiting as proprietary software. I don't understand it, personally.
matkoniecz 4y ago
Snap is a proprietary system owned by Canonical. The server is not open source, only they can run Snap Store. That is why Canonical pushes it. And `sudo apt update && sudo apt upgrade` CLI log now includes an ad: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1992026 https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-t...
- rightbyte 4y ago
  We saw this coming as soon as they included the Amazon ads in the start menu. As they are remotely breaking users' systems too I see no need to recommend Ubuntu as a newbie friendly distro anymore either.

fake-name 4y ago

My ubuntu setup script includes: # Goddammit ubuntu sudo apt-get purge snapd -y; sudo apt-get autoremove -y; echo "Package: snapd" | sudo tee /etc/apt/preferences.d/block-snap echo "Pin: release *" | sudo tee -a /etc/apt/preferences.d/block-snap echo "Pin-Priority: -1" | sudo tee -a /etc/apt/preferences.d/block-snap Uninstalls and permanently blocks the underlying `snapd` package so it will not be reinistalled. It might "break" some packages that depend on snapd, but as far as I'm concerned they're already broken by virtue of being snap packages. Realistically, with ubuntu dropping the old (text-mode) installer for ubuntu server, I'll probably basically stop using it altogether after 20.04. I've tried the Ubiquity (gui) installer several times across several virtualization hosts (Xen, KVM), and somehow I've never had it /actually work/. It always managed to crash or loop at some point.

jerome-jh 4y ago

"Close the app to avoid disruptions" is just laughingly stupid. This is a bit harsh to say it this way ... but it is. Yet another point, which is related to all the valid remarks already done: it is quite painful to have this notification seconds after Firefox had been launched. Why the update system did not notice Firefox required an update before it launches it? Technical points left aside: when an application requires an update (Chrome, IE), it performs it before launching, not after it has launched.

avnigo 4y ago

Every time I get those notifications now, I have to remember to close down the application, and go run `snap refresh`. There's literally no other way to make sure the update won't quit my application other than hope it's not running when the update will be applied in 2 weeks. A better—although arguably still horrible—notification would be to tell you when the application is actually scheduled to be updated so you know when to have it closed. Telling you that you need to have it closed at an indeterminate time 2 weeks from now or else fear "disruption" is clearly not good enough. Who thought this was an acceptable process for a user to follow and not an utter dealbreaker? Should we still call this snap growing pains? Updates should always only be applied when the application is starting. If there's a new update, a notification would just tell me to restart the application to have the update applied.

LinAGKar 4y ago

Why does it even need to stop the application before updating, that seems like a deficiency in snapd. Shouldn't it keep the application running from the old image, and install the new image side by side with it, so it launches from the new image when you restart the application. I think that works for flatpak.

sneak 4y ago

This means that they enable RCE, technically speaking, if the user is not involved in the upgrade. Uninstalling Snap is the first thing I do on Ubuntu these days.

moffkalast 4y ago

Oh snap

SQueeeeeL 4y ago

This is a very narrow perspective coming from someone who gets forced to use snap to install very specific packages, but snap always kind of gives off... I'm not sure how to verbalize this other than "bad vibes", especially compared to it's package management competition in aptitude. Is this a common experience or am I crazy?

kelnos 4y ago
I think the bad vibes come from the fact that Snap is a proprietary, walled-garden system owned by Canonical. The server is not open source, so no one else can run their own Snap Store. It's antithetical to pretty much everything about what we think of as a "Linux distro". I would absolutely never run Ubuntu or install Snap because of this. I'll stick with Debian, thanks.
- Darmody 4y ago
  I think it's not only that. In my opinion is also about how Canonical handles everything. Everyday they look and act more like Microsoft. Empty words to sell you something, to convince you they're better. You can't really act like Microsoft with people that are using your OS because they ran away from Microsoft and expect them to shut up.
  - matkoniecz 4y ago
    For example `sudo apt update && sudo apt upgrade` CLI log now includes an ad see https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1992026 https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-t... It advertises some Commercial product by Canonical and /r/linux subreddit.
    - rpgmaker 4y ago
      Didn't know it had gotten that bad. I stopped using it when it was clear the desktop was no longer a priority for them. Not blaming them since they're a private company but with so many alternatives there's no need to use a second class Linux "desktop". Fedora is more than great imho.

psanford 4y ago

This is one of the main reasons I've switched from Ubuntu to NixOS.

wging 4y ago
PopOS also doesn’t use Snap — that’s one of the reasons I like it.

Barrin92 4y ago

Personally I don't have an issue with the auto-updates and like them quite a lot. It automates something away that I do by routine anyway. If the default switched to making holding updates back explicit that would be a big improvement in my book. In particular from a security perspective.

mikro2nd 4y ago
But everybody's not you. Sometimes we're on expensive, metered bandwidth. Sometimes we're in an online business meeting. Sometimes we're giving/about to give a presentation. Sometimes we're under deadline pressure and can't afford the additional time and stress of a potentially-breaking upgrade. We have lot's of times when we'd really rather postpone an upgrade, for perfectly legitimate reasons. We get the security issue, we'll upgrade when the timing is better. Just don't take that decision out of our hands. Totally automated upgrades are an evil (unless there's an explicit opt-in) and must die.

avg_dev 4y ago

hmm... https://snapcraft.io/docs/keeping-snaps-up-to-date https://snapcraft.io/docs/keeping-snaps-up-to-date > Snaps update automatically, and by default, the snapd daemon checks for updates 4 times a day. Each update check is called a refresh. i don't know when that line made it into the docs. i could be wrong but i actually thought that being evergreen was one of the selling points of snaps, and was advertised early on. an edit: sorry upvoters - i went ahead and read the article now. i actually believe now that the article author has a point. to summarize: while it will display a notification to the user about two weeks ahead of time, announcing that an update is scheduled and that the user should close the app to avoid disruptions (the author has some valid complaints about this notification, i think), at the end of the period, the app will be killed - potentially causing unsaved data to be lost - and updated. i believe in many cases this behavior is undesirable. it probably should be discussed and a better alternative proposed. i do take issue with the author's vehemence against (and manner of expressing such for) the notification, but i suspect i would be quite angry too if i were either an application maintainer fielding complaints about something that i didn't break, or a user who was angry to have lost some data.

tonto 4y ago
the repeated notifixation message from snapd that i need to close the app is really bad IMO...and e.g.closing firefox does not make the message go away(??), its very confusing
- avg_dev 4y ago
  https://news.ycombinator.com/item?id=33854332 https://news.ycombinator.com/item?id=33854332 applies here too
sgc 4y ago
That notification is antithetical to most everything involved in my choice of Linux over Windows or macOS. It is invasive and takes away user control.
- avg_dev 4y ago

kelnos 4y ago

I don't really have a problem with this in general, if a few rules are followed (that Canonical/Snap have apparently not even remotely bothered to address): 0. First off, the user should have to opt in to automatic updates. This should never be forced. 1. The update should never cause unsaved work to be lost. This means that the auto-updater should never kill the application unless it knows that it can start back up in exactly the same state before it was killed. Some apps will do this normally (some requiring configuration first), like Firefox, but others cannot. That's actually something I think apps should be required to have: there should be a standardized "snapshot-kill-restart" interface (perhaps some DBus thing) that allows for this. The old X11 session management system was designed for this, but in practice implementations are always buggy to some extent. 2. The app should be restarted after being updated, especially if it's happening in the background outside of user control. 3. The app should never be killed while the user is present and doing something. It should only happen while the machine is idle. If there's never an opportunity for that (say, the user always puts the computer to sleep rather than leaving it idle), then the update mechanism must resort to popups that ask for consent to do the update right then. The consent should only last for that single instance. 4. Updates can't ever break things. Auto updates should be reserved for security and critical (like data-loss) bugfixes only. All other updates should be voluntary. (I'd reluctantly make an exception for the case where there are security issues that need to be fixed, but it's not possible to backport those fixes, so a "security update" becomes a straight version update. Nothing is perfect.) A big part of why users don't like automatic updates is because they break things or remove features too often. Stop doing that, and users will start to trust the auto-update mechanism again. (And point #0 will stop being an issue: users will be happy to enable auto-updates. And maybe at some point I'd even drop #0 and think it's ok for vendors to enable auto-updates by default.) Regarding killing apps that need to be updated, most do not need to be killed at all, and can be safely updated underneath the running instance. Yes, there would need to be some mechanism to ensure the OS has paged all of the executable into memory (don't want "Text file busy" errors when trying to overwrite binaries), but this doesn't feel like a huge deal. Some apps do need to be restarted, as they dynamically load and unload UI resources from disk as the user uses the app, and those files changing underneath a running instance would cause problems. If this was an unpaid, volunteer project, I could certainly understand that the auto-update process would be unpolished and not the best. But Snap is owned by Canonical, and if they're serious about this, they need to get their shit together and actually focus on UX... ironic, since that was originally the entire point of the company in the first place: make a Linux distro with a polished UX that non-techie people would feel comfortable using.

bvhvhfcgxfdf 4y ago

How is it different from Google forcing everyone to upgrade Chrome?

kelnos 4y ago
Do they, though? I use Firefox, but my understanding is that Chrome just puts a button in the corner of the window that you can click to restart and install the updates, but it doesn't ever force you to do it, and you could conceivably continue running that way for as long as you want (well, until you end up rebooting the computer for whatever reason). I could be wrong, though.
deleted 4y ago
[deleted]
signaru 4y ago
I use both browsers on Ubuntu and Chrome never caused me any unpleasant update interruptions. The Firefox binary from mozilla.org is far less invasive, btw.

loloquwowndueo 4y ago

The UX can definitely be improved but the vitriol against this snap feature is puzzling, since the core of it (what in snap jargon is called “refresh awareness”) was implemented specifically because the alternative (silently updating the app from under the user which resulted in strange bugs, crashes and other problems) was pretty undesirable. In essence refresh awareness was added at users’ behest :)

quercusa 4y ago
As mentioned in the article, the instructions are just plain misleading/wrong. Shutting down the app does not cause a refresh. Shut down and restart and you'll get another pop-up in 6 hours.
asdajksah2123 4y ago
Neither approach is necessary. There are other approaches which work just fine. Ubuntu does not get credit from going from the worst option possible to the next worst option possible.

streptomycin 4y ago

Third, the notification has one call to action: shut down the application. This application will be updated, so shut it down. If the user closes the application, presumably that then triggers it to be updated, right? But no: the snap updater runs on a schedule, and it could take 6 hours for it to run again, check whether the application is running, and then apply the update if it’s not. Is the user supposed to leave the application shut down for up to 6 hours? How could they possibly know to do that? You could see a user getting into a cycle (for 13 days!) where they restart the application, and then 6 hours later the intrusive (and apparently not suppressible) notification pops up again. I thought the same thing the first time I saw it. The only solutions are to either close Firefox and wait for several hours for something to silently happen in the background, or Google for the CLI command to run to update it. Really bizarre UX, I would love to hear someone from Canonical explain why they thought that was a good idea. Is there something I'm missing?

pull_my_finger 4y ago
What you're supposed to do is close the application then run "snap refresh", but there is absolutely no hint that this is what you have to do. I had to look it up online as well. A sane person, in 202X would assuming closing the application would immediately trigger the update, as you said.
xahrepap 4y ago
I’ve also been annoyed by this. I don’t have it handy but I did find the ticket where their conversation to implement this first happened. I guess before it would just update without notifying the user. The idea in that conversation was, at least what I took away from it, that the user gets the notification and now knows at the end of the day they should close the app and in the morning it’ll be updated! Seems fine on paper. But the messaging in the notification doesn’t tell me that at all. And it turns out despite all the nagging I always forget to close things before I step away. I hate the execution of this feature. So much. All the nagging. All the confusing messaging. On top of it all, I don’t feel like snap gives me any qol improvements in exchange.
- 4y ago

wging 4y ago

Another reason I hated snap, when I used Ubuntu, was the performance problems. Opening a url from the snap version of Slack took multiple seconds! The solution to this was to nuke it and install the .deb version. Just completely unacceptable and embarrassing.

protoster 4y ago

It's a mystery to me how Firefox updates on Ubuntu. Sometimes it goes through auto updates, but sometimes I'll try to open a new tab and it tells me that it will NOT allow me to do that until I restart. This is exceptionally annoying and not something that happens on Windows. What is this related to?

BeefWellington 4y ago
IME Firefox does this when the OS updates packages that Firefox depends on and/or changes FF version. I can't speak to Ubuntu specifically but I've seen the same behavior on Arch and Fedora and it's always around OS updates that I've triggered manually.
- Izkata 4y ago
  Ubuntu (at least pre-snap) has Firefox in unattended-upgrades so apt can update Firefox in the background even if the user never runs updates themselves.
mlvljr 4y ago
pxc 4y ago
On Windows, Firefox can't be updated while it's running because the files that comprise it are locked by the running application. On Linux, you can delete or replace open files, and even running applications. Instead of updates being handled by dozens of individual updaters that coordinate closely with each app so that updates happen between restarts, updates happen in the background without really coordinating with running apps. Sometimes, after Firefox has been updated, there's some kind of incompatibility between the old running binary and the new assets (internal JS, CSS, and idk what else). In that case, Firefox can't open new tabs because you're still running the old binary, which doesn't work with the new assets which have been installed, or which is looking for old assets that it opens dynamically at runtime that are simply no longer present on your disk.
- 4y ago

stillkicking 4y ago

One thing I find funny is the problem of data loss. On macOS, it's been the norm for years that applications retain their state when quit and re-opened, including unsaved documents. While weird when introduced, in hindsight this is exactly the right behavior, because it is the most user-friendly and it makes e.g. software updates a non-issue. Even apps like iTerm can be updated and restarted in-place, retaining all the sessions. It's a testament to how bad Linux UX still is that this sort of idea is not only utterly alien, but instead some developers thought it was acceptable to kill running apps outright.

pxc 4y ago
> Even apps like iTerm can be updated and restarted in-place, retaining all the sessions. iTerm doesn't retain sessions at all. It just presents a facade resembling preserved sessions. Close iTerm2 while you have a tmux session open, or some SSH connections, or any long-running command. Those sessions and their processes die when you close iTerm. Maybe iTerm can approximate some of those things if iTerm is actually running the whole show, i.e., iTerm mediates launching your tmux sessions and your SSH connections. But imo those features are underwhelming and oversold.
- iggldiggl 4y ago
  And browsers, too, are only semi-reliable at restoring any sort of more complex page with significant dynamic contents, because that requires the cooperation of the website itself and in practice relying on that is a crapshoot.

robertelder 4y ago

Since we're on the topic of snap updates: A couple weeks ago I was working away in the terminal when all of a sudden, my USB camera turned on and its light started flashing at me indicating something had just started interacting with my webcam. I immediately assumed "Oh, that's probably just some hackers watching me through my web-cam.", so I looked through /var/log a bit and noticed that it had just re-detected all USB devices and two new users had just been added to my system: snapd-range-12345-root:x:12345:12345::/nonexistent:/usr/bin/false snap_daemon:x:12345:12345::/nonexistent:/usr/bin/false Does anyone know what these new users are for, and why they were added just now instead of at install time? I googled a bit, but couldn't find any recent news about it.

JonChesterfield 4y ago
Seems totally legitimate for a proprietary package manager to take control over your webcam.
- forgotpwd16 4y ago
  >proprietary package manager The client is foss. The store is proprietary. The store isn't required to install or/and distribute snaps.
fulafel 4y ago
Ubuntu system user accounts use the <1000 range of user ID numbers which you can see looking at /etc/passwd. Unlike this 12345 uid listed above. On the other hand this username is mentioned in a snap dev forum: https://forum.snapcraft.io/t/system-usernames/13386 https://forum.snapcraft.io/t/system-usernames/13386 - but there it says it should be using the 524288-589823 uid range...
numeromancer 4y ago
It was the hacker known as "Canonical".

matkoniecz 4y ago

Snaps also create extreme litter in filesystem, some programs like Firefox are broken in confusing way by updates (new tabs are crashing without explanation, part of old tabs crashes), some programs like Telegram were completely broken at some pint in highly confusing ways... Also, as mentioned by others - Snap is a proprietary, walled-garden system owned by Canonical.

dstein9 4y ago
What made me drop snaps is it wouldn’t let me access files outside of $HOME no matter what I tried, and the snap decided I was running Gnome instead of KDE no matter what I tried, going back to the .deb worked perfectly.

deleted 4y ago

[deleted]

chazeon 4y ago

This sounds exactly like Canonical's doing these days. Recently found I was asked to teach a workshop to help student use Kenya's KENET vlab, it is a vm platform from Kenya's education network, to run our program. Their system have some prebuild image for us to use including Ubuntu. Probably because of lacking of fund, their vms are low-performance QEMU-based machines. I fired up Ubuntu vm and find: 1. `snapd` running constantly in the background and eating up a lot of memory. So the first thing I have to do is to stop snapd. 2. `unattended-upgrades` keep running. I guess is their internet not good so it seems it runs for a long time and keep eating bandwidth and cpu. Things like these keep making me loosing faith on Ubuntu. I remember the name Ubuntu borrowed its root from African language, but it seems their system are not so friendly to the users (including students, educators) from African countries.

user3939382 4y ago
I've been away from Linux for a while and was looking at Ubuntu the other day. Huge download size, huge minimum resources, background processes phoning home constantly. IMHO this is what Linux is there to fight. The system should be reasonably knowable and controllable by the user, especially a technical one like myself. If I want a byzantine labyrinth of processes phoning home and eating up all my system resources I'll use macOS or Windows.
JonChesterfield 4y ago
Unattended upgrades holds a lock that apt uses while downloading. Shouldn't, does. So a really common experience is turn on a machine, apt install foo, blocked by the updates, anger. Helps a little that apt now tells me what is holding the lock, but it's always unattended upgrades. Which somehow has come back to life after attempts to disable it.
rightbyte 4y ago
This is the problem with user hostile systems that think they know better than the user. You have no control and can't get a stable system. And since things change automatically you have no clue what made stuff broken. I can vision the condescending and smug guy on Canonical forcing auto updates (remote code execution) by default as some "security" measure.

xkcd-sucks 4y ago

Shortly after the push to manage everything through snap, I set up ubuntu server and installed docker, to support a client facing demo involving a few containers. A few hours before the demo snap updated docker to a version that was totally broken and there was much embarrassment. That day I gave up on Ubuntu completely and never looked back.

avg_dev 4y ago
what do you use now?
- xkcd-sucks 4y ago
  Mostly....... PopOS with KDE, lol, the 3rd party driver installation convenience is really nice. Or plain old debian for server stuff.
- jetbalsa 4y ago
  Debian, Debian all the way
remram 4y ago
On a friend's machine, Ubuntu had somehow managed to install both the APT docker and the Snap docker. This caused the entire disk to fill with log messages from the snap docker trying and failing to start, since another docker was already running. Removing snapd is the first thing I do on any Ubuntu machine now, whether mine or my friends'. This now requires adding a PPA for Firefox since 22.04 but otherwise I have never had to deal with snap again.

jrm4 4y ago

I don't like Ubuntu anymore, but not because of "how it operates." More because of "how it operates, without being forthcoming about what its new purpose is, which is not 'everybody's Linux.'" You're trying to be a tool to support big corporate IT. That is absolutely fine, good even. Getting more Linux in that space, under Ubuntu's name, seems pretty cool. But you're no longer "the people's choice" when you behave that way. They're putting in big grown up restrictions and ideas and methods of doing things, and they just need to be honest about that.

boppo1 4y ago

I use Xubuntu and snap just gets in my way. With Apt everything is transparent and 'just werks' or at least indicates what to fix. Snap has been the opposite in my experience and especially seems to make program interop more difficult. It seems like Canonical said "Apple and Microsoft have (painful) app stores that cater to the non-technical, we need one too!"

noasaservice 4y ago

Reminder for you Ubuntu(and XUbuntu and KUbuntu) people: Snap is closed source garbage ware, with MS Windows forced updating and the terribleness of being 10x slower.... So here's how to "Snap-Off" your system https://haydenjames.io/remove-snap-ubuntu-22-04-lts/ https://haydenjames.io/remove-snap-ubuntu-22-04-lts/

INeedMoreRam 4y ago
I desnapped my Kubuntu machine successfully per those instructions.

gjsman-1000 4y ago

I used Ubuntu since 11.04. I abandoned it for Fedora. Everything about Ubuntu now is seemingly defined by a spirit of defiance from Fedora. They borrow PipeWire and SystemD, but uglify GNOME, replace Flatpak with Snap, and use *.deb instead of *.rpm. Otherwise it feels mostly the same. I looked at the Fedora ecosystem and... it's basically just like Ubuntu's point versions, and instead of an LTS every 2 years, you get one every 5 years and it's called Rocky Linux / AlmaLinux. Why pick Ubuntu instead of (basically) upstream? I'll pick the same thing with prettier GNOME and Flatpak instead of the weird mystery lump Ubuntu is now.

macksd 4y ago
>> Why pick Ubuntu instead of (basically) upstream? "Upstream" for Ubuntu is more like Debian, which is the basis for MANY distros (much like Red Hat - founded around the same time as Debian - and the .rpm ecosystem is a significant core component of many systems including current versions of SuSE, etc.). Ubuntu has traditionally been a slightly more newbie-friendly / commercial-friendly version of Debian. I don't think many of the changes you're describing were really trying to defy Fedora, especially not the choice to use .deb over .rpm. That said, I did use Fedora for a while when Ubuntu started messing with Gnome a lot and I found it very refreshing, easy and reliable. It's a great distro, but the relationship between the two is absolutely not "upstream" and "downstream".
- pxc 4y ago
  What they mean is not 'upstream' with respect to distro tooling, but Fedora's closer relationship to the upstream components of the stack desktop stack (GNOME, PipeWire, SystemD, etc.), which are often entirely or in part maintained by Fedora contributors or Red Hat employees, etc. The 'defiance' they're talking about are the projects that Canonical has developed, often in secret, which are or were essentially alternatives/competitors to the components of the Linux free desktop stack which have been developed in the open, often at Red Hat and developed on Fedora. The cases that come to mind are: - Unity vs. GNOME 3 - Upstart vs. Systemd - Mir vs. Wayland - Snap vs. Flatpak The Canonical entries all appear as sort of NIH latecomers, whereas their competitors have generally been developed in an upstream-first, 'release early' kind of way. In each case, the tech opposite Canonical's has been shipped on Fedora, before eventually becoming the default in Ubuntu anyway. (Snap has yet to go.)

mkasberg 4y ago

The way Snap updates packages caused some problems with Firefox on recent versions of Ubuntu - I wrote a blog about it: https://www.mikekasberg.com/blog/2022/03/21/how-to-fix-firefox-crashes-on-ubuntu-21-10.html https://www.mikekasberg.com/blog/2022/03/21/how-to-fix-firef... Perhaps this update mechanism was part of the solution to some of those problems...

edgyquant 4y ago

Yet another sketchy and unprofitable company that has been subsidized so that it can act as the intermediary for human (teenage really) discussion.

83 4y ago
Ubuntu Snap (package management). Not Snapchat
- smallerfish 4y ago
  I had "Ubuntu" in the title of my HN submission originally for this reason, but HN admins changed it (I guess to line it up with the blog post).

jgneff 4y ago

You can now completely disable automatic updates of Snap packages. [1] [1] https://snapcraft.io/blog/hold-your-horses-i-mean-snaps-new-feature-lets-you-stop-snap-updates-for-as-long-as-you-need https://snapcraft.io/blog/hold-your-horses-i-mean-snaps-new-...

jacquesm 4y ago
Give this man a medal. Thank you. To update to this version use: snap refresh --channel=edge snapd snap refresh --hold to get rid of automatic updates.
- smallerfish 4y ago
  Yeah I mention this towards the end of my rant (in the article) but it's a) not available yet and b) not clear whether it'll actually notify you when there are updates to be made. I'm guessing it expects you to unhold at some point to get "refreshes".
  - jacquesm 4y ago
    I'm fine with that. Nothing drives me more mad than to be in the middle of an interview taking notes and then suddenly land in an endless loop of being forced to restart my browser. It's not like some of us don't have work to do while we're in the browser and the utter disrespect by the designers of this crap to the detriment of their users is baffling. This is one thing where commercial software has something of an edge over FOSS: you can't even threaten to withhold your $ if they misbehave. Power to the user.
AnIdiotOnTheNet 4y ago
Canonical watched this exact same shit play out with Microsoft and Windows yet decided to do the exact same thing. Mind boggling.
- curt15 4y ago
  Maybe they were trying to take a page from Microsoft's business model; take control away from users only to sell it back as an "enterprise edition" brand store.

danbmil99 4y ago

I struggled mightily with Firefox's tendency (on Ubuntu) to suddenly and (at least until recently without any notice) tell me "Firefox must restart right now, and will make a feeble/futile attempt to restore your pages". Terrible, terrible UX. Finally, I just uninstalled the snap version and downloaded/installed the .deb manually. So far so good -- I guess some day I might get hit with a security problem or some must-have feature, but at least I don't randomly have to restart Firefox every few weeks without prior notification.

Izkata 4y ago
Firefox has a built-in upgrade mechanism that doesn't rely on a package manager. I don't know if the .deb has it active, but it's worth checking, so if it is active you wouldn't have to worry about it.
0cf8612b2e1e 4y ago
I think you can point a direct line to that behavior and me installing PopOS. A web browser is my most used application and Ubuntu thinks they have the right to effectively crash it unexpectedly.
- ilyt 4y ago
  They took thing people hated in windows update and ported it to ubuntu lmao
asddubs 4y ago
you can use this ppa to keep it updated https://launchpad.net/~mozillateam/+archive/ubuntu/ppa https://launchpad.net/~mozillateam/+archive/ubuntu/ppa
- FullyFunctional 4y ago
  Thanks, but personally I don't want a workaround. I want a distribution that does the right thing. I have used Ubuntu for decades and use it everywhere. I hate to have to change, but as always, good things don't last.

signaru 4y ago

For those who are getting their Firefox messed up, the binary from the Mozilla site works just fine and is far more respectful. I'm using Mate 22.04 LTS. A few settings has to be done to disable updates behind your back, but at least these settings persist, unlike when I was using Snap or whatever it was I managed to install via apt (I think it still eventually reverted to Snap). There was also the issue that the Snap version disables some extensions (sure they are potentially dangerous, but that risk is for me to take). Now, I just manually update Firefox at convenient times via the Help -> About menu.

mxmlnkn 4y ago
That's also the solution I use. Especially because I have multi-rows set up in Firefox and each update breaks this. Plus, when installing the binaries manually, you can also apply some "hidden" settings by creating a distribution/policies.json file inside the firefox installation folder. This is what mine contains: { "policies": { "DisableAppUpdate": true, "DisableFeedbackCommands": true, "DisableFirefoxAccounts": true, "DisableFirefoxStudies": true, "DisablePocket": true, "DisableSetDesktopBackground": true, "DisableTelemetry": true, "NoDefaultBookmarks": true } } It's kinda sad how many settings you have to configure not only here in order to not be nagged constantly. It's like you are fighting against your tools.
- geekbird 4y ago
  That's why I hate Snap. In Linux, unlike Windows or Mac, I should not have to fight my tools in order to configure a system the way I want it. Yet Ubuntu makes me do it every goddamn time for anything on the desktop, between snap and their nasty "Unity" desktop.

sockaddr 4y ago

I was struggling with this annoyance recently and today decided to finally uninstall the snap. The “close now” is super annoying. I ran “sudo apt install firefox” and it installed a freaking snap! Today I learned that Ubuntu just decides to install snaps instead of the apt package. What the hell.

cybrexalpha 4y ago
I moved from Ubuntu to Debian because of snaps. I keep apt and the majority of my knowledge of how to run the system, but no snap.
dublinben 4y ago
You might prefer Pop! OS, which is based on Ubuntu, but uses flatpak instead of snaps.
- poszlem 4y ago
  Just to add a data point, I recently went back to Linux after spending years in the MacOS world. Installed Ubuntu out of habit, got the exact same thing happen to me (removed snap, installed firefox through apt, got snap back) and went to Pop OS. Could not be happier with the overall system and still very much disgusted by what Ubuntu decided to do.
  - alpaca128 4y ago
    I've had bad luck with PopOS, but it defniitely has one of the most reasonable and user friendly configurations out of the box.
  - brainchild-adam 4y ago
    Welcome back to Linux! What made you switch from macOS?
    - petre 4y ago
      Not OP but the desktop is super annoying for advanced users with too much mouse usage and things that are super easy in Linux to install from packages require Macports or brew pulling out N squared dependencies.

alkonaut 4y ago

Why would Snap kill the running application when the update is pushed? Any system for self-updating applications needs to install the new version side by side with the existing one anyway. So what’s the reason for terminating the running instance?

userbinator 4y ago
They've adopted Microsoft's approach of trying to hold users on a leash and beat them into submission.
- alkonaut 4y ago
  Microsoft’s self updating desktop apps (Teams etc) switch silently on restart. Unsure about their store apps but I imagine it’s the same thing. With older windows desktop apps which install to privileged locations like %programfiles% it’s more complex. But that’s the point: snap is a new system. It should be well designed because of it, and be on par with “modern” install systems. It feels strange if they restart for no reason. And it feels equally strange if they have a design that requires it.

compsciphd 4y ago

I'll just reference my rant from a month and a half ago - https://news.ycombinator.com/item?id=33275206#33277156 https://news.ycombinator.com/item?id=33275206#33277156

azornathogron 4y ago

The article mentions Snap, AppImage and FlatPak, but there is also a much older system called 0install (zero install) that was started in 2003 or so [1]. I wonder why that never took off. [1] https://zero-install.sourceforge.net/roadmap.html https://zero-install.sourceforge.net/roadmap.html (note this is the old website; the new website is https://0install.net https://0install.net - looks like it's still getting releases in October this year)

Animats 4y ago

The restart notification system is so lame that I get notifications that the snap daemon needs to update itself and I should close the snap daemon. Which is not something I opened. What am I supposed to do, kill the process?

xg15 4y ago

Apparently forcing updates is sort of the core of Snap's philosophy. To the point that they rather added a whole host of config options that lets you specify various "work periods", "postponements" and other temporarily exceptions than just give you the ability not to update. See the discussion here: https://forum.snapcraft.io/t/disabling-automatic-refresh-for-snap-from-store/707 https://forum.snapcraft.io/t/disabling-automatic-refresh-for... Edit: ...or not anymore: https://news.ycombinator.com/item?id=33836216 https://news.ycombinator.com/item?id=33836216

Taniwha 4y ago
Can I tell it what I consider my "home directory" is because snaps seem to limit me to what some bozo at canonical thinks is my home directory (rather the multiple volumes and symbolic links I've used for a couple of decades now)

dessant 4y ago

It's also alarming that GNOME extensions are updated in the background without user interaction, and the feature cannot be disabled. These extensions are not sandboxed, can run arbitrary commands, and have access to the entire system. Extensions are practically a backdoor for the entire GNOME user base that can be accessed by compromising the update server. https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2514 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2514

forgotpwd16 4y ago
I really hope the solution won't be GNOME purging extensions alltogether.
Spivak 4y ago
> access to the entire system It is bad but it’s not that bad, they are still running as your unprivileged user.
- cprecioso 4y ago
  Relevant xkcd https://xkcd.com/1200/ https://xkcd.com/1200/

kkfx 4y ago

Snaps, Flatpacks etc are tools needed to push commercial CRAP in FLOSS systems. Period. The present "sorry state of packaging", largely due to the sorry state of storage (filesystems) stuck in the '80s in the bad sense of being simply largely obsolete for today's needs can be partially surpassed by NixOS/Guix model, witch is a FLOSS packaging model. Snaps and co on contrary are needed to push distro to irrelevance and allow closed source crapware, mostly filled up with outdated dependencies and horrendous hacks to speed up delivery times by some underpaid and under-competent developer, still fail to prove ANY other realistic purpose. Really: try to honestly weight their ideas and tell different conclusions if you can find something else. At first they say "we do compartmentalize anything for safety", than "ah, yes, we can't really isolate stuff because if you want just to open a damn pdf downloaded from a modern WebVM improperly named browser for legacy reasons you can't, so we start punching holes here and there" and thereafter even the effectiveness of formal isolation was depicted as not really safe. Then/aside another justification came up: pushing fresh software to distros who do not have manpower for quick enough maintainers. The actual snap store prove the contrary: most snaps are outdated and full of outdated deps, with potentially unpatched security vulnerabilities, of course. Oh, of course they can't package anything than apps, since kernel/userland can't be in a snap, so they need anyway a secondary packaging systems.

nanna 4y ago

Installed Ubuntu on a friend's laptop last weekend. Today her Firefox wouldn't open because snap was reporting it couldn't update it because it was already running. She restarted computer, same problem. She asked if she can "delete" snap. I'm a debian person, so not sure. Can she?

matkoniecz 4y ago
Why not install Debian on her laptop?
- nanna 4y ago
  I was running out of time and the Debian installer needed non-free driver packages to be added. If I had more time I would've gone that route.
usr1106 4y ago
snap can be uninstalled. But then she needs Firefox from another source, there is no official .deb package any more. There is also the risk that some update or package installation will pull in snap again. Doable for a technical user who only runs apt from command line and always reads the dependencies before answering yes. Not suitable for non-technical users.

tgsovlerkhgsel 4y ago

What's the minimum effort way (i.e. without switching to another distro) to a) receive timely updates for Firefox b) without this bullshit? Sure, I can kill firefox, run the updater manually, then restart it, every time I see this popup, but that's pretty tiring.

sph 4y ago
Install Firefox from Flatpak. It comes straight from Mozilla, and it gets updates immediately.
spiznnx 4y ago
Go to firefox.com, download the tar.bz2, extract to /opt/firefox, and give yourself recursive ownership. Firefox will update itself.

crtasm 4y ago

I had been wondering about this new notification warning there's 12 days left to close snap-store. I don't have snap-store running!