package rhythmbox couldn't be updated - dpkg: ../../src/packages.c:221: process_queue: Assert `dependtry <= 4' failed. (I

Bug #323313 reported by Xavi Miró
2
Affects Status Importance Assigned to Milestone
dpkg (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: rhythmbox

When accepting an automatic update of Ubuntu, the package rhythmbox couldn't be updated. A message appears on the screen, saying:
<<
E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem.
>>

When I do it, it says:
<<
Procesando activadores para menu ...
Procesando activadores para libc6 ...
ldconfig deferred processing now taking place
dpkg: ../../src/packages.c:221: process_queue: Assert `dependtry <= 4' failed. (I translated this from spanish)
>>

ProblemType: Package
Architecture: i386
DistroRelease: Ubuntu 8.10
ErrorMessage: el paquete rhythmbox ya está instalado y configurado
NonfreeKernelModules: nvidia
Package: rhythmbox 0.11.6svn20081008-0ubuntu4.3
SourcePackage: rhythmbox
Title: package rhythmbox 0.11.6svn20081008-0ubuntu4.3 failed to install/upgrade: el paquete rhythmbox ya está instalado y configurado
Uname: Linux 2.6.27-11-generic i686

Revision history for this message
Xavi Miró (xmirog) wrote :
Revision history for this message
Philip Muškovac (yofel) 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 262451, 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.

summary: - package rhythmbox couldn't be updated
+ package rhythmbox couldn't be updated - dpkg: ../../src/packages.c:221:
+ process_queue: Assert `dependtry <= 4' failed. (I
Changed in dpkg (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.