cela veut dire que le module n’est pas chargé donc cela ne peut pas marcher.
# modprobe squashfs
Pour cela il fuat que kernel-modules soit installé
dnf list kernel-module* --installed
Il faut que le kernel-modules installé corresponde au kernel en service

    fgland

    deviennenicolas@Nicolas:~$ sudo su
[sudo] Mot de passe de deviennenicolas : 
root@Nicolas:/home/deviennenicolas# modprobe squashfs
root@Nicolas:/home/deviennenicolas#  dnf list kernel-module* --installed
Aucun paquet correspondant à lister

      il faut installer
      # dnf install kernel-modules
      puis peut-être charge les modules, je ne sais si c’est fait à l’installation, le plus simple étant de redémarrer.

        fgland

        deviennenicolas@Nicolas:~$ sudo su
[sudo] Mot de passe de deviennenicolas : 
root@Nicolas:/home/deviennenicolas# dnf install kernel-modules
Updating and loading repositories:
 MEGAsync                                                                                                                                             ???% |   0.0   B/s |   0.0   B |  00m00s
>>> Status code: 404 for https://mega.nz/linux/repo/Fedora_41/repodata/repomd.xml (IP: 31.216.144.5) - https://mega.nz/linux/repo/Fedora_41/repodata/repomd.xml - repomd.xml
>>> Status code: 404 for https://mega.nz/linux/repo/Fedora_41/repodata/repomd.xml (IP: 31.216.144.5) - https://mega.nz/linux/repo/Fedora_41/repodata/repomd.xml - repomd.xml
>>> Status code: 404 for https://mega.nz/linux/repo/Fedora_41/repodata/repomd.xml (IP: 31.216.144.5) - https://mega.nz/linux/repo/Fedora_41/repodata/repomd.xml - repomd.xml
>>> Status code: 404 for https://mega.nz/linux/repo/Fedora_41/repodata/repomd.xml (IP: 31.216.144.5) - https://mega.nz/linux/repo/Fedora_41/repodata/repomd.xml - repomd.xml
>>> Erreur librepo : Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
 skype (unstable)                                                                                                                                     100% |  16.0 KiB/s |   1.5 KiB |  00m00s
>>> Status code: 503 for https://repo.skype.com/rpm/unstable/repodata/repomd.xml (IP: 104.115.88.163) - https://repo.skype.com/rpm/unstable/repodata/repomd.xml - repomd.xml
>>> Status code: 503 for https://repo.skype.com/rpm/unstable/repodata/repomd.xml (IP: 104.115.88.163) - https://repo.skype.com/rpm/unstable/repodata/repomd.xml - repomd.xml
>>> Status code: 503 for https://repo.skype.com/rpm/unstable/repodata/repomd.xml (IP: 104.115.88.163) - https://repo.skype.com/rpm/unstable/repodata/repomd.xml - repomd.xml
>>> Status code: 503 for https://repo.skype.com/rpm/unstable/repodata/repomd.xml (IP: 104.115.88.163) - https://repo.skype.com/rpm/unstable/repodata/repomd.xml - repomd.xml
>>> Erreur librepo : Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
Repositories loaded.
Le paquet "kernel-modules-6.11.2-300.fc41.x86_64" est déjà installé.
Le paquet "kernel-modules-6.11.3-300.fc41.x86_64" est déjà installé.
Le paquet "kernel-modules-6.11.4-300.fc41.x86_64" est déjà installé.

Nothing to do.
root@Nicolas:/home/deviennenicolas#

            Pour ma part:

            $ sudo systemctl status snapd.service
