I think there's a misunderstanding, I'll try to clarify. When I do [EMAIL PROTECTED] tightvncserver -query localhost
and then [EMAIL PROTECTED] xtightvncviewer butters the viewer on kenny shows me the same login screen (gdm in my case) that I'd get on butter's local display. Ok. Then I use the viewer to login on butters and do stuff. Still fine. But then there's no clean way to log out so someone else can connect to the vncserver on butters and log on as their user because when I terminate the session via the logout button a grey screen with nothing on it remains. This grey screen is also shown to anyone who subsequently connects to the vncserver. I'm not saying this isn't a gnome problem, but this works fine for local gdm logins and regular XDMCP logins, i. e. logging out of gnome kills the X connection and causes gdm (for local logins), or the XDMCP chooser (for remote logins) to restart. Basically whatever initiated the X session needs to cycle. In this case this is tightvncserver, which should recognize the end of the session and issue another XDMCP query to start a new one. Maybe the XDMCP support in tightvncserver is too basic for that? Maybe it's possible to let tightvncserver's virtual X server be managed by gdm/xdm/kdm/whatever just like the regular x server? Then the -query hack would only be needed for "temporary" tightvncservers. C.
