Summary: | Crash of Kpackagekit while updating system. Reboot needed. Unable to achieve update. | ||
---|---|---|---|
Product: | [Frameworks and Libraries] kpackagekit | Reporter: | Grasyop <grasyop> |
Component: | general | Assignee: | Steven M. Parrish <smparrish> |
Status: | RESOLVED NOT A BUG | ||
Severity: | crash | CC: | dantti12 |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Grasyop
2009-04-30 10:24:09 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. 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? 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. |