apt-get dist-upgrade falied with a dbus trigger loop due to an unconfigured library (libexpat1)

Bug #1485970 reported by Andy Whitcroft
28
This bug affects 8 people
Affects Status Importance Assigned to Milestone
dbus (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

While attempting to upgrade from before the gcc-5 transition to after it apt-get dist-upgrade exploded in the middle. It was attempting to handle dbus triggers but was unable to do so due to an unconfigured library, leading to a loop attempting to run the triggers and to the install failing in the middle:

  $ sudo apt-get dist-upgrade
  [...]
  Preparing to unpack .../libexpat1_2.1.0-7_amd64.deb ...
  De-configuring libexpat1:i386 (2.1.0-6ubuntu1) ...
  Unpacking libexpat1:amd64 (2.1.0-7) over (2.1.0-6ubuntu1) ...
  Preparing to unpack .../libexpat1_2.1.0-7_i386.deb ...
  Unpacking libexpat1:i386 (2.1.0-7) over (2.1.0-6ubuntu1) ...
  [...]
  Preparing to unpack .../systemd-sysv_224-1ubuntu3_amd64.deb ...
  Unpacking systemd-sysv (224-1ubuntu3) over (224-1ubuntu1) ...
  Processing triggers for man-db (2.7.0.2-5) ...
  dpkg: dependency problems prevent processing triggers for dbus:
   dbus depends on libexpat1 (>= 2.0.1); however:
    Package libexpat1:amd64 is not configured yet.

  dpkg: error processing package dbus (--configure):
   dependency problems - leaving triggers unprocessed
  dpkg: dependency problems prevent processing triggers for dbus:
   dbus depends on libexpat1 (>= 2.0.1); however:
    Package libexpat1:amd64 is not configured yet.
  [...]
  dpkg: too many errors, stopping
  Errors were encountered while processing:
   dbus
   dbus
  [...]
   dbus
   dbus
  Processing was halted because there were too many errors.

An apt-get install -f was unable to make progress from the resulting situation simply repeating the dbus trigger loop.

This was simply correctable (not simple to figure out, thank you cjwatson) by asking dpkg to configure libexpat1:

  $ sudo dpkg --configure libexpat1

From there a sudo apt-get install -f, and then a sudo apt-get install ubuntu-desktop^ (mine was a desktop install) sorted me out.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: apt 1.0.9.10ubuntu6
ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
Uname: Linux 4.1.0-3-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.18-0ubuntu7
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Aug 18 11:21:45 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-06-20 (788 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130618)
SourcePackage: apt
UpgradeStatus: Upgraded to wily on 2013-11-10 (645 days ago)

Revision history for this message
Andy Whitcroft (apw) wrote :
Revision history for this message
Andy Whitcroft (apw) wrote :

Attached is the full apt term log for the initial failure.

Revision history for this message
Andy Whitcroft (apw) wrote :

This may have been separatly reported against dbus under bug #1484841.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in apt (Ubuntu):
status: New → Confirmed
Revision history for this message
Iain Lane (laney) wrote :

I tried a test vivid → wily dist-upgrade in a chroot with ubuntu-desktop^ installed and it hit this issue.

Revision history for this message
dino99 (9d9) wrote :

Note:
- on Wily i386 this had not been met on my system
- but with amd64 install, this happen....... and seems dist-upgrade bypass the issue.

Revision history for this message
Adam Conrad (adconrad) wrote :

Changing the dbus triggers to interest-noawait before upgrade fixes this, but now I need to sort out how to do that in the past. :P

Adam Conrad (adconrad)
affects: apt (Ubuntu) → dbus (Ubuntu)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package dbus - 1.8.12-1ubuntu6

---------------
dbus (1.8.12-1ubuntu6) wily; urgency=medium

  * debian/dbus.triggers: Switch trigger to interest-noawait to make life
    slightly easier on dpkg/apt while dependency unwinding (LP: #1485970)

 -- Adam Conrad <email address hidden> Tue, 18 Aug 2015 12:37:46 -0600

Changed in dbus (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.