How to fix dpkg: triggers pending, packages not yet configured in APT

APTBEGINNERMEDIUMUpdated Dec 29, 2025· 261 views

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.

Quick fix

Fixes dpkg: triggers pending, packages not yet configured

sudo dpkg --configure -a
  1. Configure pending packages
  2. Fix broken dependencies
  3. Process triggers explicitly
  4. Update and upgrade packages
apt — error
sudo dpkg --configure -a
dpkg: triggers pending, packages not yet configured

What this error means

The "dpkg: triggers pending, packages not yet configured" error indicates that your Debian/Ubuntu package management system is in an incomplete state. This happens when: 1. **Triggers are pending**: dpkg has recorded trigger events that packages are interested in, but those triggers haven't been processed yet. Triggers are hooks that one package uses to notify other packages about state changes (e.g., updating font caches, rebuilding menus). 2. **Packages not configured**: Some packages have been unpacked (files extracted) but the configuration scripts that complete the installation haven't run yet. This error usually appears after interrupted package operations like: - Killing apt or dpkg process (Ctrl+C during install) - Power failure or system crash during updates - Disk space issues causing installation to fail midway - Network disconnection during large package downloads - Resource exhaustion during package configuration The system is essentially stuck in a transitional state and needs to resume the configuration process.

Typical symptoms

  • Error message appears during apt-get update, apt-get upgrade, or apt-get install
  • System package manager (apt, apt-get, aptitude) refuses to install or upgrade packages
  • Updates or installations fail without proceeding
  • Running any apt command hangs or fails with trigger error
  • dpkg --configure -a command shows packages in incomplete state
  • Graphical package managers (Software Center, Synaptic) fail to open or update
  • System updates prompt you to fix broken packages

Common causes

  1. apt or dpkg process was interrupted or killed during package installation
  2. Power failure or system crash during package updates
  3. Disk space ran out during package installation
  4. Network connection dropped during large package downloads
  5. Multiple apt processes running simultaneously
  6. Manual editing or corruption of /var/lib/dpkg/status file
  7. Previous installation attempt left the system in an incomplete state

How to fix "dpkg: triggers pending, packages not yet configured"

1Configure pending packages

The most direct fix is to tell dpkg to finish configuring all pending packages:

bash
sudo dpkg --configure -a

This command will:
1. Resume configuration of all packages that were unpacked but not configured
2. Process all pending triggers
3. Restore the system to a consistent state

If this completes without errors, your system is fixed. If it shows errors, proceed to the next steps.

2Fix broken dependencies

After configuring pending packages, fix any broken dependencies:

bash
sudo apt-get install -f

The -f flag means "fix broken" and will:
1. Identify packages with unmet dependencies
2. Attempt to install missing dependencies
3. Remove incompatible packages if necessary

This often resolves issues caused by interrupted package operations.

3Process triggers explicitly

If packages are specifically stuck on triggers, process them explicitly:

bash
sudo dpkg --triggers-only -a

This tells dpkg to:
1. Run all pending trigger handlers
2. Update caches, indexes, and system configurations that depend on trigger events
3. Not process package unpacking or configuration (triggers only)

Then configure any remaining packages:

bash
sudo dpkg --configure -a
4Update and upgrade packages

Once the system is in a consistent state, update the package lists and any pending upgrades:

bash
sudo apt-get update
sudo apt-get upgrade

This ensures:
1. Package lists are refreshed from repositories
2. Any packages left in an intermediate state are properly updated
3. Security updates are applied

5If problems persist: use apt-get --fix-broken

If the above steps don't work, use apt-get's built-in recovery:

bash
sudo apt-get --fix-broken install

This is stronger than apt-get install -f and will:
1. Remove conflicting packages if necessary
2. Install missing dependencies
3. Complete interrupted configuration

You may be prompted to remove packages. Review the list and proceed if it makes sense for your system.

Alternatively, try the newer apt command:

bash
sudo apt install --fix-broken
6Check disk space

Verify you have enough disk space, as full disks can cause installation to fail:

bash
df -h

# Check specifically /var partition (where dpkg database lives)
df -h /var

# Check /tmp
df -h /tmp

If /var is near capacity, clean up:

bash
# Remove cached packages
sudo apt-get clean

# Remove cache of downloaded .deb files
sudo apt-get autoclean

# Remove packages no longer needed
sudo apt-get autoremove

Then retry the fix:

bash
sudo dpkg --configure -a
7For stubborn cases: manually fix dpkg status

