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.
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.
First, verify you have sufficient free disk space, especially on critical partitions:
df -hLook 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:
sudo apt clean
sudo apt autocleanCheck 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.
Use apt to repair any broken package dependencies:
sudo apt --fix-broken installThis command will attempt to resolve any incomplete package installations or dependency issues.
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:
sudo dpkg -i --force-overwrite /path/to/package.debAfter forcing the overwrite, repair any remaining issues:
sudo apt --fix-broken installIf the issue persists, rebuild the package database cache:
sudo apt update
sudo apt install -fThe -f flag tells apt to fix broken dependencies. If this still doesn't resolve the issue, you can attempt a dpkg configuration reset:
sudo dpkg --configure -aIf 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:
# Launch Timeshift from system menu or via terminal
timeshift-launcherSelect a snapshot from before the failed installation and restore.
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.
dpkg: serious warning: files list file for package 'package-name' contains empty filename
How to fix "files list file contains empty filename" in APT
E: Sub-process /usr/bin/dpkg returned an error code (2)
How to fix "Sub-process /usr/bin/dpkg returned an error code (2)" in APT
dpkg-divert: error: rename involves overwriting 'path' with different file
How to fix dpkg-divert rename conflicts in APT
E: Sub-process /usr/bin/dpkg returned an error code (1) during kernel installation
How to fix "dpkg returned an error code (1)" in APT kernel installation
dpkg: dependency problems prevent configuration of triggers
dpkg: dependency problems prevent configuration of triggers in apt