Public bug reported:
Hi,
I may have missed something somewhere, but I recently came across a
problem with our laptop. This machine is currently running Kubuntu
19.10 but it emerged that the version of Chromium installed dated back
to Dec 2019. On my desktop machine (also running Kubuntu 19.10),
Chromium was at the latest version. Having consulted the docs I ran a
manual refresh of Chromium and the latest version was installed.
This begs the question; why were able to use the machine for nearly five
months without snap refreshing Chromium?
After further research I suspect this is due to the way in which snaps
are automatically refreshed; by default this is four times a day between
midnight and midnight, eg every 6 hours. (There seems to be some
randomisation introduced because running 'snap refresh --timer' does not
return times of 0000, 0600, 1200 or 1800.)
My suspicion is that this has come about because our laptop rarely runs
for six hours at a time; typically it is switched on, used for an hour
or two (sometimes much less) and then shut down again. The problem that
I see with this is that in these days of people owning multiple devices
this use-case is probably quite common.
I have seen in the docs that I can change the refresh cycle to be more
aligned to the times that we use the machine, but before they can do
that, people will need to realise that they need to. I only found this
out by accident. Not everyone who runs Linux is a software developer or
system administrator (I'm not, I'm a retired systems engineer from the
test industry), so are unlikely to read the docs for snapd.
Can I suggest that snapd runs an automatic refresh within 30 minutes of
boot up, to try to prevent this problem?
** Affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: New
** Tags: refresh snap
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875340
Title:
snap refresh schedule allows laptops to miss updates
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1875340/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