If the system is still stuck, you may need to manually intervene with the dpkg database. This is a last resort - proceed carefully:

bash
# Backup the current status file
sudo cp /var/lib/dpkg/status /var/lib/dpkg/status.backup

# Remove lock files that might be stale
sudo rm /var/lib/apt/lists/lock
sudo rm /var/cache/apt/archives/lock
sudo rm /var/lib/dpkg/lock*

# Try to reconfigure again
sudo dpkg --configure -a

If you accidentally corrupted the status file:

bash
# Restore from backup
sudo cp /var/lib/dpkg/status.backup /var/lib/dpkg/status

# Update dpkg database
sudo dpkg --configure -a

For more serious corruption, you may need to check if there's an older backup:

bash
ls -la /var/lib/dpkg/status*
sudo cp /var/lib/dpkg/status.old /var/lib/dpkg/status
8Verify the fix

After applying fixes, verify the system is back to normal:

bash
# Check dpkg status - should show no errors
sudo dpkg -l | head -20

# Try installing a test package
sudo apt-get install -y curl

# Or just update
sudo apt-get update

# Check for any remaining broken packages
sudo apt-get check

If these commands succeed without trigger or configuration errors, your system is fixed.

For package managers:

bash
# If using Synaptic or GNOME Software, try refreshing now
# Or use aptitude
sudo aptitude update

Advanced notes

Understanding dpkg Triggers

Triggers are a facility in Debian/Ubuntu package management that allow packages to defer expensive operations until batched together. For example:

- When you install fonts, a trigger notifies font-related packages to rebuild caches
- When you install man pages, the man-db package trigger rebuilds the manual database
- When you install shared libraries, the libc-bin package trigger regenerates the ld cache

Instead of running these expensive operations for each package, dpkg batches triggers and processes them once. This is why you see messages like "Processing triggers for libc-bin..."

Trigger States in dpkg

Packages can be in several states during trigger processing:

- triggered: A trigger event has been noted for this package
- triggers-awaited: The package has declared interest in a trigger and is waiting for it to be processed
- triggers-pending: The package still has unprocessed triggers

When you see "packages not yet configured," it means some packages are in these transitional states.

Common Causes by Scenario

1. After system crash/power loss: dpkg was in the middle of trigger processing. Recovery is usually simple.
2. After Ctrl+C during apt-get: The worst case - you may have multiple packages in inconsistent states.
3. Disk space exhaustion: If dpkg runs out of space, it may leave files partially written.
4. Network issues during large upgrades: If the download aborted, packages may be partially unpacked.

Why This Matters

Don't ignore this error. An incomplete package installation can lead to:
- Missing libraries and broken applications
- Security vulnerabilities if security patches aren't fully installed
- Cascade failures in dependent packages
- Inability to install new software

Prevention

To avoid this error:
1. Avoid interrupting apt/dpkg operations - let them complete
2. Ensure adequate disk space before large upgrades (df -h)
3. Use a UPS if you're on a laptop or unreliable power
4. Run updates in a stable environment, not in moving containers
5. For servers, use automatic snapshots before major upgrades

When to Seek Help

If dpkg --configure -a still fails after trying the steps above:
1. Check the specific error messages - they often indicate which package is problematic
2. Try removing the problematic package and reinstalling it
3. Check system logs: sudo journalctl -xe or sudo tail /var/log/apt/term.log
4. Consider seeking help on Ubuntu Forums or Ask Ubuntu with the full error output

Relation to APT

APT (Advanced Package Tool) is a higher-level tool built on top of dpkg. When you run apt-get, it:
1. Resolves dependencies
2. Downloads packages
3. Calls dpkg to unpack and configure them

If APT is interrupted, dpkg may be left with triggers pending.

Frequently asked questions

What does "dpkg: triggers pending, packages not yet configured" mean?
The "dpkg: triggers pending, packages not yet configured" error indicates that your Debian/Ubuntu package management system is in an incomplete state. This happens when: 1. Triggers are pending: dpkg has recorded trigger events that packages are interested in, but those triggers haven't been processed yet.
How do I fix "dpkg: triggers pending, packages not yet configured"?
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.
What causes "dpkg: triggers pending, packages not yet configured"?
apt or dpkg process was interrupted or killed during package installation Power failure or system crash during package updates Disk space ran out during package installation
Is the "dpkg: triggers pending, packages not yet configured" error serious?
It is a medium-severity error — more of a blocker than a risk. The steps above resolve it.

Official resources & further reading