Mailinglist Archive: opensuse-bugs (19663 mails)

[bugzilla_noreply@xxxxxxxxxx]

https://bugzilla.novell.com/show_bug.cgi?id=389765

User matz@xxxxxxxxxx added comment
https://bugzilla.novell.com/show_bug.cgi?id=389765#c3





--- Comment #3 from Michael Matz <matz@xxxxxxxxxx>  2008-05-14 07:47:50 MST ---
Actually when you use KDE3 and this applet (that is KDE4 based) there is
another problem.  The whole kdesu thingy becomes confused about which sockets
it wants to use.

$ killall kdesud
$ /usr/bin/kdesu -c "xterm"
kdeinit4: preparing to launch /usr/lib/kde4/libexec/kdesud

(... entering password ..., nothing happens)
kdesud is now running, and we have:

$ ls -l /tmp/ksocket-matz/kdesud*
srw------- 1 matz nogroup 0 2008-05-14 15:40 /tmp/ksocket-matz/kdesud_:0

So, kdesud created a socket named kdesud_:0, all fine, including the $DISPLAY.
stracing kdesu shows that it actually wants to access a different socket:
(I strace the shell where I start kdesu):

$ /usr/bin/kdesu -c "xterm"
kdeinit4: preparing to launch /usr/lib/kde4/libexec/kdesud
kdesud(9220) create_socket: kdesud is already running

(... password dialog comes up, entering password, ... nothing happens)

The strace of kdesu shows this:
9218  access("/tmp/ksocket-matz/kdesud_:", R_OK|W_OK) = -1 ENOENT
..
9218  access("/tmp/ksocket-matz/kdesud_:", R_OK|W_OK) = -1 ENOENT

It's also interesting to see that kdeinit4 also didn't notice that
kdesud already was running, so it started it again, and the second kdesud
did notice it.

I assume that's because of the same error.

So, this is another error in connection with kdesu: kdesud and kdesu accessing
different socket names.  At least in a KDE3 setup.


-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.