Ubuntu
elmerfem package

package elmer 5.5.0.svn.4262.dfsg-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

Bug #629979 reported by Balaji on 2010-09-04

This bug report is a duplicate of: Bug #442941: debconf failed to upgrade from 1.5.27ubuntu1 to 1.5.27ubuntu2: exit status 128 - Use of uninitialized value $reply in scalar chomp at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	elmerfem (Ubuntu)	New	Undecided	Unassigned

Bug Description

Crashed while installing.

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: elmer 5.5.0.svn.4262.dfsg-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-24.42-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic i686
Architecture: i386
Date: Fri Sep 3 22:45:39 2010
ErrorMessage: subprocess installed post-installation script returned error exit status 128
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
SourcePackage: elmerfem
Title: package elmer 5.5.0.svn.4262.dfsg-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

Tags:

Revision history for this message

Balaji (balaji-ramasubramanian) wrote on 2010-09-04:

AptOrdering.txt Edit (1.5 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (3.3 KiB, text/plain; charset="utf-8")
Df.txt Edit (450 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (49.2 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (207.2 KiB, text/plain; charset="utf-8")

Revision history for this message

Brian Murray (brian-murray) wrote on 2011-08-23:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 442941, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.