Cannot Install snaps on Manjaro linux


#1

Hello Guys!

I was trying to install spotify on manjaro linux yesterday, but, when i typed the command into the terminal, I got this error:

I tried to install other snaps such as bitwarden and firefox and kept getting the same error. Not sure if this is right place to ask for help or how to proceed from here.

Thanks for your help guys!


#2

Can you upload snapd logs? Specifically journalctl -u snapd


#3

Hello @mborzecki

Here are the logs:

Blockquote
– Reboot –
ene 22 17:45:25 MJ-LINUX systemd[1]: Starting Snappy daemon…
ene 22 17:45:29 MJ-LINUX snapd[522]: AppArmor status: apparmor not enabled
ene 22 17:45:29 MJ-LINUX snapd[522]: daemon.go:381: started snapd/2.36.2-1.0 (series 16; classic; devmode) manjaro/ (amd64) linux/4.19>
ene 22 17:45:29 MJ-LINUX snapd[522]: main.go:123: system does not fully support snapd: cannot mount squashfs image using “squashfs”: m>
ene 22 17:45:29 MJ-LINUX systemd[1]: Started Snappy daemon.
ene 22 17:45:31 MJ-LINUX snapd[522]: stateengine.go:102: state ensure error: Get https://api.snapcraft.io/api/v1/snaps/sections: dial >
ene 22 17:45:34 MJ-LINUX snapd[522]: daemon.go:613: gracefully waiting for running hooks
ene 22 17:45:34 MJ-LINUX snapd[522]: daemon.go:615: done waiting for running hooks
ene 22 17:45:34 MJ-LINUX snapd[522]: daemon stop requested to wait for socket activation
ene 22 17:50:24 MJ-LINUX systemd[1]: Starting Snappy daemon…
ene 22 17:50:24 MJ-LINUX snapd[1750]: AppArmor status: apparmor not enabled
ene 22 17:50:24 MJ-LINUX snapd[1750]: daemon.go:381: started snapd/2.36.2-1.0 (series 16; classic; devmode) manjaro/ (amd64) linux/4.1>
ene 22 17:50:24 MJ-LINUX snapd[1750]: main.go:123: system does not fully support snapd: cannot mount squashfs image using “squashfs”: >
ene 22 17:50:24 MJ-LINUX systemd[1]: Started Snappy daemon.
ene 22 17:50:39 MJ-LINUX snapd[1750]: daemon.go:613: gracefully waiting for running hooks
ene 22 17:50:39 MJ-LINUX snapd[1750]: daemon.go:615: done waiting for running hooks
ene 22 17:50:39 MJ-LINUX snapd[1750]: daemon stop requested to wait for socket activation
ene 22 17:55:15 MJ-LINUX systemd[1]: Starting Snappy daemon…
ene 22 17:55:15 MJ-LINUX snapd[2136]: AppArmor status: apparmor not enabled
ene 22 17:55:15 MJ-LINUX snapd[2136]: daemon.go:381: started snapd/2.36.2-1.0 (series 16; classic; devmode) manjaro/ (amd64) linux/4.1>
ene 22 17:55:15 MJ-LINUX snapd[2136]: main.go:123: system does not fully support snapd: cannot mount squashfs image using “squashfs”: >
ene 22 17:55:15 MJ-LINUX systemd[1]: Started Snappy daemon.
ene 22 17:55:20 MJ-LINUX snapd[2136]: daemon.go:613: gracefully waiting for running hooks
ene 22 17:55:20 MJ-LINUX snapd[2136]: daemon.go:615: done waiting for running hooks
ene 22 17:55:20 MJ-LINUX snapd[2136]: daemon stop requested to wait for socket activation
ene 22 18:21:27 MJ-LINUX systemd[1]: Starting Snappy daemon…
ene 22 18:21:27 MJ-LINUX snapd[4443]: AppArmor status: apparmor not enabled
ene 22 18:21:27 MJ-LINUX snapd[4443]: daemon.go:381: started snapd/2.36.2-1.0 (series 16; classic; devmode) manjaro/ (amd64) linux/4.1>
ene 22 18:21:27 MJ-LINUX snapd[4443]: main.go:123: system does not fully support snapd: cannot mount squashfs image using “squashfs”: >
ene 22 18:21:27 MJ-LINUX systemd[1]: Started Snappy daemon.
ene 22 18:21:42 MJ-LINUX snapd[4443]: daemon.go:613: gracefully waiting for running hooks
ene 22 18:21:42 MJ-LINUX snapd[4443]: daemon.go:615: done waiting for running hooks
ene 22 18:21:42 MJ-LINUX snapd[4443]: daemon stop requested to wait for socket activation
ene 22 18:22:06 MJ-LINUX systemd[1]: Starting Snappy daemon…
ene 22 18:22:06 MJ-LINUX snapd[4512]: AppArmor status: apparmor not enabled
ene 22 18:22:06 MJ-LINUX snapd[4512]: daemon.go:381: started snapd/2.36.2-1.0 (series 16; classic; devmode) manjaro/ (amd64) linux/4.1>
ene 22 18:22:06 MJ-LINUX snapd[4512]: main.go:123: system does not fully support snapd: cannot mount squashfs image using “squashfs”: >
ene 22 18:22:06 MJ-LINUX systemd[1]: Started Snappy daemon.
ene 22 18:22:11 MJ-LINUX snapd[4512]: daemon.go:613: gracefully waiting for running hooks
ene 22 18:22:11 MJ-LINUX snapd[4512]: daemon.go:615: done waiting for running hooks
ene 22 18:22:11 MJ-LINUX snapd[4512]: daemon stop requested to wait for socket activation
– Reboot –
ene 22 18:32:22 MJ-LINUX systemd[1]: Starting Snappy daemon…
ene 22 18:32:27 MJ-LINUX snapd[531]: AppArmor status: apparmor not enabled
ene 22 18:32:27 MJ-LINUX snapd[531]: daemon.go:381: started snapd/2.36.2-1.0 (series 16; classic; devmode) manjaro/ (amd64) linux/4.19>
ene 22 18:32:28 MJ-LINUX snapd[531]: main.go:123: system does not fully support snapd: cannot mount squashfs image using “squashfs”: m>
ene 22 18:32:27 MJ-LINUX systemd[1]: Started Snappy daemon.
ene 22 18:32:29 MJ-LINUX snapd[531]: stateengine.go:102: state ensure error: Get https://api.snapcraft.io/api/v1/snaps/sections: dial >
ene 22 18:32:32 MJ-LINUX snapd[531]: daemon.go:613: gracefully waiting for running hooks
ene 22 18:32:32 MJ-LINUX snapd[531]: daemon.go:615: done waiting for running hooks
ene 22 19:09:46 MJ-LINUX snapd[3801]: daemon stop requested to wait for socket activation
ene 22 19:19:05 MJ-LINUX systemd[1]: Starting Snappy daemon…
ene 22 19:19:05 MJ-LINUX snapd[4492]: AppArmor status: apparmor not enabled
ene 22 19:19:05 MJ-LINUX snapd[4492]: daemon.go:381: started snapd/2.36.2-1.0 (series 16; classic; devmode) manjaro/ (amd64) linux/4.1>
ene 22 19:19:05 MJ-LINUX snapd[4492]: main.go:123: system does not fully support snapd: cannot mount squashfs image using “squashfs”: >
ene 22 19:19:05 MJ-LINUX systemd[1]: Started Snappy daemon.
ene 22 19:19:10 MJ-LINUX snapd[4492]: daemon.go:613: gracefully waiting for running hooks
ene 22 19:19:10 MJ-LINUX snapd[4492]: daemon.go:615: done waiting for running hooks
ene 22 19:19:10 MJ-LINUX snapd[4492]: daemon stop requested to wait for socket activation
ene 22 19:22:01 MJ-LINUX systemd[1]: Starting Snappy daemon…
ene 22 19:22:01 MJ-LINUX snapd[4822]: AppArmor status: apparmor not enabled
ene 22 19:22:01 MJ-LINUX snapd[4822]: daemon.go:381: started snapd/2.36.2-1.0 (series 16; classic; devmode) manjaro/ (amd64) linux/4.1>
ene 22 19:22:01 MJ-LINUX snapd[4822]: main.go:123: system does not fully support snapd: cannot mount squashfs image using “squashfs”: >
ene 22 19:22:01 MJ-LINUX systemd[1]: Started Snappy daemon.
ene 22 19:22:16 MJ-LINUX snapd[4822]: daemon.go:613: gracefully waiting for running hooks
ene 22 19:22:16 MJ-LINUX snapd[4822]: daemon.go:615: done waiting for running hooks
ene 22 19:22:16 MJ-LINUX snapd[4822]: daemon stop requested to wait for socket activation
– Reboot –
ene 23 04:16:27 MJ-LINUX systemd[1]: Starting Snappy daemon…
ene 23 04:16:31 MJ-LINUX snapd[518]: AppArmor status: apparmor not enabled
ene 23 04:16:31 MJ-LINUX snapd[518]: daemon.go:381: started snapd/2.36.2-1.0 (series 16; classic; devmode) manjaro/ (amd64) linux/4.19>
ene 23 04:16:32 MJ-LINUX snapd[518]: main.go:123: system does not fully support snapd: cannot mount squashfs image using “squashfs”: m>
ene 23 04:16:32 MJ-LINUX systemd[1]: Started Snappy daemon.
ene 23 04:16:33 MJ-LINUX snapd[518]: stateengine.go:102: state ensure error: Get https://api.snapcraft.io/api/v1/snaps/sections: dial >
ene 23 04:16:37 MJ-LINUX snapd[518]: daemon.go:613: gracefully waiting for running hooks
ene 23 04:16:37 MJ-LINUX snapd[518]: daemon.go:615: done waiting for running hooks
ene 23 04:16:37 MJ-LINUX snapd[518]: daemon stop requested to wait for socket activation

