Snap stopped working on F41

Ask Fedora
,
1

Hello,

Recently (I’m not sure for how long, though) my snap installation stopped working correctly. I can successfully perform basic commands (like listing installed packages, etc.) and it seems that existing packages get automatic updates, but I can’t install or remove any of them.

For example, when trying to install a package (e.g., sudo snap install hello-world), I get the following error:

sudo snap install hello-world
error: system does not fully support snapd: unexpected snapd tooling directory /usr/lib/snapd on
       fedora

Following the official documentation: Installing snap on Fedora | Snapcraft documentation & Fix common issues | Snapcraft documentation i’ve :

  • tried to reinstall snap
  • checked that the /snap link exists: sudo ln -s /var/lib/snapd/snap /snap
  • checked that kernel-modules are installed: (e.g. sudo dnf install kernel-modules)

I can’t find any meaningful errors in logs, other than these entries:

Aug 01 02:22:32 electron snapd[9884]: taskrunner.go:299: Change 735 task (Run install hook of “mesa-2404” snap if present) failed: run hook “install”:
Aug 01 02:22:32 electron snapd[9884]: -----
Aug 01 02:22:32 electron snapd[9884]: + mkdir --parents --verbose /var/snap/mesa-2404/887/kernel-gpu-2404
Aug 01 02:22:32 electron snapd[9884]: mkdir: created directory ‘/var/snap/mesa-2404/887/kernel-gpu-2404’
Aug 01 02:22:32 electron snapd[9884]: + dirname /snap/mesa-2404/887/meta/hooks/install
Aug 01 02:22:32 electron snapd[9884]: + cd – /snap/mesa-2404/887/meta/hooks
Aug 01 02:22:32 electron snapd[9884]: + pwd -P
Aug 01 02:22:32 electron snapd[9884]: + HOOKS=/snap/mesa-2404/887/meta/hooks
Aug 01 02:22:32 electron snapd[9884]: + snapctl is-connected kernel-gpu-2404
Aug 01 02:22:32 electron snapd[9884]: error: system does not fully support snapd: unexpected snapd tooling directory /usr/lib/snapd on fedora
Aug 01 02:22:32 electron snapd[9884]: + . /snap/mesa-2404/887/meta/hooks/disconnect-plug-kernel-gpu-2404
Aug 01 02:22:32 electron snapd[9884]: + set -xeu
Aug 01 02:22:32 electron snapd[9884]: + rm --force --verbose /var/snap/mesa-2404/887/kernel-gpu-2404/kernel-gpu-2404-sentinel
Aug 01 02:22:32 electron snapd[9884]: + snapctl stop --disable mesa-2404.component-monitor
Aug 01 02:22:32 electron snapd[9884]: error: system does not fully support snapd: unexpected snapd tooling directory /usr/lib/snapd on fedora
Aug 01 02:22:32 electron snapd[9884]: -----

or

Aug 01 03:04:16 electron systemd[1]: Starting snapd.service - Snap Daemon…
Aug 01 03:04:16 electron snapd[16453]: overlord.go:284: Acquiring state lock file
Aug 01 03:04:16 electron snapd[16453]: overlord.go:289: Acquired state lock file
Aug 01 03:04:16 electron snapd[16453]: daemon.go:273: started snapd/2.70-1.fc41 (series 16; classic; devmode) fedora/41 (amd64) linux/6.15.8-100.fc41.x86_64.
Aug 01 03:04:16 electron snapd[16453]: main.go:142: system does not fully support snapd: unexpected snapd tooling directory /usr/lib/snapd on fedora
Aug 01 03:04:16 electron snapd[16453]: daemon.go:367: adjusting startup timeout by 2m50s (pessimistic estimate of 30s plus 5s per snap)
Aug 01 03:04:16 electron snapd[16453]: backends.go:68: AppArmor status: apparmor not enabled
Aug 01 03:04:16 electron systemd[1]: Started snapd.service - Snap Daemon.

I’v also noticed a few SELinux denials, but it’s in Permissive mode.

Some details:

> uname -a
Linux electron 6.15.8-100.fc41.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Jul 24 12:25:37 >UTC 2025 x86_64 GNU/Linux

> getenforce
Permissive

