How to fix subprocess installed pre-removal script returned error exit status 1 in APT

Start with basic cleanup and reconfiguration commands. This fixes many corrupted package database issues:

sudo apt-get clean
sudo apt-get update
sudo dpkg --configure -a

Then try removing or upgrading the package again:

sudo apt-get upgrade

This approach is non-destructive and resolves the majority of pre-removal script errors. If this works, you're done.

If dpkg reports broken dependencies after the above, use apt's fix-broken-install feature:

sudo apt-get install -f
sudo apt-get upgrade

The -f flag tells apt to try to fix broken package dependencies. This resolves dependency conflicts that may be preventing the pre-removal script from running correctly.

If the package still won't budge, use dpkg's force-remove options. First identify the exact package name from the error message:

sudo dpkg --remove --force-remove-reinstreq PACKAGE_NAME

Replace PACKAGE_NAME with the actual package (e.g., mariadb-server, docker.io, etc.).

If that fails, you can move the problematic script files and try again:

sudo mv /var/lib/dpkg/info/PACKAGE_NAME.prerm /tmp/
sudo mv /var/lib/dpkg/info/PACKAGE_NAME.postrm /tmp/
sudo dpkg --remove --force-remove-reinstreq PACKAGE_NAME

Then reinstall the package if needed:

sudo apt-get install PACKAGE_NAME

If you control the package or know it's safe, you can edit the pre-removal script directly:

sudo nano /var/lib/dpkg/info/PACKAGE_NAME.prerm

Either fix the script logic or replace the entire contents with a safe no-op:

#!/bin/bash
exit 0

Save the file (Ctrl+O, Enter, Ctrl+X), then attempt package removal again.

In rare cases, dpkg lock files may be stuck. Clear them and reconfigure:

sudo rm -f /var/lib/dpkg/lock-frontend
sudo rm -f /var/lib/dpkg/lock
sudo rm -f /var/cache/apt/archives/lock
sudo dpkg --configure -a

After clearing locks, retry your apt operations.