© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
Base cause for me was actively setting the root password to be
different from the initial
user password requested by the install wizard. apt was still trying to
use a copy of the
initial password, so variations of sudo su -, plus command line
aptitude calls saved the
day.
I still believe strongly in keeping that root password different and
secure, so I just got
used to the penalty of doing my updates in CLI (which I like anyway)
-steve
On Sat, Jun 18, 2011 at 3:30 AM, Andrew Allcock <email address hidden> wrote:
> My report of this bug came from when I was using 11.04 Beta. This has
> not occurred to me in the full release but, if it helps, the full
> release is a dual-boot installation and upgraded from 10.10 whereas the
> beta release was an upgrade of a WUBI install.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (774286).
> https:/
>
> Title:
> 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/
>
> Status in “debconf” package in Ubuntu:
> Confirmed
> Status in “tzdata” package in Ubuntu:
> Confirmed
>
> Bug description:
> Binary package hint: debconf
>
> Failed to report to debconf during first upgrade after installation of
> 9.10 beta. Upgrade failed.
>
> ProblemType: Package
> Architecture: amd64
> Date: Mon Oct 5 09:54:06 2009
> DistroRelease: Ubuntu 9.10
> ErrorMessage: subprocess installed post-installation script returned error exit status 128
> NonfreeKernelMo
> Package: debconf 1.5.27ubuntu2
> PackageArchitec
> ProcVersionSign
> 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
>
> To manage notifications about this bug go to:
> https:/
>