package libsystemd0:amd64 229-4ubuntu6 failed to install/upgrade: Paket libsystemd0:amd64 kann nicht konfiguriert werden, da libsystemd0:i386 nicht bereit ist (aktueller Status »half-installed«)

Bug #1585710 reported by Chuck-kensy
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apt (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Error occurred while apt upgrade

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libsystemd0:amd64 229-4ubuntu6
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
AptOrdering:
 libsystemd0: Configure
 libsystemd0: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Wed May 25 18:33:53 2016
ErrorMessage: Paket libsystemd0:amd64 kann nicht konfiguriert werden, da libsystemd0:i386 nicht bereit ist (aktueller Status »half-installed«)
InstallationDate: Installed on 2016-04-29 (26 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt 1.2.10ubuntu1
SourcePackage: systemd
Title: package libsystemd0:amd64 229-4ubuntu6 failed to install/upgrade: Paket libsystemd0:amd64 kann nicht konfiguriert werden, da libsystemd0:i386 nicht bereit ist (aktueller Status »half-installed«)
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Chuck-kensy (chuck-kensy) wrote :
Revision history for this message
Martin Pitt (pitti) wrote :

This is a bug in apt, not systemd. I'm not sure how to debug this, though. Julien, Michael, any idea?

affects: systemd (Ubuntu) → apt (Ubuntu)
Revision history for this message
Julian Andres Klode (juliank) wrote :

I think the bug submitter just broke his system, the log just started with the error message; and it was perfectly fine in the previous run, just look a few lines above and you see:

Setting up libsystemd0:amd64 (229-4ubuntu6) ...
Setting up libsystemd0:i386 (229-4ubuntu6) ...
Setting up systemd (229-4ubuntu6) ...

So, without further input, I can't say anything about this.

Furthermore, apt's history log only shows the command and what started it, but does not get any further.

It would be a good idea to get the dpkg.log file, that contains the actual dpkg logs (status changes, etc). Then we can see when it broke, but it does not look like apt broke it.

Changed in apt (Ubuntu):
status: New → Incomplete
Revision history for this message
Chuck-kensy (chuck-kensy) wrote :

I guess I will need to reinstall it.

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

[Expired for apt (Ubuntu) because there has been no activity for 60 days.]

Changed in apt (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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