Linux Snap Refresh In Progress Lock Error — What It Means & How to Fix It

Fix Snap package manager 'snap change in progress' or refresh lock preventing new installations or updates from running. This guide covers everything you need to know about this topic, including common causes, step-by-step solutions, and answers to frequently asked questions.

Here are the key things to understand: Snap uses a sequential change queue — only one operation can run at a time. If a snap refresh gets stuck or fails mid-way, it can block all subsequent snap operations. This is common after interrupted updates, failed downloads, or when snapd restarts during an operation. The error message typically includes a change ID number that can be used to investigate. Understanding these fundamentals will help you diagnose and resolve this issue more effectively.

The most common reasons this occurs include: Previous snap refresh was interrupted by reboot, network failure, or manual cancellation. snapd service crashed during a change leaving it in an incomplete state. Automatic refresh started and is still downloading large snaps in the background. Insufficient disk space preventing the refresh from completing. Identifying the root cause is the first step toward finding the right solution.

To resolve this, follow these recommended steps: Check pending changes: snap changes to see all running and pending operations with their status. Abort stuck changes: sudo snap abort <change-id> for the stuck operation. If abort does not work, restart snapd: sudo systemctl restart snapd then try aborting again. As a last resort, manually clear stuck state: sudo snap set system refresh.hold=forever, fix the issue, then snap unset system refresh.hold. If these steps do not resolve the issue, consider consulting additional resources or a qualified professional.

This article is part of our Linux Error Codes collection on Error Codes Wiki. We provide comprehensive, up-to-date information to help you find solutions quickly.