Comment 25 for bug 175909

I don't have the problem any more, at present, so I can't test it..... I did try kdesu and/or kdesudo on kcontrol before hitting on gksudo, and it didn't seem to clear things up at all. None of the other sudo options including plain 'sudo kcontrol' had the same effect of getting the DCOP connections cleared up. (Someone else on the Ubuntu forum link did find that restarting the DCOP server also did this.)

Interestingly, after a reboot I have found no need to repeat the 'gksudo kcontrol' - now I find that kcontrol launched from menus is OK, with the Administrator Mode button functioning. Also, after the reboot, I had only one dcopserver running:

$ ps aux| grep dcop
richard 6478 0.1 0.0 25840 3104 ? S 10:19 0:00 dcopserver [kdeinit] --nosid
richard 6643 0.0 0.0 2992 788 pts/1 S+ 10:19 0:00 grep dcop
$

My two KDE sessions on Gutsy were interspersed with long sessions on XP and Ubuntu Hardy (separate partition and using GNOME not KDE), so I think any sudo credentials must have expired by now (and they should be reset on boot anyway).

My workaround is not ideal, as gksudo may well not be installed on Kubuntu by default, and will probably pull in GNOME libraries, but I hope it helps in figuring out a better workaround or a fix.