5 ms·

If you ignore the notifications for two weeks, yes. But you even get a notification at least four hours before updating saying you have little time left. That

If you ignore the notifications for two weeks, yes. But you even get a notification at least four hours before updating saying you have little time left. That said, if you run `snap hold firefox`, it will wait indefinitely.

bauruine 4y ago
Not updating isn't a solution. What works for me is a systemd service that does a snap refresh on boot. At least I have some controll on when it updates.
- deleted 4y ago
  [deleted]
- bobmaxup 4y ago
  I know it is simple to do, but care to share the unit file?
  - bauruine 4y ago
    It's the most basic file possible but it does it's job. cat /etc/systemd/system/upgrade-system.service [Unit] After=network-online.target [Service] ExecStart=/bin/bash -c '/usr/bin/snap refresh && apt update && apt upgrade -y' [Install] WantedBy=default.target
magicalhippo 4y ago
The problem is that the dialog says to quit the application so snap can update, but snap doesn't do that. It checks a few times a day and bails if the application is running. It doesn't wait for the application to exit and then update, like the dialog indicates it would. Thus you quit the Firefox, wait a few minutes, assume it has been updated because why shouldn't it, and after two weeks it gets killed mid-session. Completely inexcusable UX...
- Zuiii 4y ago
  I've encountered this exact issue: It kept bugging me to close firefox so that I can update. I closed it. Then I relaunched it and the message popped up again. I repeated this process for a couple of days until I gave up, uninstalled snap, and installed flatpak. Issues like this are present in a lot of highly-opinionated software; they become utterly unusable when used in a way that deviates from the dev's ideal vision, or ways they plain just refuse to support. Configurability and transparency is almost always a good thing in software. It seems that some Devs will have to relearn this lesson the hard way.
  - josephcsible 4y ago
    For the record, the solution to this is to run "snap refresh" manually right after you exit Firefox.

bauruine 4y ago

Not updating isn't a solution. What works for me is a systemd service that does a snap refresh on boot. At least I have some controll on when it updates.

deleted 4y ago
[deleted]
bobmaxup 4y ago
I know it is simple to do, but care to share the unit file?
- bauruine 4y ago
  It's the most basic file possible but it does it's job. cat /etc/systemd/system/upgrade-system.service [Unit] After=network-online.target [Service] ExecStart=/bin/bash -c '/usr/bin/snap refresh && apt update && apt upgrade -y' [Install] WantedBy=default.target

magicalhippo 4y ago

The problem is that the dialog says to quit the application so snap can update, but snap doesn't do that. It checks a few times a day and bails if the application is running. It doesn't wait for the application to exit and then update, like the dialog indicates it would. Thus you quit the Firefox, wait a few minutes, assume it has been updated because why shouldn't it, and after two weeks it gets killed mid-session. Completely inexcusable UX...

Zuiii 4y ago
I've encountered this exact issue: It kept bugging me to close firefox so that I can update. I closed it. Then I relaunched it and the message popped up again. I repeated this process for a couple of days until I gave up, uninstalled snap, and installed flatpak. Issues like this are present in a lot of highly-opinionated software; they become utterly unusable when used in a way that deviates from the dev's ideal vision, or ways they plain just refuse to support. Configurability and transparency is almost always a good thing in software. It seems that some Devs will have to relearn this lesson the hard way.
- josephcsible 4y ago
  For the record, the solution to this is to run "snap refresh" manually right after you exit Firefox.