Blockquote


#4

Can you double check you are actually running the same kernel version as is installed?


#5

I’ve checked the kernel installed on snap and on my system and they are not the same, the kernel installed on the snaps system is:

[josh17@MJ-LINUX ~]$ snap version
snap 2.36.2-1.0
snapd 2.36.2-1.0
series 16
manjaro -
kernel 4.19.14-1-MANJARO

The kernel version on my system is:
image

Do they have to be the same version? If so, How do i go about to update the snap version?

Thanks for your help.


#6

What I meant is that you need to make sure that the kernel that is running is the same version as installed through your package manager. Eg. on my Arch box:

$ uname -r 
4.20.3-arch1-1-ARCH
$ pacman -Q linux
linux 4.20.3.arch1-1

AFAIK Manjaro has the same problem as Arch, there is just one kernel version installed at a time. If you upgraded your host and did not reboot to the new kernel, anything that loads modules on demand will fail in most non obvious ways.

Another alternative is that Manjaro kernel does not support squashfs, but I consider this highly unlikely.


#7

Thanks for the explanation.

Checking my system kernel installed is running the same version but, the issue persists

josh17@MJ-LINUX ~]$ uname -r
4.19.16-1-MANJARO
[josh17@MJ-LINUX ~]$ pacman -Q linux
linux419 4.19.16-1


