Mar 27 17:32:46 localhost.localdomain /usr/lib/snapd/snapd: snapmgr.go:306: DEBUG: snapmgr refresh randomness 3h59m2.770559101s Mar 27 17:32:46 localhost.localdomain systemd: Started Snappy daemon. Mar 27 17:32:46 localhost.localdomain systemd: rvice: Failed with result 'signal'. Mar 27 17:32:46 localhost.localdomain systemd: rvice: Unit entered failed state. Mar 27 17:32:46 localhost.localdomain systemd: Stopped Snappy daemon. I am having a hard time wrapping my head aroung this $ sudo journalctl -f -u snapd I appreciate you giving a hand out even on your vacation. try sudo snap refresh core and report back.

in another terminal do snap version, and pastebin what you see in journalctl.watch the snapd log: sudo journalctl -f -u snapd.restart snapd: sudo systemctl restart snapd.add SNAPD_DEBUG=1 to /etc/environment (for example, echo SNAPD_DEBUG=1 | sudo tee -a /etc/environment, or just use vi - nano might also be installed).I’d really like to help you figure this one out (so much, that I’m supposed to be on vacation right now, but here I am). It should print some variation of ‘not found’.

There also is no sane reason for snap refresh snapd to print “EOF”. There is no reason snap list nor snap version should delay in any way after printing their thing. The core snap is from the store, published almost exactly a year ago (T04:26z). The kernel and gadget you have are sideloaded, not from the store, so they’ll never refresh. The core snap you have is similarly ancient. First off, that image is very old: nearly a year old, in fact.

Skype error 1618 windows 10