All Errors

This error occurs when APT encounters invalid syntax in the /etc/apt/preferences file. The preferences file must follow strict formatting rules with required Package, Pin, and Pin-Priority headers separated by blank lines.

The dpkg package manager gets stuck in a loop while processing package triggers, usually due to corrupted state or conflicting package dependencies. This error halts system updates and package installation.

APT ignores files in /etc/apt/sources.list.d/ that don't have valid extensions (.list or .sources). This happens when backup files, disabled sources, or files with wrong extensions are placed in the directory.

This warning appears when an APT repository's metadata (InRelease file) reports a different distribution codename than what your sources.list expects. This typically happens after system upgrades or when third-party repositories are misconfigured.

This error occurs when apt cannot resolve the domain name for package repositories due to DNS configuration issues or network connectivity problems. Common causes include missing DNS servers, network interface misconfiguration, or systemd-resolved service issues.

This error occurs when trying to remove a foreign architecture (like i386) from dpkg while packages from that architecture are still installed. You must uninstall all packages from the target architecture before removing it.

This error occurs when apt attempts to upgrade a package marked as held while using -y (automatic yes), but the --allow-change-held-packages flag was not provided. Held packages are protected from automatic changes to prevent dependency conflicts.

This error occurs when apt cannot access a repository due to HTTP 403 access restrictions. Common causes include deprecated PPAs, repository configuration mismatches, or network issues.

This error occurs when the dpkg package manager encounters a failure during installation, removal, or configuration of packages. It's usually caused by interrupted installations, broken dependencies, or corrupted package databases.

When you remove packages from Debian/Ubuntu systems, their dependencies may become orphaned. APT warns you about these unused packages that can be safely removed to free up disk space.

The "Repository changed its Label value" notification appears when apt detects that a package repository has modified its metadata, such as its Label, Origin, or Suite fields. This is a security feature that requires explicit acknowledgment. You can resolve this by running apt update with the --allow-releaseinfo-change flag to approve the changes.

The "dpkg: error processing triggers for man-db" error occurs when the manual page database update fails during package installation or configuration. This can be fixed by reconfiguring the dpkg system or disabling automatic man-db updates.

This error occurs when a package's pre-removal script (prerm) fails during package removal or upgrade. It's typically caused by missing services, corrupted scripts, or database issues. Can usually be fixed by cleaning package cache, configuring dpkg, or forcefully removing the problematic package.

This error occurs when two different packages contain the same file, preventing installation. Resolve it by removing conflicting packages, using force options carefully, or fixing the underlying package conflict.

This error occurs when apt's HTTPS method crashes during package updates, usually due to CPU instruction incompatibility or corrupted binaries. Set GNUTLS_CPUID_OVERRIDE=0x1 or reinstall apt-transport-https to fix it.

This security notification appears when a package repository changes its Origin metadata. It requires explicit user acknowledgment before package updates can proceed. Learn how to safely accept these changes.

The dpkg package manager is reporting too many errors during installation or upgrades and has halted processing. This typically indicates a corrupted package database or interrupted installation that needs database reconfiguration.

This error occurs when dpkg cannot create backup copies of files before updating packages, typically due to filesystem limitations or file attribute restrictions. It usually affects /boot with FAT32 EFI partitions or files with immutable flags set.

This error occurs when apt finds a package mentioned as a dependency but can't locate it in any enabled repository. Usually fixed by updating package lists, checking repository configuration, or fixing broken dependencies.

This error occurs when the dpkg package manager fails to process systemd triggers during package configuration or installation. It typically indicates corrupted dpkg state, broken dependencies, or pending packages that need configuration. This can block all package operations until resolved.