KDESudo segfault, my solution

[barbolani]

Just finished the 9.04->9.10 upgrade and had to face the "kdesudo crash" issue that is being reported during the upgrade. What happened to me more or less fits the description of the rest of the people. Upgrade started, downloaded packages and started to do its thing.

And at some point I got the window saying that kdesudo had crashed. The upgrade window was frozen and there was no machine activity. This is what I did:

1- Forced closing of the upgrade window.
2- Open a konsole, run sudo ps xa and kill all upgrade related process (look for phyton or dpkg in the command line or anything related to package management) The sad part is that I did not took note of what I killed.
3- Did sudo apt-get dist-ugprade. Got an error message saying that things were not consistent. Executed sudo dpkg --configure -a. Waited while it did its thing and had to decide for configuration files changed. After this finished, rebooted.

I'm writing this from my upgraded KUbuntu, so for some people this advice could work.

[bag]

Re: KDESudo segfault, my solution

This is a great post - I just wish it had been available before I tried my upgrade!!!

It may well help out a whole bunch of people...!

Thanks barbolani.

Bag.

[kjjjjshab]

Re: KDESudo segfault, my solution

I think it is a bit insane that there is no mention of this on kubuntu.org or in the release notes... this is hitting quite a few people...

Thanks for the post.

[tnorris]

Re: KDESudo segfault, my solution

I upgraded to KK when the Beta came out and had this problem. Unfortunately, at the time, I couldn't find anything about it happening to anyone else. I looked at it as an <sarcasm>opportunity</sarcasm> to clean up my install after I had been upgrading it over and over again since Dapper. Luckily just a few months before I had started taking nightly snapshots of my home directory on to a new NAS I bought.

Initially, after the upgrade, I couldn't get ANY kind of shell at all (not even a recovery shell). Booting would just crash half way (not even a kernel panic). It appeared to me to be a mismatch between the version of libc the kernel expected and the version that was ?still? installed because I got a symbol not found error in libc.so.