This error occurs when a snap installation is interrupted or when concurrent snap operations are attempted simultaneously, leaving the snap daemon unable to complete. The snap system locks the package to prevent further actions until the stuck process is aborted.
The "install-snap" change in progress error indicates that the Snap daemon detected an incomplete or interrupted installation operation. This lock prevents any further actions on that snap package. The error typically occurs when an installation is interrupted due to manual cancellation, system freeze, network interruption, or when multiple snap operations are attempted at the same time. The snap system uses change tracking to manage operations, and this error means a previous change is still marked as "Doing" even though it may not be actively running.
First, list all ongoing snap operations to identify which one is stuck:
snap changesThis command displays all snap changes with their status. Look for any change with a status of "Doing" - this is your stuck process. Note the ID number of the stuck change.
Once you've identified the stuck change ID, abort it using the sudo snap abort command:
sudo snap abort <ID>Replace <ID> with the actual change ID number from the previous step. For example: sudo snap abort 8
Run snap changes again to confirm the stuck change is now marked as "Done" or "Error":
snap changesThe previously stuck change should no longer show a "Doing" status.
Now attempt to install (or perform your desired operation) on the snap package again:
sudo snap install package-nameThe installation should now proceed without the "change in progress" error. If you're installing a different package, replace package-name with the actual snap name.
If aborting the change doesn't resolve the issue, you can try removing snap lock files manually: sudo rm /var/lib/snapd/lock and sudo rm /var/lib/snapd/seed.lock. In severe cases, restarting the snap daemon with sudo systemctl restart snapd or rebooting the system may be necessary. To prevent this error in the future, avoid running multiple snap operations concurrently and monitor your system resources to prevent interruptions during installations. If the error persists after all attempts, check snap daemon logs with sudo snap debug requests for more detailed error information.
E: Could not connect to proxy server
Could not connect to proxy server
E: Package 'package:i386' has no installation candidate
How to fix "Package package:i386 has no installation candidate" in apt
E: The value 'value' is invalid for APT::Default-Release
How to fix invalid APT::Default-Release value in APT
dpkg: error: unable to create new file 'path': Permission denied
How to fix dpkg permission denied errors in APT
subprocess installed post-removal script returned error exit status 1
How to fix "subprocess installed post-removal script returned error exit status 1" in APT