● snapd.service - Snap Daemon
     Loaded: loaded (/usr/lib/systemd/system/snapd.service; disabled; preset: disabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: active (running) since Fri 2024-10-18 09:18:47 CEST; 4h 37min ago
 Invocation: 5967424187eb41a7b721defa6ce1b56f
TriggeredBy: ● snapd.socket
   Main PID: 3536 (snapd)
      Tasks: 17 (limit: 18768)
     Memory: 32.7M (peak: 36.8M)
        CPU: 988ms
     CGroup: /system.slice/snapd.service
             └─3536 /usr/libexec/snapd/snapd

oct. 18 12:45:30 kapoue snapd[3536]: snapmgr.go:573: cannot read snap info of snap "bare" at revision 5: cannot find installed snap "bare" at revision 5: missing file /var/lib/snapd/snap/bare/5/meta/snap.yaml
oct. 18 12:45:30 kapoue snapd[3536]: snapmgr.go:573: cannot read snap info of snap "core18" at revision 2846: cannot find installed snap "core18" at revision 2846: missing file /var/lib/snapd/snap/core18/284>
oct. 18 12:45:30 kapoue snapd[3536]: snapmgr.go:573: cannot read snap info of snap "spotify" at revision 79: cannot find installed snap "spotify" at revision 79: missing file /var/lib/snapd/snap/spotify/79/m>
oct. 18 12:45:30 kapoue snapd[3536]: snapmgr.go:573: cannot read snap info of snap "gnome-3-38-2004" at revision 143: cannot find installed snap "gnome-3-38-2004" at revision 143: missing file /var/lib/snapd>
oct. 18 12:45:30 kapoue snapd[3536]: snapmgr.go:573: cannot read snap info of snap "core20" at revision 2379: cannot find installed snap "core20" at revision 2379: missing file /var/lib/snapd/snap/core20/237>
oct. 18 12:45:30 kapoue snapd[3536]: snapmgr.go:573: cannot read snap info of snap "gtk-common-themes" at revision 1535: cannot find installed snap "gtk-common-themes" at revision 1535: missing file /var/lib>
oct. 18 12:45:30 kapoue snapd[3536]: snapmgr.go:573: cannot read snap info of snap "snapd" at revision 21759: cannot find installed snap "snapd" at revision 21759: missing file /var/lib/snapd/snap/snapd/2175>
oct. 18 12:45:31 kapoue snapd[3536]: storehelpers.go:1019: cannot refresh: snap has no updates available: "bare", "core18", "core20", "gnome-3-28-1804", "gnome-3-38-2004", "gtk-common-themes", "skype", "snap>
oct. 18 12:45:31 kapoue snapd[3536]: autorefresh.go:628: Cannot prepare auto-refresh change: cannot find installed snap "core18" at revision 2846: missing file /var/lib/snapd/snap/core18/2846/meta/snap.yaml
oct. 18 12:45:31 kapoue snapd[3536]: stateengine.go:161: state ensure error: cannot find installed snap "core18" at revision 2846: missing file /var/lib/snapd/snap/core18/2846/meta/snap.yaml
            $ sudo lsmod | grep squashfs
squashfs               98304  0

            J’ai supprimé et réinstaller snapd dans le doute:

            $ sudo systemctl status snapd
● snapd.service - Snap Daemon
     Loaded: loaded (/usr/lib/systemd/system/snapd.service; disabled; preset: disabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: active (running) since Fri 2024-10-18 14:00:05 CEST; 6s ago
 Invocation: 80f835479d524ae9a7fc2cdac1a8bc35
TriggeredBy: ● snapd.socket
   Main PID: 76149 (snapd)
      Tasks: 17 (limit: 18768)
     Memory: 12.9M (peak: 14.5M)
        CPU: 84ms
     CGroup: /system.slice/snapd.service
             └─76149 /usr/libexec/snapd/snapd

oct. 18 14:00:05 kapoue snapd[76149]: -----
oct. 18 14:00:05 kapoue snapd[76149]: mount: /tmp/syscheck-mountpoint-341746599: wrong fs type, bad>
oct. 18 14:00:05 kapoue snapd[76149]:        dmesg(1) may have more information after failed mount >
oct. 18 14:00:05 kapoue snapd[76149]: -----
oct. 18 14:00:05 kapoue snapd[76149]: daemon.go:353: adjusting startup timeout by 30s (pessimistic >
oct. 18 14:00:05 kapoue snapd[76149]: backends.go:58: AppArmor status: apparmor not enabled
oct. 18 14:00:05 kapoue snapd[76149]: helpers.go:160: error trying to compare the snap system key: >
oct. 18 14:00:05 kapoue systemd[1]: Started snapd.service - Snap Daemon.
oct. 18 14:00:10 kapoue snapd[76149]: daemon.go:548: gracefully waiting for running hooks
oct. 18 14:00:10 kapoue snapd[76149]: daemon.go:550: done waiting for running hooks
            deviennenicolas@Nicolas:~$ sudo systemctl status snapd.service
[sudo] Mot de passe de deviennenicolas : 
○ snapd.service - Snap Daemon
     Loaded: loaded (/usr/lib/systemd/system/snapd.service; disabled; preset: d>
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: inactive (dead) since Fri 2024-10-18 13:18:32 CEST; 40min ago
   Duration: 8.024s
 Invocation: 8bc150525d944d80b33ad167f0463a76
TriggeredBy: ● snapd.socket
    Process: 56429 ExecStart=/usr/libexec/snapd/snapd (code=exited, status=42)
   Main PID: 56429 (code=exited, status=42)
   Mem peak: 11.2M
        CPU: 85ms

oct. 18 13:18:24 Nicolas snapd[56429]:        dmesg(1) may have more informatio>
oct. 18 13:18:24 Nicolas snapd[56429]: -----
oct. 18 13:18:24 Nicolas snapd[56429]: daemon.go:353: adjusting startup timeout>
oct. 18 13:18:24 Nicolas snapd[56429]: backends.go:58: AppArmor status: apparmo>
oct. 18 13:18:24 Nicolas systemd[1]: Started snapd.service - Snap Daemon.
oct. 18 13:18:29 Nicolas snapd[56429]: daemon.go:548: gracefully waiting for ru>
oct. 18 13:18:29 Nicolas snapd[56429]: daemon.go:550: done waiting for running >
oct. 18 13:18:32 Nicolas snapd[56429]: overlord.go:515: Released state lock file
oct. 18 13:18:32 Nicolas snapd[56429]: daemon stop requested to wait for socket>
oct. 18 13:18:32 Nicolas systemd[1]: snapd.service: Deactivated successfully.
lines 1-23/23 (END)...skipping...
○ snapd.service - Snap Daemon
     Loaded: loaded (/usr/lib/systemd/system/snapd.service; disabled; preset: disabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: inactive (dead) since Fri 2024-10-18 13:18:32 CEST; 40min ago
   Duration: 8.024s
 Invocation: 8bc150525d944d80b33ad167f0463a76
TriggeredBy: ● snapd.socket
    Process: 56429 ExecStart=/usr/libexec/snapd/snapd (code=exited, status=42)
   Main PID: 56429 (code=exited, status=42)
   Mem peak: 11.2M
        CPU: 85ms

oct. 18 13:18:24 Nicolas snapd[56429]:        dmesg(1) may have more information after failed mount system call.
oct. 18 13:18:24 Nicolas snapd[56429]: -----
oct. 18 13:18:24 Nicolas snapd[56429]: daemon.go:353: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)
oct. 18 13:18:24 Nicolas snapd[56429]: backends.go:58: AppArmor status: apparmor not enabled
oct. 18 13:18:24 Nicolas systemd[1]: Started snapd.service - Snap Daemon.
oct. 18 13:18:29 Nicolas snapd[56429]: daemon.go:548: gracefully waiting for running hooks
oct. 18 13:18:29 Nicolas snapd[56429]: daemon.go:550: done waiting for running hooks
oct. 18 13:18:32 Nicolas snapd[56429]: overlord.go:515: Released state lock file
oct. 18 13:18:32 Nicolas snapd[56429]: daemon stop requested to wait for socket activation
oct. 18 13:18:32 Nicolas systemd[1]: snapd.service: Deactivated successfully.
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
deviennenicolas@Nicolas:~$ sudo lsmod | grep squashfs
squashfs               98304  0

            @Hardelot , il y a du progrès ! je ne comprends pas pourquoi il n’a pas listé les kernel-mudules la première fois. Enfin squashfs est maintenant présent. Comme indiqué plusieurs fois il faut regarder dmesg(1) may have more information mais cela risque de me dépasser. J’espère qu’un pro prendra la main

            squashfs-tools est bien installé ?

              je viens de me rendre compte que ce n’est pas snap que j’ai utilisé pour HanBrake mais flatpack.
              N’ayant aucun logiciel sous snap, je fais snap install vivaldi et cela marche.
              Le débit pour vivaldi est trop lent pour ce soir, je l’ai interrompu ce qui explique l’erreur finale, le core s’est installé normalement

              ● snapd.service - Snap Daemon
     Loaded: loaded (/usr/lib/systemd/system/snapd.service; disabled; preset: disabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: active (running) since Fri 2024-10-18 21:23:13 EEST; 4min 53s ago
 Invocation: a3aad29d78ae450a829585cb620ab4c4
TriggeredBy: ● snapd.socket
   Main PID: 38468 (snapd)
      Tasks: 14 (limit: 9399)
     Memory: 123.9M (peak: 137.7M)
        CPU: 17.576s
     CGroup: /system.slice/snapd.service
             └─38468 /usr/libexec/snapd/snapd

oct. 18 21:23:13 fedora snapd[38468]: overlord.go:271: Acquiring state lock file
oct. 18 21:23:13 fedora snapd[38468]: overlord.go:276: Acquired state lock file
oct. 18 21:23:13 fedora snapd[38468]: daemon.go:250: started snapd/2.65.1-0.fc41 (series 16; classic; devmode) fedora/41 (amd64) linux/6.11.4-300.fc41.x86_64.
oct. 18 21:23:13 fedora snapd[38468]: daemon.go:353: adjusting startup timeout by 55s (pessimistic estimate of 30s plus 5s per snap)
oct. 18 21:23:13 fedora snapd[38468]: backends.go:58: AppArmor status: apparmor not enabled
oct. 18 21:23:13 fedora systemd[1]: Started snapd.service - Snap Daemon.
oct. 18 21:23:13 fedora snapd[38468]: api_snaps.go:468: Installing snap "vivaldi" revision unset
oct. 18 21:23:16 fedora snapd[38468]: storehelpers.go:1019: cannot refresh: snap has no updates available: "bare", "core20", "gnome-3-38-2004", "gtk-common-themes", "snapd"
oct. 18 21:25:10 fedora snapd[38468]: taskrunner.go:299: Change 24 task (Download snap "gnome-42-2204" (176) from channel "stable") failed: the download has been cancelled: context canceled
oct. 18 21:25:10 fedora snapd[38468]: taskrunner.go:299: Change 24 task (Download snap "vivaldi" (58) from channel "stable") failed: the download has been cancelled: context canceled

              Hardelot je remarque seulement maintenant que snapd marchait bien au post 16 :
              Active: active (running) since Fri 2024-10-18 14:00:05 CEST; 6s ago
              alors qu’au 17, cela ne marche plus…
              Que se passe-t-il si tu refais
              # systemctl start snapd

                  et plus précisément, pas de message d’erreur ?
                  Vérifier que le module squashfs est bien chargé, puis relancer # systemctl start snapd et nous donner le retour

                  deviennenicolas@Nicolas:~$ sudo su
[sudo] Mot de passe de deviennenicolas : 
root@Nicolas:/home/deviennenicolas# dnf install squashfs
Updating and loading repositories:
 skype (unstable)                                                                                                                                     100% |  13.2 KiB/s |   1.5 KiB |  00m00s
>>> Status code: 503 for https://repo.skype.com/rpm/unstable/repodata/repomd.xml (IP: 104.115.88.163) - https://repo.skype.com/rpm/unstable/repodata/repomd.xml - repomd.xml
>>> Status code: 503 for https://repo.skype.com/rpm/unstable/repodata/repomd.xml (IP: 104.115.88.163) - https://repo.skype.com/rpm/unstable/repodata/repomd.xml - repomd.xml
>>> Status code: 503 for https://repo.skype.com/rpm/unstable/repodata/repomd.xml (IP: 104.115.88.163) - https://repo.skype.com/rpm/unstable/repodata/repomd.xml - repomd.xml
>>> Status code: 503 for https://repo.skype.com/rpm/unstable/repodata/repomd.xml (IP: 104.115.88.163) - https://repo.skype.com/rpm/unstable/repodata/repomd.xml - repomd.xml
>>> Erreur librepo : Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
 MEGAsync                                                                                                                                             ???% |   0.0   B/s |   0.0   B |  00m00s
>>> Status code: 404 for https://mega.nz/linux/repo/Fedora_41/repodata/repomd.xml (IP: 31.216.145.5) - https://mega.nz/linux/repo/Fedora_41/repodata/repomd.xml - repomd.xml
>>> Status code: 404 for https://mega.nz/linux/repo/Fedora_41/repodata/repomd.xml (IP: 31.216.145.5) - https://mega.nz/linux/repo/Fedora_41/repodata/repomd.xml - repomd.xml
>>> Status code: 404 for https://mega.nz/linux/repo/Fedora_41/repodata/repomd.xml (IP: 31.216.145.5) - https://mega.nz/linux/repo/Fedora_41/repodata/repomd.xml - repomd.xml
>>> Status code: 404 for https://mega.nz/linux/repo/Fedora_41/repodata/repomd.xml (IP: 31.216.145.5) - https://mega.nz/linux/repo/Fedora_41/repodata/repomd.xml - repomd.xml
>>> Erreur librepo : Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
Repositories loaded.
Échec de la résolution de la transaction:
Aucune correspondance pour l'argument : squashfs
You can try to add to command line:
  --skip-unavailable to skip unavailable packages
root@Nicolas:/home/deviennenicolas# dnf install squashfs --skip-unavailable
Updating and loading repositories:
 skype (unstable)                                                                                                                                     100% |  18.0 KiB/s |   1.5 KiB |  00m00s
>>> Status code: 503 for https://repo.skype.com/rpm/unstable/repodata/repomd.xml (IP: 104.115.88.163) - https://repo.skype.com/rpm/unstable/repodata/repomd.xml - repomd.xml
>>> Status code: 503 for https://repo.skype.com/rpm/unstable/repodata/repomd.xml (IP: 104.115.88.163) - https://repo.skype.com/rpm/unstable/repodata/repomd.xml - repomd.xml
>>> Status code: 503 for https://repo.skype.com/rpm/unstable/repodata/repomd.xml (IP: 104.115.88.163) - https://repo.skype.com/rpm/unstable/repodata/repomd.xml - repomd.xml
>>> Status code: 503 for https://repo.skype.com/rpm/unstable/repodata/repomd.xml (IP: 104.115.88.163) - https://repo.skype.com/rpm/unstable/repodata/repomd.xml - repomd.xml
>>> Erreur librepo : Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
 MEGAsync                                                                                                                                             ???% |   0.0   B/s |   0.0   B |  00m00s
>>> Status code: 404 for https://mega.nz/linux/repo/Fedora_41/repodata/repomd.xml (IP: 31.216.144.5) - https://mega.nz/linux/repo/Fedora_41/repodata/repomd.xml - repomd.xml
>>> Status code: 404 for https://mega.nz/linux/repo/Fedora_41/repodata/repomd.xml (IP: 31.216.144.5) - https://mega.nz/linux/repo/Fedora_41/repodata/repomd.xml - repomd.xml
>>> Status code: 404 for https://mega.nz/linux/repo/Fedora_41/repodata/repomd.xml (IP: 31.216.144.5) - https://mega.nz/linux/repo/Fedora_41/repodata/repomd.xml - repomd.xml
>>> Status code: 404 for https://mega.nz/linux/repo/Fedora_41/repodata/repomd.xml (IP: 31.216.144.5) - https://mega.nz/linux/repo/Fedora_41/repodata/repomd.xml - repomd.xml
>>> Erreur librepo : Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
Repositories loaded.
Aucune correspondance pour l'argument : squashfs

Nothing to do.
root@Nicolas:/home/deviennenicolas# systemctl start snapd
root@Nicolas:/home/deviennenicolas# snap install makemkv
error: system does not fully support snapd: cannot mount squashfs image using "squashfs":
       ----- mount: /tmp/syscheck-mountpoint-932730702: 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.

       -----
root@Nicolas:/home/deviennenicolas#

                  c’est squashfs-tools et non juste squashfs qu’il faut installer

                  activer un module ce n’et pas installer un paquet
                  # lsmod | grep squashfs
                  S’il n’y a pas de retour c’est qu’in m’est pas charger, pour le charger
                  # modprobe squashfs
                  refaire la vérification pour voir s’il est bien là,
                  si oui vérifier l’état de snapd avec
                  systemctl status snapd
                  s’il est en ligne 5
                  Active: inactive
                  Alors essayer
                  systemctl start snapd
                  et nous donner le retour.

                  Désolé mais cela ne sert à rien de faire des réinstalles, si on est pas assez clair, demander avant de taper à l’aveuglette

                    fgland

                    deviennenicolas@Nicolas:~$ sudo su
root@Nicolas:/home/deviennenicolas# lsmod | grep squashfs
squashfs               98304  0
root@Nicolas:/home/deviennenicolas# modprobe squashfs
root@Nicolas:/home/deviennenicolas# systemctl status snapd
○ snapd.service - Snap Daemon
     Loaded: loaded (/usr/lib/systemd/system/snapd.service; disabled; preset: disabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: inactive (dead) since Sat 2024-10-19 10:20:23 CEST; 3h 6min ago
   Duration: 8.032s
 Invocation: 1fe516d1e2534e848bbbfd6dd5842cc4
TriggeredBy: ● snapd.socket
    Process: 24131 ExecStart=/usr/libexec/snapd/snapd (code=exited, status=42)
   Main PID: 24131 (code=exited, status=42)
   Mem peak: 11.5M
        CPU: 60ms

oct. 19 10:20:15 Nicolas snapd[24131]:        dmesg(1) may have more information after failed mount system call.
oct. 19 10:20:15 Nicolas snapd[24131]: -----
oct. 19 10:20:15 Nicolas snapd[24131]: daemon.go:353: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)
oct. 19 10:20:15 Nicolas snapd[24131]: backends.go:58: AppArmor status: apparmor not enabled
oct. 19 10:20:15 Nicolas systemd[1]: Started snapd.service - Snap Daemon.
oct. 19 10:20:20 Nicolas snapd[24131]: daemon.go:548: gracefully waiting for running hooks
oct. 19 10:20:20 Nicolas snapd[24131]: daemon.go:550: done waiting for running hooks
oct. 19 10:20:23 Nicolas snapd[24131]: overlord.go:515: Released state lock file
oct. 19 10:20:23 Nicolas snapd[24131]: daemon stop requested to wait for socket activation
oct. 19 10:20:23 Nicolas systemd[1]: snapd.service: Deactivated successfully.
root@Nicolas:/home/deviennenicolas#  systemctl start snapd
root@Nicolas:/home/deviennenicolas# exit
exit
deviennenicolas@Nicolas:~$ snap install makemkv
error: system does not fully support snapd: cannot mount squashfs image using "squashfs":
       ----- mount: /tmp/syscheck-mountpoint-260761303: 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.

       -----
deviennenicolas@Nicolas:~$ sudo snap install makemkv
error: system does not fully support snapd: cannot mount squashfs image using "squashfs":
       ----- mount: /tmp/syscheck-mountpoint-260761303: 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.

       -----
deviennenicolas@Nicolas:~$

                      j’abandonne mais une dernière fois…
                      si squashfs est présent, il n’y a pas faire modprobe ! je croyais avoir été clair.
                      Après avoir fait systemctl start snapd il aurait fallut refaire systemctl status snapd pour voir s’il est passé en actif
                      Y aurait-il un problème avec Selinux, je vois qu’il y a un paquet snapd-selinux, est-il installé chez toi ?
                      Je ne l’ai pas mais j’ai désactivé Selinux, c’est pas bien je sais

                      10 jours plus tard

                      Quand j’ai vu que cela ne fonctionnait pas je suis reparti à la 40 d’où mon silence et là, la 41… release installée, tout fonctionne.