Ubuntu
openttd package

package openttd 0.7.1-1 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 128

Bug #496741 reported by Joachim R. on 2009-12-14

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 9 people

Affects		Status	Importance	Assigned to	Milestone
	openttd (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

Binary package hint: openttd

While installing openttd I got a warning saying I must have the original "Transport Tycoon" files. I clicked 1 time on "next" button and 3 times on "cancel". Each time the warning re-poped, except the last one where I got an error code 128 and an apport notification about this installer.

ProblemType: Package
Architecture: amd64
Date: Mon Dec 14 23:25:11 2009
DistroRelease: Ubuntu 9.10
ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 128
NonfreeKernelModules: nvidia
Package: openttd 0.7.1-1
ProcVersionSignature: Ubuntu 2.6.31-16.53-generic
SourcePackage: openttd
Title: package openttd 0.7.1-1 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 128
Uname: Linux 2.6.31-16-generic x86_64

Tags:

Revision history for this message

Joachim R. (jro) wrote on 2009-12-14:

Dependencies.txt Edit (1.5 KiB, text/plain; charset="utf-8")
Dmesg.txt Edit (50.3 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (61.5 KiB, text/plain; charset="utf-8")

Revision history for this message

Jean-Baptiste Lallement (jibel) wrote on 2010-03-06:

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.