Error: "/var/tmp/kdecache-privat" is owned by uid 1000 instead of uid 0.

[Tscheesy]

Binary package hint: kdesudo

when i run kdesudo kate in the konsole, i get:

privat@privat-laptop:~$ kdesudo kate
passprompt

Error: "/var/tmp/kdecache-privat" is owned by uid 1000 instead of uid 0.

Error: "/tmp/ksocket-privat" is owned by uid 1000 instead of uid 0.

QFile::open: No file name specified

( i exited without saving..)

[dlugidll (dlugilin)]

i confirm this bug, is the same 133358

[Wouter Horré (wouterh)]

I also see these error messages. I suspect kdesudo does not completely replace the KDE environment with an environment for root before calling sudo. I think running a program with kdesudo should result in kde using /var/tmp/kdecache-root and /tmp/ksocket-root instead of the once of the user calling kdesudo.

[ugaciaka (ugaciaka)]

i confirm this bug.
I upgrade kubuntu festy to gutsy...

[dlugidll (dlugilin)]

solution:
uninstall kdesudo, then works fine

[Wouter Horré (wouterh)]

That's not a solution, that's a workaround (but a workaround I consider not sufficient). I need kdesudo. It works, even with these errors, but nevertheless, these error should not happen.

[spartan778 (spartan778)]

Confirmed, but now I can't update anything but however I don't know if thats due to this or not.

[Òscar Casajuana (elboletaire)]

I get the same error but with sudo, not with kdesudo

[libertyernie (libertyernie)]

kdesudo is now fixed, this bug should be too (just don't use sudo for X11 apps.)

[wateenellende (fpbeekhof)]

maybeway36 wrote:
> *** This bug is a duplicate of bug 155032 ***
> https://bugs.launchpad.net/bugs/155032
>
> kdesudo is now fixed, this bug should be too (just don't use sudo for
> X11 apps.)
>

kdesudo is NOT fixed, there is still a permission problem:

$ kdesudo xterm
X Error: BadDevice, invalid or uninitialized input device 171
  Major opcode: 147
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 171
  Major opcode: 147
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
passprompt

Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified

$ dpkg -s kdesudo
Package: kdesudo
Status: install ok installed
Priority: optional
Section: kde
Installed-Size: 168
Maintainer: Anthony Mercatante <email address hidden>
Architecture: amd64
Version: 1.1-0ubuntu2.2
 ......

The bug has been diagnosed: to connect to X, you need to have access
.Xauthority, which is problematic in a NFS+root_squash environment:
$ ls -al ~/.X*
-rw------- 1 beekhof spc 738 2008-01-20 17:44 /home/beekhof/.Xauthority

Currently, the only solution I am aware of is:
apt-get install kdesu; apt-get remove kdesudo

kdesu works fine.

[Frode M. Døving (frode)]

If the trunk version of kdesudo works like my branch when it comes to authentication. It does not rely on ~/.Xauthority for anything at all. It does however, rely on a writeable /tmp/

[wateenellende (fpbeekhof)]

Maybe the conclusion that there is a problem with ~/.Xauthority is
premature. Please see previous discussions on the subject.

However, as you can see from my last mail, it just doesn't work, and I
do remember that this was a problem shared by people having their home
dir on an NFS mount, and that disabling the root_squash option resolved it.

So it would seem some sort of read access to the home dir is required
for root, which is denied due to root_squash. If it is not for
~/.Xauthority, I would not know what it would be for - I'm not an expert
on the subject.

Suggestions welcome!

Frode M. Døving wrote:
> *** This bug is a duplicate of bug 155032 ***
> https://bugs.launchpad.net/bugs/155032
>
> If the trunk version of kdesudo works like my branch when it comes to
> authentication. It does not rely on ~/.Xauthority for anything at all.
> It does however, rely on a writeable /tmp/
>