#8

I’ll try to install it in a VM and see what’s going on.

Does the problem persist if you install snapd from AUR instead of Manjaro repositories?


#9

I Just installed the snapd package from the AUR and tried to install spotify from snapcraft but, the problem persists:

josh17@MJ-LINUX ~]$ sudo snap install spotify
[sudo] password for josh17:
error: system does not fully support snapd: cannot mount squashfs image using
“squashfs”: mount: /tmp/sanity-mountpoint-923455446: el montaje ha
fallado: Operación no permitida.

josh17@MJ-LINUX ~]$ snap version
snap 2.37.r194.g96fee42f2-1
snapd 2.37.r194.g96fee42f2-1
series 16
manjaro -
kernel 4.19.16-1-MANJARO


#10

I did a clean install of Manjaro in a VM, but could not reproduce your problem. I tried the package from community repo and the one from AUR. Both worked fine. Mounting a random squashfs image manually, works fine too.

Can you try this in a terminal?

$ mkdir /tmp/foo && echo bar > /tmp/foo/bar
$ mksquashfs /tmp/foo /tmp/foo.img -all-root
$ mkdir /tmp/foo-mount-point
$ sudo mount -t squashfs /tmp/foo.img /tmp/foo-mount-point

Does it fail on the mount step?


#11

Yes, It does.

At the end, it showed me an error. Here is all what the commands displayed:

[josh17@MJ-LINUX ~]$ mkdir /tmp/foo && echo bar > /tmp/foo/bar
[josh17@MJ-LINUX ~]$ mksquashfs /tmp/foo /tmp/foo.img -all-root
Parallel mksquashfs: Using 4 processors
Creating 4.0 filesystem on /tmp/foo.img, block size 131072.
[=====================================================|] 1/1 100%

Exportable Squashfs 4.0 filesystem, gzip compressed, data block size 131072
compressed data, compressed metadata, compressed fragments,
compressed xattrs, compressed ids
duplicates are removed
Filesystem size 0.22 Kbytes (0.00 Mbytes)
90.04% of uncompressed filesystem size (0.25 Kbytes)
Inode table size 41 bytes (0.04 Kbytes)
62.12% of uncompressed inode table size (66 bytes)
Directory table size 21 bytes (0.02 Kbytes)
84.00% of uncompressed directory table size (25 bytes)
Number of duplicate files found 0
Number of inodes 2
Number of files 1
Number of fragments 1
Number of symbolic links 0
Number of device nodes 0
Number of fifo nodes 0
Number of socket nodes 0
Number of directories 1
Number of ids (unique uids + gids) 1
Number of uids 1
root (0)
Number of gids 1
root (0)
[josh17@MJ-LINUX ~]$ mkdir /tmp/foo-mount-point
[josh17@MJ-LINUX ~]$ sudo mount -t squashfs /tmp/foo.img /tmp/foo-mount-point
mount: /tmp/foo-mount-point: el montaje ha fallado: Operación no permitida.


#12

At this point it’s clearly not snapd related. The problem is, mounting squashfs images in your host does not work for some reason. It does work for me in a Manjaro VM. I think you’re better off asking around Manjaro forums.


#13

No problem @mborzecki. Thank you for helping me and trying. I truly appreciate your efforts.

Hopefully with one of the updates that manajaro releases, this can be fixed.

Also, keep it up the good job with snaps. I really like the idea behind it. Let’s hope that in the future, there can be more apps.

Have a nice day!


#14

Hello @mborzecki!

I was able to fix the issue!!! Please take a look at what I did in the following link https://forum.manjaro.org/t/snapd-is-not-working-since-downgrade-to-systemd-239-6-2-2-advised-in-the-security-update-on-2019-01-19/73774

Thank you for your help with this. I’ll mark this as solved.

Hopefully this can help others with the same or similar issue.

Kind regards