I run Xubuntu on my RockPi and snap is already reinstalled in Xubuntu
rock@linaro-alip:~$ sudo snap install hello-world
Fehler: system does not fully support snapd: cannot mount squashfs image using “squashfs”: mount:
/tmp/sanity-mountpoint-503847617: wrong fs type, bad option, bad superblock on /dev/loop0,
missing codepage or helper program, or other error.
I am not a friend of Snap and therefore have no experience with it. From the feeling, I assume that Snap is usually installed differently, it is installed somehow during your installation, but some dependencies are not fulfilled. This can happen if you go down untested paths. I would completely uninstall Snap if I were you. And reinstall it afterwards. With a little luck the missing dependencies will be detected and considered, so missing inf files and scripts will be created and one or the other package will be installed.
If you use ubuntu then..Maybe, just maybe, there is one special package missing which have connection to mount (i had problem like this, but now with snap), try
– Logs begin at Sun 2018-01-28 15:58:17 UTC, end at Sun 2019-03-03 07:40:36 UTC. –
Feb 26 14:12:03 linaro-alip systemd[1]: Starting Snappy daemon…
Feb 26 14:12:03 linaro-alip snapd[23838]: AppArmor status: apparmor not enabled
Feb 26 14:12:03 linaro-alip snapd[23838]: helpers.go:145: error trying to compare the snap system key: system-key missing on disk
Feb 26 14:12:03 linaro-alip snapd[23838]: daemon.go:379: started snapd/2.37.1.1+18.04 (series 16; classic; devmode) ubuntu/18.04 (arm64) linux/4.4.154-59-rockchip-g5e7
Feb 26 14:12:03 linaro-alip snapd[23838]: main.go:123: system does not fully support snapd: cannot mount squashfs image using “squashfs”: mount: /tmp/sanity-mountpoint
Feb 26 14:12:03 linaro-alip systemd[1]: Started Snappy daemon.
Feb 26 14:12:08 linaro-alip snapd[23838]: daemon.go:611: gracefully waiting for running hooks
Feb 26 14:12:08 linaro-alip snapd[23838]: daemon.go:613: done waiting for running hooks
Feb 26 14:12:08 linaro-alip snapd[23838]: daemon stop requested to wait for socket activation
– Reboot –
Feb 26 14:16:27 localhost.localdomain systemd[1]: Starting Snappy daemon…
Feb 26 14:16:27 localhost.localdomain snapd[410]: AppArmor status: apparmor not enabled
Feb 26 14:16:27 localhost.localdomain snapd[410]: daemon.go:379: started snapd/2.37.1.1+18.04 (series 16; classic; devmode) ubuntu/18.04 (arm64) linux/4.4.154-59-rockc
Feb 26 14:16:27 localhost.localdomain snapd[410]: main.go:123: system does not fully support snapd: cannot mount squashfs image using “squashfs”: mount: /tmp/sanity-mo
Feb 26 14:16:27 localhost.localdomain systemd[1]: Started Snappy daemon.
Feb 26 14:16:32 localhost.localdomain snapd[410]: daemon.go:611: gracefully waiting for running hooks
Feb 26 14:16:32 localhost.localdomain snapd[410]: daemon.go:613: done waiting for running hooks
Feb 26 14:16:32 localhost.localdomain snapd[410]: daemon stop requested to wait for socket activation
Feb 26 14:21:16 linaro-alip systemd[1]: Starting Snappy daemon…
Feb 26 14:21:16 linaro-alip snapd[1654]: AppArmor status: apparmor not enabled
Feb 26 14:21:16 linaro-alip snapd[1654]: daemon.go:379: started snapd/2.37.1.1+18.04 (series 16; classic; devmode) ubuntu/18.04 (arm64) linux/4.4.154-59-rockchip-g5e70
Feb 26 14:21:16 linaro-alip snapd[1654]: main.go:123: system does not fully support snapd: cannot mount squashfs image using “squashfs”: mount: /tmp/sanity-mountpoint-
lines 1-23
sudo apt-get install squashfs-tools
[sudo] password for rock:
Reading package lists… Done
Building dependency tree
Reading state information… Done
squashfs-tools is already the newest version (1:4.3-6ubuntu0.18.04.1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
rock@linaro-alip:~$
how can i find out what on the system is not supported?