I’ve got a similar problem as described in this thread, but didn’t have the same issue with the ‘state.json’ file which was not corrupted (I tried removing it but it just recreated as soon as a snap command was run - can open it with sudo and have put slightly redacted contents below) and am now at a loss. Hoping someone here can spot what the problem might be!
I’m running Solus 4.0 with snap version 2.39.3-48 installed from Solus’ software center.
trenchanter@solus ~ $ snap find error: cannot list snaps: cannot communicate with server: Get http://localhost/v2/find?scope=wide§ion=featured: dial unix /run/snapd.socket: connect: connection refused
systemctl status snapd.service
snapd.service - Snappy daemon Loaded: loaded (/usr/lib/systemd/system/snapd.service; disabled; vendor pres> Active: failed (Result: exit-code) since Tue 2019-12-31 10:33:20 NZDT; 25min> Process: 3521 ExecStart=/usr/lib64/snapd/snapd (code=exited, status=1/FAILURE) Main PID: 3521 (code=exited, status=1/FAILURE)
sudo SNAPD_DEBUG=1 /usr/lib/snapd/snapd
AppArmor status: apparmor is enabled and all features are available 2019/12/31 11:13:47.018042 cmd_linux.go:70: DEBUG: re-exec not supported on distro "solus" yet 2019/12/31 11:13:47.022514 backend.go:115: snapd enabled NFS support, additional implicit network permissions granted cannot run daemon: cannot reload snap-confine apparmor profile: cannot load apparmor profiles: exit status 2 apparmor_parser output: File /etc/apparmor.d/usr.lib.snapd.snap-confine not found, skipping...
journalctl -u snapd --no-pager
-- No entries --
Output from: sudo journalctl -xe (< I’ve put this in pastebin)