Bug#361888: tightvncserver: in -query mode: shows empty screen instead of gdm after logout
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... No necessarily, but that would be a workaround, since I could start it up again immediately after. * [...] let gdm start Xtightvnc server instead of its normal xserver. I tried that, like so (excerpt): [daemon] VTAllocation=false [server-VNC] name=VNC server command=/usr/bin/Xtightvnc -geometry 1024x768 -depth 32 flexible=false handled=true chooser=false It just doesn't work. The tightvncserver starts up, but before gdm can run the login window it exits again. After a number of tries gdm gives up. Thanks for helping, C.
Bug#361888: tightvncserver: in -query mode: shows empty screen instead of gdm after logout
Hi On Tue, Apr 11, 2006 at 01:40:13AM +0200, Christian Pernegger wrote: Package: tightvncserver Version: 1.2.9-6 Severity: normal For a normal session initiated with gdm, gdm will reappear after the user logs out, i. e. the session ends. With the -query option to vncserver one can get much the same effect (gdm login) but after the session ends all that remains is a gray screen, gdm does not return, or only after a multi-minute timeout. I do not fully see the relation to tightvnc here. You run tightvncserver -query somexdmcpserver Then you log out The session is still alive because you still have the server running So what do you expect tightvncserver to do? A new query, the old one have not exited (as far as I can tell) yet. I can agree that the timeout is not that nice, but I do not really see the relation to vnc here. It would be good to know more about what happens on the host that you query. Has it terminated the session? Do the session ever terminate? Is it gdm that do not restart as it should? I do personnaly feel that I'm complaining on everything else now but I hope it is useful for you anyway. :) // Ola Thanks, C. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-k7 Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8) Versions of packages tightvncserver depends on: ii dpkg 1.13.17package maintenance system for Deb ii libc6 2.3.6-3GNU C Library: Shared libraries an ii libjpeg62 6b-12 The Independent JPEG Group's JPEG ii libx11-6 6.9.0.dfsg.1-6 X Window System protocol client li ii libxext6 6.9.0.dfsg.1-6 X Window System miscellaneous exte ii perl 5.8.8-3Larry Wall's Practical Extraction ii vnc-common3.3.7-8Virtual network computing server s ii xbase-clients 6.9.0.dfsg.1-6 miscellaneous X clients ii xlibs 6.9.0.dfsg.1-6 X Window System client libraries m ii xserver-common6.9.0.dfsg.1-6 files and utilities common to all ii zlib1g1:1.2.3-11 compression library - runtime Versions of packages tightvncserver recommends: ii xfonts-base 6.9.0.dfsg.1-6 standard fonts for X -- no debconf information -- - 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]
Bug#361888: tightvncserver: in -query mode: shows empty screen instead of gdm after logout
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.
Bug#361888: tightvncserver: in -query mode: shows empty screen instead of gdm after logout
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]
Bug#361888: tightvncserver: in -query mode: shows empty screen instead of gdm after logout
Package: tightvncserver Version: 1.2.9-6 Severity: normal For a normal session initiated with gdm, gdm will reappear after the user logs out, i. e. the session ends. With the -query option to vncserver one can get much the same effect (gdm login) but after the session ends all that remains is a gray screen, gdm does not return, or only after a multi-minute timeout. Thanks, C. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-k7 Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8) Versions of packages tightvncserver depends on: ii dpkg 1.13.17package maintenance system for Deb ii libc6 2.3.6-3GNU C Library: Shared libraries an ii libjpeg62 6b-12 The Independent JPEG Group's JPEG ii libx11-6 6.9.0.dfsg.1-6 X Window System protocol client li ii libxext6 6.9.0.dfsg.1-6 X Window System miscellaneous exte ii perl 5.8.8-3Larry Wall's Practical Extraction ii vnc-common3.3.7-8Virtual network computing server s ii xbase-clients 6.9.0.dfsg.1-6 miscellaneous X clients ii xlibs 6.9.0.dfsg.1-6 X Window System client libraries m ii xserver-common6.9.0.dfsg.1-6 files and utilities common to all ii zlib1g1:1.2.3-11 compression library - runtime Versions of packages tightvncserver recommends: ii xfonts-base 6.9.0.dfsg.1-6 standard fonts for X -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
