Bug 191124 - Crash of Kpackagekit while updating system. Reboot needed. Unable to achieve update.
Summary: Crash of Kpackagekit while updating system. Reboot needed. Unable to achieve ...
Status: RESOLVED NOT A BUG
Alias: None
Product: kpackagekit
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Steven M. Parrish
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-30 10:24 UTC by Grasyop
Modified: 2009-04-30 15:50 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Grasyop 2009-04-30 10:24:09 UTC
Version:            (using KDE 4.2.2)
OS:                Linux
Installed from:    Ubuntu Packages

The update notifier told me there were some updates available. I clicked on "apply all available updates". Update began, then crashed midway (frozen screen, I couldn't do anything but reboot the computer). Of course, I couldn't get any error message.

Now I try to apply the updates again, but it tells me that: "Cannot get the exclusive lock on the packaging backend.
Please close any other legacy packaging tools that may be open."
There's none! I've just rebooted!
Comment 1 Daniel Nicoletti 2009-04-30 14:25:53 UTC
Well, there are lot's of reasons why that happen, the one i believe that happened is that your dbus might got updated, and if you update dbus we lost connection with packagekit, and since PackageKit -> apt backend uses dbus, the apt backend stops. That's why Ubuntu should stop tagging experimental stuff as stable, and the reason i use debin and am creating a backend done in cpp so we don't lose connection.
If i were you i'd try doing as root aptitude safe-upgrade. If the lock problem still happens there try removing the lock file.
Comment 2 Grasyop 2009-04-30 15:18:48 UTC
It worked (sudo aptitude safe-upgrade), thank you!

I agree with you, Kubuntu shouldn't tag experimental stuff like this as stable. There are too many problems, it annoys me more and more.
May I ask you which Debian you use, stable or testing, and if you think Debian testing is more stable than Kubuntu?
Comment 3 Daniel Nicoletti 2009-04-30 15:50:28 UTC
Glad it worked :D
I use a mixture of testing/unstable/experimental, all tunned with apt pinning to always try to be testing. Imo Debian testing is even more stable that kubuntu since it is still using kde 3.5 :P, that's why i have also unstable to get kde4 which imo is still a bit unstable :D
I close this bug as invalid since it's apt backend fault.