Hi On Wed, Apr 12, 2006 at 12:20:02AM +0200, Christian Pernegger wrote: > I think there's a misunderstanding, I'll try to clarify. When I do
To some extent yes. :) > [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 That is because they create a new XDMCP login, which mean that you can login with several users simultaniously to the same host. In your case you do the same but then only allow one user at a time after that. So if one user get problem when logging out (timeout) the next user is affected which is not the case when they can log in simultaniously. > 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. I think the solution in normal cases is that X in the local side terminate and start again. I do not really think you want your vncserver to terminate... > 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? Probably. > 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. I see two ways to solve this problem (at least temporarily): * Use vnc4 x0vncserver or the vnc module so that your normal X login will be possible to use by other people. This can be handled by GDM * Either use gdm from the vncserver start script or let gdm start Xtightvnc server instead of its normal xserver. I think both these two alternative solutions are easier to manage than the way you do not with XDMCP query. Hope this helps. Regards, // Ola > C. -- --------------------- Ola Lundqvist --------------------------- / [EMAIL PROTECTED] Annebergsslingan 37 \ | [EMAIL PROTECTED] 654 65 KARLSTAD | | +46 (0)54-10 14 30 +46 (0)70-332 1551 | | http://www.opal.dhs.org UIN/icq: 4912500 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / --------------------------------------------------------------- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
