maybeway36 wrote:
> Seems like a different issue, all right. I don't use NFS, and it works
> fine here.
I thought the same, but maybe we are wrong.
Here's why:
gogh wrote:
> I have exactly the same behavior as wateenellende here.
> kdesu version 1.1-0ubuntu2.2 doesn't fix it.
Brian Buchanan wrote:
> I set no_root_squash on the export, remounted and my problem was solved.
gogh wrote:
> I confirm that I have the same no_root_squash behaviour.
However:
Frode M. Døving wrote:
> The current version of kdesudo in gutsy and hardy does not need root-write access to $HOME.
But if that is the case, why would root need write-access (through "no_root_squash") on $HOME to be able to connect to X ?
My guess (and only explanation) is that kdesu version 1.1-0ubuntu2.2 is still trying to write to $HOME to handle the connection to X.
So, a) it seems at least related to this bug; (and we can't "unduplicate" anyway); b) kdesu version 1.1-0ubuntu2.2 needs another fix.
maybeway36 wrote:
> Seems like a different issue, all right. I don't use NFS, and it works
> fine here.
I thought the same, but maybe we are wrong.
Here's why:
gogh wrote:
> I have exactly the same behavior as wateenellende here.
> kdesu version 1.1-0ubuntu2.2 doesn't fix it.
Brian Buchanan wrote:
> I set no_root_squash on the export, remounted and my problem was solved.
gogh wrote:
> I confirm that I have the same no_root_squash behaviour.
However:
Frode M. Døving wrote:
> The current version of kdesudo in gutsy and hardy does not need root-write access to $HOME.
But if that is the case, why would root need write-access (through "no_root_squash") on $HOME to be able to connect to X ?
My guess (and only explanation) is that kdesu version 1.1-0ubuntu2.2 is still trying to write to $HOME to handle the connection to X.
So, a) it seems at least related to this bug; (and we can't "unduplicate" anyway); b) kdesu version 1.1-0ubuntu2.2 needs another fix.