package libc6 2.17-0ubuntu5.1 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1

[Dale F. Victor]

When I try to upgrade it used to say that it could not perform task because there was a libc6 2.7 in a directory it was not supposed to be in. I removed it and tried again. Said I had to remove the -new version of the file, did so and still had the problem. Went to Synaptic and used this to remove all the broken files all 240 of them. Did this and then ran apt-get update and upgrade and the problem apparently is still not fixed. I do not know how the glib file is getting placed into the improper directory.

Thanks for your time and effort.

Dale F. Victor

ProblemType: Package
DistroRelease: Ubuntu 13.04
Package: libc6 2.17-0ubuntu5.1
ProcVersionSignature: Ubuntu 3.8.0-33.48-generic 3.8.13.11
Uname: Linux 3.8.0-33-generic x86_64
ApportVersion: 2.9.2-0ubuntu8.5
Architecture: amd64
Date: Tue Nov 12 20:25:28 2013
DuplicateSignature: package:libc6:2.17-0ubuntu5.1:subprocess new pre-installation script returned error exit status 1
ErrorMessage: subprocess new pre-installation script returned error exit status 1
InstallationDate: Installed on 2012-05-26 (535 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MarkForUpload: True
SourcePackage: eglibc
Title: package libc6 2.17-0ubuntu5.1 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1
UpgradeStatus: Upgraded to raring on 2013-04-28 (199 days ago)

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your dmesg attachment in this bug report it seems that there is a problem with your hardware. I recommend performing a back up and then investigating the situation. Measures you might take include checking cable connections and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck!

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]