How to Fix Snap Not Working or Installing Apps on Ubuntu Desktop (2026 Guide)

What Is Snapd and Why Snap Breaks on Ubuntu

Snap is Ubuntu's universal package manager, developed by Canonical to distribute containerised applications across Linux distributions. When you run snap install vlc or open the Snap Store to grab VS Code, Discord, or Spotify, your system relies on a background service called snapd (the Snap daemon) to handle all communication, downloads, and mounts.

When snapd stops responding, gets stuck in a broken state, or is simply not installed, every snap command fails — sometimes silently, sometimes with a wall of cryptic errors. The good news is that almost every snap failure on Ubuntu Desktop traces back to one of a handful of root causes, and each one has a clear fix.

This guide covers the most common snap problems on Ubuntu 22.04 LTS, 24.04 LTS, and 24.10 in 2026, with step-by-step terminal commands to get you back up and running.

How Snap Works Under the Hood

When you run any snap command, the CLI talks to the snapd socket at /run/snapd.socket. If that socket is missing or the daemon behind it is dead, you immediately get the dreaded cannot communicate with server error. Snapd also maintains a database of ongoing operations — called changes — and if a previous install or refresh crashed mid-way, the database is left locked, blocking all future operations until the stale change is aborted.

Common Snap Error Messages Explained

Before diving into fixes, it helps to understand exactly what each error means so you apply the right solution first time.

• cannot communicate with server: dial unix /run/snapd.socket: connect: connection refused — The snapd service is not running or has crashed. The socket file exists but nothing is listening on it, or the file is missing entirely.
• snap "package-name" has "install-snap" change in progress — A previous installation was interrupted (power cut, network drop, manual kill) and the operation was never cleanly aborted. Snap refuses to start a second operation on the same package until the first is resolved.
• snapd is not running — Systemd reports that the snapd unit failed or was never started. Often seen on minimal Ubuntu installs or after a failed system update.
• snap: command not found — The snap binary is not on your PATH, which usually means the snapd package was removed or was never installed. It can also appear in a shell session started before snapd was installed — logging out and back in fixes that variant.
• error: too many requests (429) — The Snap Store rate-limits excessive refresh attempts. Wait a few minutes and try again, or check whether a proxy or VPN is interfering.
• Mount namespace processing failure — A kernel module (squashfs or overlayfs) failed to load, or AppArmor policies are blocking snap mounts. Usually seen after a kernel upgrade without a reboot.

How to Restart and Repair the Snapd Service

The single fastest fix for most snap failures is restarting the snapd service. Open a terminal (Ctrl + Alt + T) and run the following commands in order.

Step 1 — Check the current snapd status

1. Run: systemctl status snapd
2. Look for Active: active (running). If you see failed, inactive, or dead, proceed to the next steps.
3. Scroll through the journal output for any error messages — they often name the exact file or module that caused the failure.

Step 2 — Restart the snapd service

1. Run: sudo systemctl restart snapd
2. Wait about 10 seconds, then check the status again: systemctl status snapd
3. If the service is now active, test it: snap list

Step 3 — Enable snapd to start automatically on boot

On some Ubuntu installations, snapd is installed but not enabled as a systemd service. Run:

1. sudo systemctl enable --now snapd
2. sudo systemctl enable --now snapd.apparmor
3. Reboot: sudo reboot

Step 4 — Reinstall snapd if the service will not start

If snapd keeps failing to start even after a restart, the package itself may be corrupted. Reinstall it cleanly:

1. sudo apt update
2. sudo apt install --reinstall snapd
3. sudo systemctl start snapd
4. Verify: snap version

Fix 'Cannot Communicate with Server' and Stuck Snap Changes

These two errors are the most disruptive because they block every snap operation, not just one package. Here is how to resolve each.

Fixing 'cannot communicate with server'

1. Confirm the snapd socket is missing or dead: ls -la /run/snapd.socket — if the file does not exist, snapd is definitely not running.
2. Restart snapd: sudo systemctl restart snapd
3. If that fails, check for lock files left by a previous crash: sudo rm -f /var/lib/snapd/lock then restart snapd again.
4. Verify the socket is now present: ls -la /run/snapd.socket
5. Run a test command: snap find firefox

Aborting a Stuck 'install-snap change in progress'

When an install is stuck mid-way, snap's change database holds an open record. You must identify and abort it before any new operation can proceed.

1. List all current and recent changes: snap changes
2. Find the entry with status Doing or Error and note its ID number (for example, 42).
3. Abort it: sudo snap abort 42 — replace 42 with your actual change ID.
4. Confirm the change is now marked Hold or Error: snap changes
5. Retry your original install: sudo snap install <package-name>

Removing stale lock files

If aborting the change does not help, stale lock files are likely the culprit:

1. sudo systemctl stop snapd
2. sudo rm -f /var/lib/snapd/lock
3. sudo rm -f /var/lib/snapd/seed.lock
4. sudo systemctl start snapd
5. Wait 15 seconds and retry: snap list

Reinstall or Refresh the Snap Store

The Snap Store itself is a snap package (snap-store). It can get stuck, fail to update, or refuse to launch after a botched refresh — especially on Ubuntu 22.04 and 24.04 where it ships as a default application.

Refresh the Snap Store

1. Kill any running instance: sudo snap stop snap-store
2. Force a refresh: sudo snap refresh snap-store
3. Relaunch: snap run snap-store

Reinstall the Snap Store from scratch

If a refresh does not help, remove and reinstall the snap-store package entirely:

1. sudo snap remove snap-store
2. sudo snap install snap-store
3. If the store still will not launch, try refreshing all snaps first: sudo snap refresh then reinstall.

Resetting snapd state completely (last resort)

In rare cases where snapd's database is corrupted beyond repair, a full reset is necessary. Warning: this removes all installed snaps and their data.

1. sudo systemctl stop snapd snapd.socket snapd.seeded
2. sudo apt purge snapd
3. sudo rm -rf /var/lib/snapd
4. sudo apt install snapd
5. sudo systemctl enable --now snapd snapd.apparmor
6. Reinstall your snaps: sudo snap install snap-store && sudo snap install vlc (and any others you need)

If repeated snap failures are eating your productivity, our team at CloudHouse offers professional desktop support — remote technicians can diagnose and fix complex snapd issues in minutes without you needing to touch the terminal.

Additional Snap Troubleshooting Tips

After a kernel upgrade — reboot first

Snap uses squashfs mounts and kernel namespaces. After any kernel update, snap commands can fail with mount errors until the system is rebooted into the new kernel. Always run sudo reboot after apt upgrade if a new kernel was installed.

Check AppArmor is not blocking snapd

1. sudo aa-status | grep snap
2. If snap profiles appear in enforce mode and you are seeing permission errors, try: sudo systemctl restart apparmor && sudo systemctl restart snapd

Verify network access for snap refresh

Snapd communicates with api.snapcraft.io over HTTPS (port 443). If a firewall or proxy blocks this, refreshes and new installs will time out silently. Test with: curl -I https://api.snapcraft.io — you should get a 200 or 301 response.

Fix 'snap: command not found' on a fresh terminal

If snap was just installed in the current terminal session, the PATH may not have updated. Either open a new terminal window, run source ~/.bashrc, or log out and log back in. If the command is still not found, confirm the binary exists: which snap or ls /usr/bin/snap.

Frequently Asked Questions

Why does snap say 'cannot communicate with server' even though snapd is installed?

This error means the snapd daemon is installed but not currently running, or its Unix socket at /run/snapd.socket is missing. Run sudo systemctl restart snapd to start it, then verify with systemctl status snapd. If the service fails to start, check the journal with journalctl -xe | grep snapd for the underlying error.

How do I abort a stuck snap installation that says 'change in progress'?

Run snap changes to list all pending operations. Find the one showing status Doing or Error and note its numeric ID. Then run sudo snap abort <ID> to cancel it. After aborting, wait a moment and retry your original snap install command.

Why is my Snap Store not opening or loading on Ubuntu 22.04 / 24.04?

The Snap Store application (snap-store) is itself a snap and can fail after an incomplete self-update. Kill it with sudo snap stop snap-store, force a refresh with sudo snap refresh snap-store, then relaunch. If it still won't open, remove and reinstall it: sudo snap remove snap-store && sudo snap install snap-store.

Does removing snapd also remove all my installed snap apps?

Yes. Purging snapd with sudo apt purge snapd removes snapd and unmounts all snap packages. Reinstalling snapd starts fresh — you will need to reinstall each snap app individually. Always note your installed snaps first with snap list before purging.

Why does snap work fine from one user account but fail from another on the same Ubuntu machine?

Snap commands run as root via sudo, so user-level PATH or environment differences rarely affect core snap operations. However, snap GUI apps launched from a desktop session can fail if the user's AppArmor profile or home directory permissions differ. Check that the affected user is not in a restricted profile and that /home/<username> has correct ownership: ls -la /home/ and id <username>.