I have the same problem on Kubuntu Gutsy, upgraded from Feisty. This
breaks Kubuntu quite severely, as you can't do any system admin through
the KDE tools at all - some sort of fix or workaround is essential if
I'm to carry on with Kubuntu.
Is this fixed in Hardy?
Any suggestions on a
I found quite a good workaround (gksudo kcontrol) that seems to fix the
DCOP server setup so that plain kcontrol works afterwards - not sure how
long the fix will last though.
See http://ubuntuforums.org/showthread.php?p=4977989#post4977989 for
more discussion, and link to another Launchpad bug
*** This bug is a duplicate of bug 175909 ***
https://bugs.launchpad.net/bugs/175909
I believe this is a dupe of 175909 - my gksudo workaround has persisted
across reboots, see https://bugs.launchpad.net/ubuntu/+source/kde-
systemsettings/+bug/175909 for details.
** This bug has been marked
That will hardly be fixed in gutsy, since this is more a kde bug than a kdesudo
one.
The issue is that for some reason, kcontrol/kcm modules are broken on new
accounts on some computers.
That's the famous kcontrol is empty bug.
There is not much we can do with kdesudo yet, since the user-root
Confiming bug in Kubuntu Gutsy, kdesudo version 1.1-0ubuntu2.2, version
1.1-0ubuntu2 works normally.
--
kdesudo --nonewdcop option breaks the system
https://bugs.launchpad.net/bugs/182403
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
