Comment 52 for bug 155032

In that case, there must be something else wrong as well.

The kdesudo ubuntu2.2 did not work for me, programs could not connect to
the X server. If I recall correctly, issueing an "xhost +" would resolve
that.

Removing kdesudo and using kdesu instead worked for me.

Other people have reported that removing the option root_squash from the
NFS share made it work for them, but I am not root at the faculties main
file server, so I can't test that.

Frode M. Døving wrote:
> The current version of kdesudo in gutsy and hardy does not need root-write access to $HOME.
> The kdesudo version released in the first gutsy, did however start programs as root, but with the users environment variables.
> This evil and ugly bug told programs like adept, dolphin, konqueror and others,
> to save their configuration files to the users $HOME/.kde/ folder,
> even when the programs actually were running as the root user.
> The result is root-owned files in the users home directory once a program is executed with kdesudo.
> This issue is fixed in the ubuntu2.2 version in gutsy and in the hardy version.
>
> One should check the user home directory for root-ownership on configuration files, as that can be frustrating.
> Saving new configurations, bookmarks, settings etc. as the user might not work at all, if this is the case.
>