Upgrade problem

[aged hippy]

When upgrading from Kubuntu 7.10 to 8.10 on Sunday night/Monday morning, the download got stuck at configuring "en_AU-UTF-8".
I left it for some hours, then killed the upgrade.

Doing a depkg (booted from safe mode) resulted in the same error.

This has also been reported in the Kubuntu Forums this morning.

[aged hippy (malcolm-rogers)]

Edited to add:
I also find it impossible to upgrade via the Alternate install disk, it runs into problems when telling it to fetch updated packages as it goes, and it also has problems when i tell it i will update it later.

Fortunately it restores the system to the previous state. :)

[aged hippy (malcolm-rogers)]

This is the output from the console when upgrading from the Alternate Install cd, when i tell it that i will update the packages later:

>>>>>>
malcolm@hippy:~$ kdesu "/cdrom/cdromupgrade"
kbuildsycoca running...

adept_manager: no process killed

adept_updater: no process killed

kdecore (KProcess): WARNING: _attachPty() 12

gpgv:
Signature made Wed 02 Jul 2008 09:18:51 BST using DSA key ID FBB75451

gpgv:
Good signature from "Ubuntu CD Image Automatic Signing Key <email address hidden>"

Launched ok, pid = 6180

kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.8: undefined symbol: PKCS7_content_free

kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.8: undefined symbol: OpenSSL_add_all_algorithms

kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.8: undefined symbol: OPENSSL_add_all_algorithms

kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.8: undefined symbol: OpenSSL_add_all_algorithms_conf

can't load DistUpgradeViewGtk (No module named Common.SimpleGladeApp)
updateStatus: Reading cache
updateStatus: Checking package manager
updateStatus: Updating repository information
updateStatus: Checking package manager
updateStatus: Calculating the changes
updateStatus: Fetching
updateStatus: Restoring original system state
<<<<<<

And this is the message in the message in the 'details' of the installer:

>>>>>>
Failed to fetch cdrom:[Kubuntu 8.04.1 _Hardy Heron_ - Release i386 (20080702.1)]/pool/main/o/openoffice.org/python-uno_2.4.1-1ubuntu2_i386.deb Hash Sum mismatch
<<<<<<

[Michael Vogt (mvo)]

Thanks for your bugreport.

The failed to fetch message might be a bad CD burn, could you please check the CD for defects?

[aged hippy (malcolm-rogers)]

I'll do better than that, i'll re-download it tonight. :)

I burned that one with K3B at 4x and checked the burn, which was OK.

I will let you know how it goes.

Warmest Regards,
malcolm

Michael Vogt wrote:
> Thanks for your bugreport.
>
> The failed to fetch message might be a bad CD burn, could you please
> check the CD for defects?
>
> ** Changed in: update-manager (Ubuntu)
> Status: New => Incomplete
>
>

[aged hippy (malcolm-rogers)]

Well i re-downloaded the .iso, burned it at 4x, checked (validated?) it
and K3B reported success.

So i stuffed it in the CD drive, and did the kdesu
"/cdrom/cdromupgrade" thing.
It hung at precisely the same place:
Generating locales...
  en_AU.UTF-8...

It broke, and a dpkg from safe mode also failed at the same point, so i
re-installed again, updated completely, then tried what another Forum
member said worked for him: remove locales with Adept, then do the
upgrade, then re-install locales.

I don't doubt that it worked for him, but it didn't for me. :(
Generating locales...
  en_AU.UTF-8...

Three re-installs in 24 hours, five in 48.... i'm going for a record
here. :)

The entire output of the attempted upgrade is here if it's of any help:
http://www.agedhippy.plus.com/upgrade.txt

It seems that i'm fated to stick with Gutsy.

Warmest Regards,
malcolm

Michael Vogt wrote:
> Thanks for your bugreport.
>
> The failed to fetch message might be a bad CD burn, could you please
> check the CD for defects?
>
> ** Changed in: update-manager (Ubuntu)
> Status: New => Incomplete
>
>

[Duane Hinnen (duanedesign)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

[aged hippy (malcolm-rogers)]

No, it's not an issue now, i've been using Hardy for some time, and the installation was flawless.

I won't be going to install any later releases than Hardy as i'm perfectly happy with the 3.5.10 desktop, and find the 4.x desktop to be all gloss and glitter - meaning no disrespect to the developers.