All Errors

Git's "could not create work tree dir: Permission denied" means it cannot create the clone target folder because your user lacks write access to the parent directory. Fix it by cloning to a directory you own.

Fix npm "access token expired or revoked" (E401) errors. Re-authenticate with npm login or replace the stale token in your .npmrc, and use OIDC trusted publishing in CI.

This error occurs when apt package metadata files become corrupted or fail to download properly. Rebuilding the package cache by removing corrupted files and running apt update resolves the issue in most cases.

The "Unable to locate package" error for i386 packages occurs when apt cannot find 32-bit packages because multiarch support is not enabled or repositories are architecture-restricted. Enable i386 architecture and verify your repository configuration to resolve this.

This error occurs when APT finds a dependency on a package that no longer exists in your repositories. The package may have been removed, renamed, or moved to a disabled repository.

This Git warning occurs when a short reference name (like 'feature') matches multiple refs, such as a branch and a tag with the same name. Use the full refname or remove the duplicate ref.

This error occurs when running dpkg without specifying an action flag like -i, -r, -P, or --configure. dpkg requires an explicit action to know whether you want to install, remove, purge, or configure a package.

The 'fatal: bad object HEAD' error means Git can't resolve the commit HEAD points to, usually from corruption, interrupted operations, or cloud-synced .git folders. Recovery is normally via fetch or ref repair.

This error occurs when APT cannot find a package in its configured repositories. Common causes include outdated package cache, typos in the package name, missing repositories, or unsupported package versions.

This error occurs when you try to install a virtual package that multiple real packages can provide, and apt cannot automatically choose which one you want. The solution is to explicitly select one of the concrete packages instead of the virtual package name.

The "Couldn't find any package by regex" error occurs when apt cannot locate a package because it doesn't exist in your repositories, the package name is misspelled, or you're using glob patterns incorrectly. Update your package lists, verify the exact package name, and ensure your repositories are properly configured to resolve this.

npm fails with code EAI_AGAIN when it can't resolve registry.npmjs.org via DNS. It's usually a transient or misconfigured DNS issue you fix by testing resolution and switching DNS servers.

This error occurs when the apt package manager cannot acquire the dpkg lock file because another package management operation is already in progress. The system's package manager can only run one operation at a time, and concurrent attempts will fail with this lock error.

This error occurs when you use an invalid option with apt or specify an option that is not compatible with the particular subcommand. Check your command spelling, option validity, and subcommand compatibility to resolve the issue.

This error occurs when attempting to run apt or dpkg commands without sufficient permissions. The /var/lib/dpkg/lock-frontend file requires root access. Using sudo, waiting for background updates, or checking for blocking processes resolves this issue.

The SFTP "Received message too long" error happens when shell startup files print text during login, corrupting the binary SFTP stream. The large number is those bytes read as a packet size.

APT cannot resolve package dependencies because required packages are unavailable, have version conflicts, or are held. This typically occurs with conflicting PPAs, version mismatches, or incompatible repositories.

apt treats "--install" as a package name instead of a command flag when placed after "apt". This is a syntax error caused by incorrect command ordering or quoting issues.

This error occurs when the package manager (apt or dpkg) is being used by another process, preventing new installations or updates. The system uses lock files to prevent simultaneous access that could corrupt the package database.

APT shows this warning when it cannot verify a repository's GPG signature, usually due to a missing, expired, or rotated signing key, or a wrong system clock. The repo is skipped until fixed.