debconf failed to upgrade: exit status 128 - Use of uninitialized value $reply in scalar chomp at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66

Bug #441248 reported by capput
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
debconf (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: debconf

Fresh install of 9.10 (64 bit). When updating for the first time debconf caused system to detect a crash report.

ProblemType: Package
Architecture: amd64
Date: Sat Oct 3 02:58:12 2009
DistroRelease: Ubuntu 9.10
ErrorMessage: subprocess installed post-installation script returned error exit status 128
Package: debconf 1.5.27ubuntu2
PackageArchitecture: all
ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
SourcePackage: debconf
Title: package debconf 1.5.27ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
Uname: Linux 2.6.31-11-generic x86_64

Revision history for this message
capput (capput) wrote :
Revision history for this message
capput (capput) wrote :

I should also mention this was the beta.

summary: - crash report generated when attempting to update first time. Failed
- when "Configuring debconf".
+ debconf failed to upgrade: exit status 128 - Use of uninitialized value
+ $reply in scalar chomp at
+ /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

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.

Changed in debconf (Ubuntu):
status: New → Confirmed
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.