Thank you for the excellent suggestions. However none of them address the issue that Canonical will not update the snap for an application that is actually running. As I have said elsewhere the ONLY time I am not running Firefox is when I reboot to apply other maintenance. When Canonical asks me to reboot to apply outstanding maintenance, how am I supposed to read their minds and know that this does not include snaps?
I, too, would like to know the answer to this question which has been bugging me for a while now. It took me some time in the beginning (of snaps) for me to realize that snaps were not being updated after a reboot. Mutter mutter! So now, after every reboot and before I login to the GUI I have to manually switch to another tty and run sudo snap refresh, then close it and got back to the GUI and login as usual which then causes all the things I had open to start back up again. This is pretty daft IMHO and I hope it is resolved soon. Cheers Pete
Originally Posted by grahammechanical The GUI utility Software Updater should run apt update; apt upgrade; apt autoremove and snap refresh. Regards It does for my updates.
Cheers, The Linux Command Line at https://linuxcommand.org/
I solved this issue by instructing Firefox to save my open windows when I close. This means I can safely close Firefox any time I know I am going to be away from my system for a period of time, for example when I go to bed. This means that snap can apply the updates, and they are available any time I start Firefox.
Please mark this thread as SOLVED, using the Thread Tools button. This helps the community save time. Also, thanks for posting what you decided to do. There are ramifications in allowing Firefox to save session data between restarts. To me, I want most cookies to all be flushed and at restart is a reasonable timeframe for that. I don't use the snap version of firefox for a number of reasons, but having all cookies cleaned out at program close time is a good middle-ground for my privacy desires.
Today I rebooted Ubuntu to apply outstanding changes that cannot be implemented without a reboot. The updater reassured me that all outstanding changes had been applied but when after the reboot I did: sudo snap refresh chromium 128.0.6613.137 from Canonical✓ refreshed core20 20240705 from Canonical✓ refreshed firefox 130.0.1-1 from Mozilla✓ refreshed thunderbird 128.2.1esr-2 from Canonical✓ refreshed Why were these critical components, most of which as you can see are distributed by Canonical, not updated as part of the update?
Originally Posted by 7-webmaster Why were these critical components, most of which as you can see are distributed by Canonical, not updated as part of the update? It is arguable whether or not that software was truly "critical." Those upgrades were not included simply because the "update" (Upade Manager application), with some exceptions, refers only to deb packages. The truly critical components of your system (except Ubuntu Core systems) are all deb packages. Snap packages don't need synchronized updates. Snap updates happen more frequently than deb updates and mostly without any notification. Snap updates are not stratfied like deb updates (main, updates, security, universe, multiverse, etc). There is generally no need to synchronize snap updates with deb updates.
Last edited by ian-weisser; September 18th, 2024 at 03:39 AM.
View Tag Cloud
Ubuntu Forums Code of Conduct