Last year on my mother's laptop, Windows completely stopped working and would not want to come out of recovery mode anymore.
I switched her over to #Ubuntu, which works just fine.
But twice now, she has run into this problem with #Snap, which results in both Firefox and Thunderbird refusing to start up (without any error dialog).
So I get called in because "Internet does not work".
This is a really catastrophic failure mode. I hope it gets more robust in the future.
https://forum.snapcraft.io/t/snapd-cannot-run-daemon-cannot-read-state-unexpected-eof/17908
Snapd: "cannot run daemon: cannot read state: unexpected EOF"
I have a Raspbian system with snapd, where the snapd daemon is no longer running. E.g. I get the following $ sudo snap refresh error: cannot communicate with server: Post http://localhost/v2/snaps: dial unix /run/snapd.socket: connect: connection refused In the snapd systemd log I see the following repeated over and over until the service fails: systemd[1]: Starting Snappy daemon... snapd[313]: AppArmor status: apparmor not enabled snapd[313]: AppArmor status: apparmor not enabled snapd[313]:...






