I’m having trouble (often) updating chromium regularly.
guiverc@d960-ubu2:~/.config/hexchat$ snap refresh error: cannot perform the following tasks: - Run configure hook of "chromium" snap if present (run hook "configure": ----- /usr/share/fonts/X11: caching, new cache contents: 0 fonts, 5 dirs /usr/share/fonts/X11/100dpi: caching, new cache contents: 358 fonts, 0 dirs /usr/share/fonts/X11/Type1: caching, new cache contents: 8 fonts, 0 dirs /usr/share/fonts/X11/encodings: caching, new cache contents: 0 fonts, 1 dirs /usr/share/fonts/X11/encodings/large: caching, new cache contents: 0 fonts, 0 dirs <redacted> /usr/share/fonts/truetype/monoid: caching, new cache contents: 5 fonts, 0 dirs /usr/share/fonts/truetype/msttcorefonts: caching, new cache contents: 60 fonts, 0 dirs /usr/share/fonts/truetype/nanum: caching, new cache contents: 12 fonts, 0 dirs /usr/share/fonts/truetype/noto: <exceeded maximum runtime of 5m0s> -----)
I’ve seen the same from other user (eg. https://askubuntu.com/questions/1300249/updating-chromium-fails-times-out-as-snap-package) and maybe it’s just how we use our boxes
(I usually suspend boxes overnight; rebooting only when required, say every 10 days, though I often close
firefox before I suspend at night as extensions I use cause ram-leaks & this nullifies the leak/thrashing issue.
I’m on hirsute, and I update (
apt) my box 2-3 times per day, but only
snap refresh when I get sick of the nagging & count-down of days… quitting
chromium & trying
snap refresh… if this issue occurs a few times (
exceeded maximum runtime of), I just re-load chromium & return to ignoring the nagging).
Eventually I’ll succeed
guiverc@d960-ubu2:~/.config/hexchat$ snap refresh chromium 89.0.4389.82 from Canonical✓ refreshed
or I just be very patient on next reboot, letting it update before I start
chromium (most of what I do is in
I suspect it relates to my older box (2009 dell)
- dell [optiplex] 960 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350)
This issue doesn’t worry me, but I’m reporting.