I suspect that in order to reproduce this bug I'd have to revert not only my system's configuration back before I encountered the problem but also any repositories that it was connecting to. Particularly, kpackage kit back to the one I was using on my computer and whichever version I was trying to install back up to the repositories.
Since the power cut I don't know how reliable the end of the log file is. I'm guessing it had a lot more trouble trying to install kpackagekit that simply didn't get written out before the power cut. Prehaps it was this deadlock that caused it? If you know a way to artificially recreate such a situation then you may be able to find out if that was what caused it. -- KPackageKit update caused immediate power down https://bugs.launchpad.net/bugs/372268 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kpackagekit in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
