Serious bug with X forwarding?
hornung "at" uni-math.gwdg.de
Fri Sep 3 11:54:01 2004
Since I've not heard anything about this since last month, I'll just post
it again to see if anyone can confirm this problem.
Or if someone could tell me where to post an 'official' bug report? This
is a quite annoying problem, preventing us from using vnc (which
generally is a great program) as often as we'd like to. ;-/
If it helps, I could of course also post our XF86config and the logs.
Thanks in advance,
> Hello all,
> I'm not quite sure if this is a bug or a feature:
> We are using the current version of RealVNC (4.0.1, rpm) as an XF86
> extension to forward the current display (usually :0) to a number of
> clients. The configuration of the XF86Config doesn't seem to be a problem,
> the module and options (such as the password file and whether to accept
> shared connections (always)) are fully recognized according to the logs
> and any number of clients (both Windows and Linux, RealVNC 3.3.7 and
> 4.0.1) can connect at the same time and share the desktop.
> The problem arises when the Linux clients disconnect, there's no problem
> with the Windows clients. The disconnecting of the first client works
> fine, but when the second client disconnects, the VNC-server seems to
> restart, and the whole X System with it -> Windowmanager is halted -> X
> (with VNC) restarts -> Windowmanager restarts.
> Procedure to reproduce:
> 1) Start VNC-Server (RealVNC 4.0.1) as X module (see
> http://www.realvnc.com/v4/x0.html ) for further instructions
> 2) Connect from another linux-machine with any version of the RealVNC
> vncviewer to the server
> 3) Shut down the vncviewer (with kill -9 or F8 -> Exit viewer)
> 4) Repeat steps 2) and 3)
> 5) X server on the first machine will restart
> Either we've missed something obvious (in which case we'd be happy about
> your advice) or the server is buggy (which we'd like to have confirmed),
> so please just try it out and tell about your experiences.
> Thanks, Daniel Hornung
> University of Goettingen