I can confirm that I've seen this on systems other than Ubuntu. Probably
needs further investigation.
** Changed in: snapd
Status: New => Triaged
** Changed in: snapd
Importance: Undecided => Medium
** Changed in: snapd (Ubuntu)
Status: New => Incomplete
** Changed in: snapd (U
Today this happened again. I installed a bunch of updates with update-
manager, was prompted to reboot, checked with 'snap refresh --list' to
see if there were any snap updates pending (there weren't), and let
update-manager do the reboot.
snapd took 1m30s to shut down.
lapkr. 11 09:08:29 blyna
It would be nice if snapd would log something about what it's doing to
the journal.
I did run a `snap refresh --list` before rebooting and I saw that a
chromium update was being delayed since chromium was running. I closed
chromium a few seconds before initiating the reboot. Perhaps snapd
thought
I wonder what is causing that activity:
spal. 28 11:03:26 blynas snapd[1013]: daemon.go:586: WARNING: cannot
gracefully shut down in-flight snapd API activity within: 25s
This is why we are timing out on shutdown.
** Also affects: snapd
Importance: Undecided
Status: New
--
You recei
