dpkg: ../../src/packages.c:221: process_queue: Assertion `dependtry <= 4' failed

[Rajinder Sandhu, Bangalore]

Binary package hint: update-manager

When ever I want to do upgrade or install anything crash report is generated by Apport which is being attached with this file.
Thanks

ProblemType: Package
Architecture: i386
DistroRelease: Ubuntu 8.10
ErrorMessage: ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg exited unexpectedly

NonfreeKernelModules: nvidia
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(): E:Sub-process /usr/bin/dpkg exited unexpectedly
Uname: Linux 2.6.27-9-generic i686

[Jean-Baptiste Lallement (jibel)]

This is because of bug 305763 that you've reported earlier and the bug we've marked duplicate of it.

One solution might be to try to reinstall the package:
sudo apt-get install --reinstall hal-info

But if this doesn't work then remove the package and reinstall it (do it at your own risk):
sudo apt-get clean
sudo apt-get update
sudo dpkg -r --force-depends hal-info
sudo apt-get install hal-info

[Rajinder Sandhu, Bangalore (sandy744-breakthru)]

The bug was fixed by unistalling the package hal, hal-info and libmbca0 (this file was reported by dpkg) and then reinstalling them
The process went like this:
sudo dpkg -r hal hal-info
and if any other file is showing error add that file also, then
sudo aptitude reinstall

This has fixed the problem
Thanks all
Rajinder Sandhu

[Rajinder Sandhu, Bangalore (sandy744-breakthru)]

The bug was fixed by unistalling the package hal, hal-info and libmbca0 (this file was reported by dpkg) and then reinstalling them
The process went like this:
sudo dpkg -r hal hal-info
and if any other file is showing error add that file also, then
sudo aptitude reinstall

This has fixed the problem
now run
sudo dpkg --configure -a

Thanks all
Rajinder Sandhu

[Jean-Baptiste Lallement (jibel)]

I'm glad that the workaround fixed your problem. I'm marking this report as dup of bug 279709