KPackageKit fails to recover from a dpkg interruption

Bug #483788 reported by Huynh Huu, Long on 2009-11-16
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kpackagekit (Ubuntu)

Bug Description

Binary package hint: kpackagekit

In case of an dpkg-interruption KPackageKit tells me about a different packagemanager already running, which is not the case -- error messages should at least point to the correct problem, if at all. Therefore I could not fix this problem via the GUI, which forced me to switch to the command line.
There was no lock file in /var/lock to be seen, "sudo aptitude update" gave:

$ sudo aptitude update
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.

After following this instruction I could use KPackageKit for updating packages again. Please consider handling this case within a userfriendly dialog, thanks!

kpackagekit version: 0.4.2-0ubuntu3 (according to dpkg.log the version didn't change during the above procedure)
on Ubuntu 9.10

Philip Muškovac (yofel) wrote :

Confirmed by killing the dpkg process whle removing a package. Kpackagekit only complains about not being able to get the excusive lock on the database without any suggestion on how to fix this.

Changed in kpackagekit (Ubuntu):
status: New → Confirmed
Philip Muškovac (yofel) wrote :

I have reported this bug to the KPackageKit developers. You can follow it at . Please report any other bugs you may find!

Philip Muškovac (yofel) on 2010-01-15
Changed in kpackagekit (Ubuntu):
status: Confirmed → Invalid
Changed in kpackagekit:
status: Unknown → Invalid
Changed in kpackagekit:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.