All Errors

This error occurs when a package has a malformed version string containing spaces instead of a valid Debian version format. This typically happens when shell scripts use single quotes instead of backticks for command substitution, or when manually editing package files. The version field must follow Debian's strict format without any whitespace, or dpkg will reject the package.

This error occurs when apt-mark cannot modify a package's installation status due to dependency conflicts or package state issues. Resolving dependency conflicts or using apt-get fix-broken to repair broken dependencies resolves this issue.

This error occurs when dpkg attempts to ask about configuration file changes during package installation or upgrade in a non-interactive environment. Since stdin is empty or closed, the prompt cannot be answered and the operation fails.

This warning occurs when dpkg cannot find the .list file for an installed package in /var/lib/dpkg/info/. The issue typically happens after interrupted package installations or corrupted package metadata. Reinstalling the affected package or running package repair commands usually resolves it.

This error occurs when the Pin-Priority field in /etc/apt/preferences or /etc/apt/preferences.d/ contains an invalid value. Pin-Priority must be a positive or negative integer, and common causes include non-numeric values, missing the Pin-Priority keyword, or incorrect syntax formatting.

This warning appears when apt detects broken packages or corrupted cache files in your system. Fix it by running apt-get update, clearing corrupted cache, or removing duplicate repository entries from your sources.list.

This is a warning message, not an error, that appears during 'apt update' when your system is configured to look for 32-bit (i386) packages but a repository only provides 64-bit (amd64) packages. The update still succeeds, but you'll see warnings for repositories that don't support the i386 architecture.

This error occurs when apt cannot mark a package as manually installed, typically because the package is virtual, not installed, or has dependency issues. Virtual packages are references to other packages and cannot be directly marked as manually installed.

The 'dpkg: triggers pending, packages not yet configured' error occurs when package installations or upgrades were interrupted, leaving the system in an inconsistent state where some packages have unprocessed triggers or incomplete configuration. This typically happens after interrupted apt/dpkg operations, power failures, or killed processes during system updates.

The "Could not mark packages as held" error occurs when apt-mark fails to prevent a package from being automatically upgraded. This typically happens due to package state issues, dpkg database corruption, or administrative permission problems, and can be resolved by fixing package states, using alternative methods to hold packages, or clearing dpkg status.

The 'package conflicts with package' error occurs when dpkg detects that two packages cannot be installed simultaneously because they declare mutual conflicts. This typically happens when multiple versions, variants, or incompatible software provide the same functionality. Resolve this by removing the conflicting package first or using apt to resolve dependencies automatically.

This error occurs when dpkg cannot remove outdated package files due to insufficient permissions. The file or parent directory ownership/permissions prevent the deletion operation needed during package installation or upgrade.

This relocation error occurs when your apt package manager has library version mismatches, typically caused by mixing packages from different distributions or incomplete upgrades. The fix involves reinstalling apt and libapt-pkg packages to restore compatibility.

This error occurs when APT cannot authenticate to a package repository that requires credentials. Common causes include missing subscription credentials for enterprise repositories (like Proxmox), expired authentication tokens, or misconfigured repository URLs with invalid credentials.

The dpkg status area has become read-only, blocking package installations and updates. This usually means your filesystem encountered an error and was mounted in read-only mode for protection. Remounting it as read-write or fixing filesystem errors will resolve the issue.

This warning occurs when apt cannot establish a network connection to a package repository server. The repository server may be down, unreachable due to network issues, or your system's network configuration is blocking the connection.

This Perl warning occurs when system locale settings are not properly configured on Debian/Ubuntu systems. The warning appears when Perl detects that environment variables like LC_ALL, LANG, or LANGUAGE are unset or point to unsupported locales. It can be fixed by generating missing locales or setting appropriate environment variables.

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 /boot partition is full and cannot install new kernel updates. This occurs when old kernel versions accumulate and consume all available space. Free up space by removing old unused kernels.

This warning occurs when Perl cannot find the locale configuration specified in your environment variables. It typically appears when using apt or Perl scripts on systems where locale packages are not fully installed or configured.