Snap error: system does not fully support snapd: cannot mount squashfs image using "squashfs": -----

Ask Fedora
, , ,
1

Fedora 39 on Lenovo ideapad

Installed Snap via the instructions at connical’s snap site.

Snap install gives the following message:

error: system does not fully support snapd: cannot mount squashfs image using “squashfs”: -----
mount: /tmp/syscheck-mountpoint-4050560700: wrong fs type, bad option, bad superblock on
/dev/loop0, missing codepage or helper program, or other error.

   dmesg(1) may have more information after failed mount system call.

.
How do I get past this? …and install snaps

2

My system info:

Operating System: Fedora Linux 39
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.113.0
Qt Version: 5.15.12
Kernel Version: 6.6.13-200.fc39.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Pentium® CPU 6405U @ 2.40GHz
Memory: 3.6 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics
Manufacturer: LENOVO
Product Name: 81WA
System Version: IdeaPad 3 14IML05

3

Snap is not installed nor recommended with fedora, though it may be used. Packages that are installed from a 3rd party site often do not play well in fedora, either during install (with missing or improper dependencies) or when running. Squashfs is also not installed by default but must be user managed.

You should search here for other threads related to snap.
You should also be aware that a “snap” image takes up permanent storage on a partition and many instances of running out of space have been traced to using snap on fedora.

4

I was trying inatall the desktop Notion app. Should have been more cautious when I saw Flatpak as the default.

5

Do you have the squashfs-tools package installed?

Fedora should not have any problems mounting a squashfs file system. The Live images, for example, depends on it.

1 Like
6

Yes I do.

Package squashfs-tools-4.6.1-2.fc39.x86_64 is already installed.

7

Likewise:

Package “squashfs-tools-4.6.1-5.fc41.x86_64” is already installed.

…yet I continue to see the error:

RokeJulianLockhart@SNRW3Q:~$ snap install powershell
error: system does not fully support snapd: cannot mount squashfs image using "squashfs":
       ----- mount: /tmp/syscheck-mountpoint-218649608: wrong fs type, bad option, bad superblock
       on /dev/loop0, missing codepage or helper program, or other error.

       dmesg(1) may have more information after failed mount system call.

       -----

I have filed the undermentioned:

8

Do in you need squashfuse as well?

9

@grumpey, per the aforementioned Launchpad URI:

Neither attempting to install kernel-modules (kernel-modules-6.11.10-300.fc41.x86_64 is already installed) nor installing squashfuse-0:0.5.2-2.fc41.x86_64 (and its dependency, squashfuse-libs-0:0.5.2-2.fc41.x86_64) work.

Thanks, though.

1 Like
10

What does dmesg say?

For me, it says selinux: security_context_str_to_sid (system_u:object_r:snappy_snap_t:s0) failed with errno=-22.

I don’t understand selinux enough to understand what this error is trying to say, but when I disable selinux, I am able to install snaps.

Relabeling the filesystem does not help.

Likely relatedly, sudo semodule -i /usr/share/selinux/packages/snappy.pp.bz2 says:

Failed to resolve typeattributeset statement at /var/lib/selinux/targeted/tmp/modules/400/snappy/cil:223
Failed to resolve AST
semodule: Failed!

11

@sompom, I’ve used journalctl a few times, but not dmesg. What should I be searching for? The undermentioned doesn’t return anything useful:

  1. #!/usr/bin/env -S bash
sudo dmesg | grep -e 'selinux'

  2. RokeJulianLockhart@SNRW3Q:~$ sudo dmesg | grep -e 'selinux'
[    0.094927] LSM: initializing lsm=lockdown,capability,yama,selinux,bpf,landlock,ima,evm
[    0.878803] evm: security.selinux
[    8.412507] audit: type=1404 audit(1733082975.156:2): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295 enabled=1 old-enabled=1 lsm=selinux res=1
[    8.496131] audit: type=1403 audit(1733082975.240:3): auid=4294967295 ses=4294967295 lsm=selinux res=1
12

I’d usually do something like:

sudo dmesg -wH

In one terminal window, which follows the tail of the logs

and in another window, run whatever you want to see the dmesg logs from. In this case, whatever you are doing with snap.

1 Like
13

@sompom, that’s changed my life. Thank you. The logs are undermentioned:

[  +0.961620] loop0: detected capacity change from 0 to 8
[  +0.005043] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[  +0.000301] SELinux: security_context_str_to_sid (system_u:object_r:snappy_snap_t:s0) failed with errno=-22
14

This can be marked as the solution, I presume.