How to fix E: Internal Error, No file name for package-name:amd64 in APT

APTINTERMEDIATEMEDIUMUpdated Oct 2, 2026· 541 views

This error occurs when apt fails to find or configure a package after a failed installation or interrupted process. It typically happens with multi-arch packages and can be resolved by clearing the package cache or purging and reinstalling the affected package.

Quick fix

Fixes E: Internal Error, No file name for package-name:amd64

sudo rm -rf /var/lib/apt/lists/*
sudo mkdir -p /var/lib/apt/lists/partial
sudo apt-get update
  1. Clear the apt package cache
  2. Configure any pending packages
  3. Purge and reinstall the problematic package
  4. Run full dependency fix if needed
apt — error
sudo rm -rf /var/lib/apt/lists/*
sudo mkdir -p /var/lib/apt/lists/partial
sudo apt-get update
E: Internal Error, No file name for package-name:amd64

What this error means

The "Internal Error, No file name for package:amd64" error indicates that the apt package manager has lost track of where a package file is located in its internal cache. This occurs when a package installation fails partway through (due to network issues, disk space, or interrupted updates), leaving the package database in an inconsistent state. The apt package manager then cannot locate the necessary package files to complete the installation or configuration process.

Typical symptoms

  • apt-get or apt commands fail with "E: Internal Error, No file name" messages
  • Attempting to install, upgrade, or configure packages results in this error
  • The error typically occurs with multi-arch packages (e.g., package-name:amd64)
  • Running apt-get -f install does not resolve the issue
  • Package manager appears stuck or unable to proceed with any operations

Common causes

  1. Failed or interrupted package installation from a previous update or install attempt
  2. Corrupted or incomplete package cache in /var/lib/apt/lists/
  3. Network interruption during apt-get update or install operations
  4. Mismatched package metadata between different repositories or architectures
  5. Power failure or system crash during package management operations
  6. Conflicting third-party repositories containing incompatible package versions

How to fix "E: Internal Error, No file name for package-name:amd64"

1Clear the apt package cache

The most common fix is to clean out the package list cache. Open a terminal and run:

bash
sudo rm -rf /var/lib/apt/lists/*
sudo mkdir -p /var/lib/apt/lists/partial
sudo apt-get update

This removes all cached package metadata and forces apt to download fresh lists from your configured repositories. The mkdir command recreates the partial directory where apt stores incomplete downloads.

2Configure any pending packages

After clearing the cache, configure any packages that may be left in an incomplete state:

bash
sudo dpkg --configure -a

This command attempts to finish configuring any packages that were interrupted. If you see errors about specific packages, note them for the next step.

3Purge and reinstall the problematic package

If the error persists and you know which package is causing the issue, completely remove and reinstall it:

bash
# Remove the package and its configuration files
sudo apt-get purge package-name

# Update package lists again
sudo apt-get update

# Reinstall the package fresh
sudo apt-get install package-name

Replace "package-name" with the actual package causing the error (e.g., "linux-firmware" or "libc6").

4Run full dependency fix if needed

If you still have broken dependencies, fix them with:

bash
sudo apt-get -f install

The -f flag tells apt to attempt to correct system with broken dependencies. After this, try your original command again:

bash
sudo apt-get update
sudo apt-get upgrade
5Check disk space and filesystem health

This error can also occur if your system is running out of disk space. Check available space:

bash
df -h

If you're low on disk space, delete unnecessary files or logs. Additionally, verify your filesystem is not corrupted:

bash
sudo fsck -n /dev/sdXX

Replace /dev/sdXX with your root partition (found from df -h output). The -n flag runs a read-only check without making changes.

Advanced notes

In rare cases where the error involves core system packages like libc6, you may need to manually download packages from Ubuntu/Debian repositories and use dpkg -i --force-all to reinstall them directly, bypassing the broken apt cache. Additionally, if you have third-party PPAs or custom repositories enabled, temporarily disable them and retry the fixes, as they may contain incompatible or conflicting packages. This error was historically more common with multi-arch systems (mixing 32-bit and 64-bit packages) but newer versions of apt have improved handling for this scenario.

Frequently asked questions

What does "E: Internal Error, No file name for package-name:amd64" mean?
The "Internal Error, No file name for package:amd64" error indicates that the apt package manager has lost track of where a package file is located in its internal cache. This occurs when a package installation fails partway through (due to network issues, disk space, or interrupted updates), leaving the package database in an inconsistent state. The apt package manager then cannot locate the necessary package files to complete the installation or configuration process.
How do I fix "E: Internal Error, No file name for package-name:amd64"?
This error occurs when apt fails to find or configure a package after a failed installation or interrupted process. It typically happens with multi-arch packages and can be resolved by clearing the package cache or purging and reinstalling the affected package.
What causes "E: Internal Error, No file name for package-name:amd64"?
Failed or interrupted package installation from a previous update or install attempt Corrupted or incomplete package cache in /var/lib/apt/lists/ Network interruption during apt-get update or install operations
Is the "E: Internal Error, No file name for package-name:amd64" error serious?
It is a medium-severity error — more of a blocker than a risk. The steps above resolve it.

Official resources & further reading