I am using Xvnc (as a link to Xrealvnc) launched via inetd to connect to a gdm desktop on a debian distribution. My inetd.conf line looks like this: -
vnc-1024x768x16 stream tcp nowait nobody.tty /usr/bin/Xvnc Xvnc -inetd -query localhost -once -geometry 1024x768 -depth 16 All works fine (get the greeter, login, get nautilus desktop) until I try to run a application from the menu that needs root access using gksu (e.g. synaptic). When I try one of these I get the keyring access dialog but then the launched app just dies with no further dialogs on the display. The Xvnc log for the session in /usr/adm/X2msgs shows that the launched application has been refused a connection to the server. AUDIT: Wed Mar 19 20:45:12 2008: 12916 Xvnc: client 22 connected from IP 127.0.0.1 port 3645 Auth name: MIT-MAGIC-COOKIE-1 ID: 41 AUDIT: Wed Mar 19 20:45:16 2008: 12916 Xvnc: client 22 disconnected AUDIT: Wed Mar 19 20:45:17 2008: 12916 Xvnc: client 22 rejected from IP 127.0.0.1 port 3646 AUDIT: Wed Mar 19 20:45:17 2008: 12916 Xvnc: client 22 disconnected I admit that I am now totally lost in a maze of Xauthority files, Xvnc, gdm, and gksu. Who is supplying what token to whom, what token are they being checked against and where are they getting them from? Any ideas on how I fix this? Is there any way to up the logging level so I can see what tokens are being checked in Xrealvnc? For information. If I run a terminal app in the desktop and do a normal su and then launch synaptic from the terminal it works fine. Any help will be gratefully received. Roger _______________________________________________ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