> snap version
snap    2.70-1.fc41
snapd   2.70-1.fc41
series  16
fedora  41
kernel  6.15.8-100.fc41.x86_64

 > systemctl status snapd snapd.socket
● 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, 50-keep-warm.conf
     Active: active (running) since Fri 2025-08-01 03:04:16 EDT; 1min 34s ago
 Invocation: 30d9a93b978d4211b932b83705cb7e5d
TriggeredBy: ● snapd.socket
   Main PID: 16453 (snapd)
      Tasks: 22 (limit: 37835)
     Memory: 18.2M (peak: 23.8M)
        CPU: 1.386s
     CGroup: /system.slice/snapd.service
             └─16453 /usr/libexec/snapd/snapd

Aug 01 03:04:16 electron snapd[16453]: desktop.go:308: cannot read instance name from "/var/lib/snapd/desktop/applications/xmind_xmind.desktop": desktop file "/var/lib/snapd/>
Aug 01 03:04:16 electron snapd[16453]: desktop.go:308: cannot read instance name from "/var/lib/snapd/desktop/applications/xmind_xmind.desktop": desktop file "/var/lib/snapd/>
Aug 01 03:04:16 electron snapd[16453]: desktop.go:308: cannot read instance name from "/var/lib/snapd/desktop/applications/xmind_xmind.desktop": desktop file "/var/lib/snapd/>
Aug 01 03:04:16 electron snapd[16453]: desktop.go:308: cannot read instance name from "/var/lib/snapd/desktop/applications/xmind_xmind.desktop": desktop file "/var/lib/snapd/>
Aug 01 03:04:16 electron snapd[16453]: desktop.go:308: cannot read instance name from "/var/lib/snapd/desktop/applications/xmind_xmind.desktop": desktop file "/var/lib/snapd/>
Aug 01 03:04:16 electron snapd[16453]: desktop.go:308: cannot read instance name from "/var/lib/snapd/desktop/applications/xmind_xmind.desktop": desktop file "/var/lib/snapd/>
Aug 01 03:04:16 electron snapd[16453]: desktop.go:308: cannot read instance name from "/var/lib/snapd/desktop/applications/xmind_xmind.desktop": desktop file "/var/lib/snapd/>
Aug 01 03:04:16 electron snapd[16453]: desktop.go:308: cannot read instance name from "/var/lib/snapd/desktop/applications/xmind_xmind.desktop": desktop file "/var/lib/snapd/>
Aug 01 03:04:16 electron snapd[16453]: desktop.go:308: cannot read instance name from "/var/lib/snapd/desktop/applications/xmind_xmind.desktop": desktop file "/var/lib/snapd/>
Aug 01 03:04:16 electron snapd[16453]: desktop.go:308: cannot read instance name from "/var/lib/snapd/desktop/applications/xmind_xmind.desktop": desktop file "/var/lib/snapd/>

● snapd.socket - Socket activation for snappy daemon
     Loaded: loaded (/usr/lib/systemd/system/snapd.socket; enabled; preset: enabled)
     Active: active (running) since Fri 2025-08-01 03:04:16 EDT; 1min 34s ago
 Invocation: e991d8b6ba8e4d96a3b4acbceab2c0fb
   Triggers: ● snapd.service
     Listen: /run/snapd.socket (Stream)
             /run/snapd-snap.socket (Stream)
      Tasks: 0 (limit: 37835)
     Memory: 0B (peak: 0B)
        CPU: 1ms
     CGroup: /system.slice/snapd.socket

Aug 01 03:04:16 electron systemd[1]: Starting snapd.socket - Socket activation for snappy daemon...
Aug 01 03:04:16 electron systemd[1]: Listening on snapd.socket - Socket activation for snappy daemon.

> echo $PATH
[...]:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/var/lib/snapd/snap/bin

> sudo dnf update
Updating and loading repositories:
Repositories loaded.
Nothing to do.

I’ve also tried searching online, but I can’t find any similar issues.

Can anyone help please?

2

If you’re looking for a solution, here is the manual fix:

Simply remove the old snapd symlink from /usr/lib and then restart the snapd service:

[ -L '/usr/lib/snapd' ] && sudo rm -rfi '/usr/lib/snapd'
sudo systemctl restart snapd

Why?

Due to recent updates (see this commit), Fedora is now expected to use /usr/libexec/snapd instead of /usr/lib/snapd as its tooling directory.