How to fix dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) in APT

APTINTERMEDIATEHIGHUpdated May 30, 2026· 427 views

The "paste subprocess was killed by signal" error occurs during package installation when dpkg encounters a subprocess failure, typically caused by file conflicts, insufficient disk space, or package database corruption. Resolve by checking disk space, fixing broken packages, or forcing package overwrites.

Quick fix

Fixes dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

df -h
  1. Check available disk space
  2. Identify file conflicts
  3. Fix broken package installation
  4. Force overwrite conflicting files (if needed)
apt — error
df -h
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

What this error means

This error indicates that dpkg-deb, the Debian package management tool, encountered an unexpected termination of a subprocess while unpacking or processing a .deb archive. The "broken pipe" signal usually means a subprocess process was abruptly killed, which prevents the package installation or upgrade from completing. This is often a secondary symptom of an underlying problem such as file conflicts between packages, insufficient disk space, or issues with package extraction.

Typical symptoms

  • Package installation or upgrade halts unexpectedly with the broken pipe error
  • System left in partially installed state after failed package operation
  • Multiple package installation attempts fail with the same error
  • Error appears when installing or upgrading software via apt or dpkg commands
  • Related error messages mention file conflicts or "trying to overwrite" file paths

Common causes

  1. File conflicts between packages where two packages claim ownership of the same file
  2. Insufficient disk space on the system, especially on /boot, /var, or root partitions
  3. Corrupted or inconsistent package database state
  4. Interrupted or failed previous package installation leaving incomplete state
  5. Issues extracting or copying package data due to file permissions or mount issues

How to fix "dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)"

1Check available disk space

First, verify you have sufficient free disk space, especially on critical partitions:

bash
df -h

Look for partitions that are 85% or more full. If /boot is full, consider removing old kernel images. If /var is full, clean up apt cache:

bash
sudo apt clean
sudo apt autoclean
2Identify file conflicts

Check the full output of your apt command for clues about which packages are conflicting. Look for messages like "trying to overwrite '/path/to/file', which is also in package [package-name]". Note down the conflicting package names and file paths.

3Fix broken package installation

Use apt to repair any broken package dependencies:

bash
sudo apt --fix-broken install

This command will attempt to resolve any incomplete package installations or dependency issues.

4Force overwrite conflicting files (if needed)

If you have identified conflicting packages, you can force dpkg to overwrite the file. This should only be used when you understand the conflict and are willing to replace the file:

bash
sudo dpkg -i --force-overwrite /path/to/package.deb

After forcing the overwrite, repair any remaining issues:

bash
sudo apt --fix-broken install
5Repair package database integrity

If the issue persists, rebuild the package database cache:

bash
sudo apt update
sudo apt install -f

The -f flag tells apt to fix broken dependencies. If this still doesn't resolve the issue, you can attempt a dpkg configuration reset:

bash
sudo dpkg --configure -a
6Restore from backup (last resort)

If you have a Timeshift or other system backup created before the failed installation, restoring from the snapshot is the safest way to recover. This completely undoes the failed package operation and returns the system to a known working state:

bash
# Launch Timeshift from system menu or via terminal
timeshift-launcher

Select a snapshot from before the failed installation and restore.

Advanced notes

In rare cases where file conflicts result from buggy package transitions, the maintainers may have made errors by including files in the wrong package. The --force-overwrite flag is a workaround for such packaging errors but should be used cautiously. For containerized environments (Docker, LXC, Proxmox), broken pipe errors can also indicate resource constraints or mount point issues within the container. On systems with SELinux or AppArmor enabled, the error can also result from policy violations preventing file operations. If you regularly encounter this error, ensure your system is up-to-date with security patches and consider regularly running apt upgrade to avoid large accumulations of conflicting package versions.

Frequently asked questions

What does "dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)" mean?
deb archive. The "broken pipe" signal usually means a subprocess process was abruptly killed, which prevents the package installation or upgrade from completing. This is often a secondary symptom of an underlying problem such as file conflicts between packages, insufficient disk space, or issues with package extraction.
How do I fix "dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)"?
The "paste subprocess was killed by signal" error occurs during package installation when dpkg encounters a subprocess failure, typically caused by file conflicts, insufficient disk space, or package database corruption. Resolve by checking disk space, fixing broken packages, or forcing package overwrites.
What causes "dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)"?
File conflicts between packages where two packages claim ownership of the same file Insufficient disk space on the system, especially on /boot, /var, or root partitions Corrupted or inconsistent package database state
Is the "dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)" error serious?
Yes. This is a high-severity error that usually blocks work until it is fixed, but the steps above resolve it.

Official resources & further reading