Ubuntu
moodle package

package moodle 1.9.9.dfsg2-2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

Bug #816482 reported by Girish Mautadin on 2011-07-26

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
	moodle (Ubuntu)	New	Undecided	Unassigned

Bug Description

did not install..

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: moodle 1.9.9.dfsg2-2
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
Architecture: amd64
Date: Tue Jul 26 19:20:56 2011
ErrorMessage: subprocess installed post-installation script returned error exit status 128
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
PackageArchitecture: all
SourcePackage: moodle
Title: package moodle 1.9.9.dfsg2-2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

Girish Mautadin (coolmystic07) wrote on 2011-07-26:

AptOrdering.txt Edit (1.8 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (3.9 KiB, text/plain; charset="utf-8")
Df.txt Edit (652 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (70.6 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (17.9 KiB, text/plain; charset="utf-8")

Revision history for this message

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

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.