Hi, at least in my case the problem was that the "SingleClick" VNC server reported the protocol version 3.16 and the client's top version was the infamous 3.8 ; unfortunately, the client thinks that 3.8 is the maximum version that would be available ever and behaves (in)appropriately.
In my case the solution was fixing the code to use protocol version 3.3 when uncertain and using "hextile" for the encoding parameter ( i.e. replacing ">= 8" to "== 8" in the file 'rfbproto.c' at line 241 ) : 1. sudo apt-get install build-essential xutils-dev # and may be sth else; basically you'll need make & gcc sudo apt-get build-dep xtightvncviewer 2. wget http://www.tightvnc.com/download/1.3.10/tightvnc-1.3.10_unixsrc.tar.gz tar xzvf tightvnc-1.3.10_unixsrc.tar.gz patch -p0 <rfbproto.patch # see attached cd vnc_unixsrc/libvncauth && xmkmf && make cd ../vncviewer && xmkmf && make 3. ./vncviewer -listen -encoding "hextile" # should be done by now 4. notes: (a) should you have any problems with applying the patch file, you may simply edit the file 'rfbproto.c' and replace ">= 8" comparison near line 241 with a simple check for "== 8" ; (b) there are two more ">= 8" entries in the protocol file, I didn't explore that, as the listen mode was all I wanted . ** Patch added: "change "server_minor >= 8" to "server_minor == 8" at line 241" https://bugs.launchpad.net/ubuntu/+source/tightvnc/+bug/123631/+attachment/3705529/+files/rfbproto.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/123631 Title: vncviewer -listen allows connections from UltraVNC SC clients, but doesn't display the window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tightvnc/+bug/123631/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
