kde-icons-mono line 354 name must be followed by :

[Wilson Morris]

Binary package hint: kde-icons-mono

Dpkg reports name not followed by colon in the form ':.
This halts upgrade to Jaunty.

ProblemType: Package
Architecture: i386
DistroRelease: Ubuntu 8.10
ErrorMessage: ErrorMessage: SystemError in cache.commit(): installArchives() failed

Package: update-manager 1:0.93.34
PackageArchitecture: all
SourcePackage: update-manager
Title: package update-manager 1:0.93.34 failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): installArchives() failed
Uname: Linux 2.6.27-14-generic i686

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we are unable to examine your VarLogDistupgrade log file as it is corrupted. Could you please manually add the log files in '/var/log/dist-upgrade' to this bug report? This will allow us to better determine what went wrong with this package installation.

[Wilson Morris (grem1999)]

Brian Murray wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. Unfortunately, we are unable to examine your
> VarLogDistupgrade log file as it is corrupted. Could you please
> manually add the log files in '/var/log/dist-upgrade' to this bug
> report? This will allow us to better determine what went wrong with
> this package installation.
>
> ** Changed in: kdeaccessibility (Ubuntu)
> Status: New => Incomplete
>
> ** Tags added: corrupt-varlogdistupgrade
>
>
Hi:
Could the corrupt files cause the problem rather than result from it?
I had formatted and started over. I could not reproduce the result;
however, during the attempt to recreate the porblem, I got a garbled
/boot/grub/menu.lst. Filesystem was jfs (I think). Installation media
Linux-format dvd-114 (8.10).

If I still have something of use, let me know.

Thanks,
Wilson

[Jonathan Thomas (echidnaman)]

What most likely happened here is that filesystem corruption corrupted both the log and the kde-icons-mono file. There's not much to do since we can't really know what caused the corruption, so I am closing this bug. Thanks for the report all the same.