package libc6:amd64 2.23-0ubuntu4 failed to install/upgrade: package libc6:amd64 is not ready for configuration cannot configure (current status 'half-installed')

Bug #1638945 reported by mike motley on 2016-11-03
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
glibc (Ubuntu)
Undecided
Unassigned

Bug Description

appears every time I start up

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libc6:amd64 2.23-0ubuntu4
ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
Uname: Linux 4.4.0-45-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Thu Oct 27 16:33:50 2016
Dependencies:
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu4
 libgcc1 1:6.0.1-0ubuntu1
DpkgTerminalLog:
 dpkg: error processing package libc6:amd64 (--configure):
  package libc6:amd64 is not ready for configuration
  cannot configure (current status 'half-installed')
ErrorMessage: package libc6:amd64 is not ready for configuration cannot configure (current status 'half-installed')
InstallationDate: Installed on 2016-09-23 (40 days ago)
InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt 1.2.12~ubuntu16.04.1
SourcePackage: glibc
Title: package libc6:amd64 2.23-0ubuntu4 failed to install/upgrade: package libc6:amd64 is not ready for configuration cannot configure (current status 'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)

mike motley (mot) wrote :
Ceiling Cat (ceilingcat-r) wrote :

This prevents the installation of g++, gcc-multilib, g++-multilib among others. gcc can still be installed but it can only generate binaries that don't depend on libc.

This bug does not seem to appear when a system is upgraded from lubuntu 14.04.

Launchpad Janitor (janitor) wrote :

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

Changed in glibc (Ubuntu):
status: New → Confirmed
Ceiling Cat (ceilingcat-r) wrote :

Shortly after installation, I went into update-manager->Settings->Updates and unselected everything except for "Important security updates". This seemed to be the cause of the problem I was observing (may not be the case for others). To fix, I selected "Recommended updates", ran apt-get update, and then unselected "Recommended updates".

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers