Ubuntu
virtuoso-opensource package

package libvirtodbc0 6.1.2 dfsg1-1ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

Bug #815003 reported by marcolxpt on 2011-07-23

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

Bug Description

i don't know what happened, i've just send the error report as asked

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: libvirtodbc0 6.1.2+dfsg1-1ubuntu4
ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7
Uname: Linux 2.6.38-10-generic i686
Architecture: i386
Date: Sat Jul 23 09:35:55 2011
ErrorMessage: subprocess installed post-installation script returned error exit status 128
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
SourcePackage: virtuoso-opensource
Title: package libvirtodbc0 6.1.2+dfsg1-1ubuntu4 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

marcolxpt (marcolxpt) wrote on 2011-07-23:

AptOrdering.txt Edit (4.3 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (753 bytes, text/plain; charset="utf-8")
Df.txt Edit (523 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (123.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.