package gcc 4:4.8.2-1ubuntu6 failed to install/upgrade: subprocess new pre-installation script returned error exit status 127

Bug #1314524 reported by Thomas Emmrich
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu
Expired
Undecided
Unassigned

Bug Description

Ubuntu 14-04 LTS
pkgname not found
tried to update
failed

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: gcc 4:4.8.2-1ubuntu6
ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5
Uname: Linux 3.11.0-19-generic i686
ApportVersion: 2.14.1-0ubuntu3
Architecture: i386
Date: Wed Apr 30 11:18:22 2014
Df:

Dmesg:

DuplicateSignature: package:gcc:4:4.8.2-1ubuntu6:subprocess new pre-installation script returned error exit status 127
ErrorMessage: subprocess new pre-installation script returned error exit status 127
InstallationDate: Installed on 2013-06-21 (313 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
SourcePackage: gcc-defaults
Title: package gcc 4:4.8.2-1ubuntu6 failed to install/upgrade: subprocess new pre-installation script returned error exit status 127
UpgradeStatus: Upgraded to trusty on 2014-04-30 (0 days ago)

Revision history for this message
Thomas Emmrich (thomas-emmrich) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Matthias Klose (doko) wrote :

Not a GCC error, but likely a corrupted file system

Preparing to unpack .../gcc_4%3a4.8.2-1ubuntu6_i386.deb ...
/bin/sh: error while loading shared libraries: libc.so.6: failed to map segment from shared object: Cannot allocate memory
dpkg: error processing archive /var/cache/apt/archives/gcc_4%3a4.8.2-1ubuntu6_i386.deb (--unpack):
 subprocess new pre-installation script returned error exit status 127

affects: gcc-defaults (Ubuntu) → ubuntu
Revision history for this message
Paul White (paulw2u) wrote :

We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time.

Presumably this problem was a one time occurrence and/or is no longer an issue? Can the bug report now be closed? If we do not hear from you the bug report will close itself in approximately 60 days time.

Thank you again for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]

Changed in ubuntu:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in 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.