Don't know if I am missing the point, but why not at your convenience
just do a:
sudo snap refresh to update any installed snap packages
or
sudo snap refresh /package-name/ to update a specific snap package
//
Aidan
On 26/04/2020 14:07, Ralph Corderoy wrote:
Hi Terry,
terry@OptiPlex:~$ snap refresh --time
timer: 00:00~24:00/4
last: today at 13:22 BST
next: today at 22:08 BST
That says it all really. We are likely to be eating lunch (or washing
up) at 13:22 and in bed / watching TV at 22:08.
Yes, I think it's a good idea to ensure the laptop is off and cannot
refresh tonight at 10 p.m.
The trouble is that since that is the default, most people would get
caught by this unless they run their machines all day.
Which they know, as I've already said, so I'd be surprised if there's no
mechanism to cope. When the laptop gets turned on tomorrow, it will be
interesting to see what ‘snap refresh --time’ then plans to do.
I'm wondering if an element of randomisation of the next +6 hour time,
say by ±2 hours, is causing your symptoms. The gap you show above is a
lot more than the ‘/4’ suggests.
$ units '22hour+8min - 13hour-22min' time
8 hr + 46 min
If the laptop is only ever on for 30 minutes at a time then the attempt
to avoid doing lots of timely things soon after power on might result in
few of them running time after time?
--
Next meeting: Online, Jitsi, Tuesday, 2020-05-05 20:00
Check to whom you are replying
Meetings, mailing list, IRC, ... http://dorset.lug.org.uk
New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
