Hi,
I originally posted these questions and the previous ones to
VirtualGL-Users but was asked to move to this list:
I am using TurboVNC (in Ubuntu 14.04 and in WIn7) to connect to
VirtualGL running on a Centos6.5 machine. Everything is fine except from
the lack of transmission of special characters like backtick, acute, and
caret (but @ and | do work!). When connecting to the same machine via
ssh all characters are displayed correctly. DRC had suggested to install
the pre-release of TurboVNC to fix this.
Before installing it on the server running Centos I have now installed
turbovnc_1.2.80_amd64.deb and turbovnc_1.2.80_i386.deb on two laptops
running ubuntu-14.04 64 and 32 bits, respectively. Regardless from where
I connect I get a black screen and the message (in a box "TurboVNC
Viewer") saying 'connection closed'
I find this in ./vnc/ubuntu:1.log:
> .............................
> 23/09/2014 21:37:48 Using protocol version 3.8
> 23/09/2014 21:37:48 Enabling TightVNC protocol extensions
> 23/09/2014 21:37:53 Full-control authentication enabled for 192.168.1.9
> 23/09/2014 21:37:53 Pixel format for client 192.168.1.9:
> 23/09/2014 21:37:53 32 bpp, depth 24, little endian
> 23/09/2014 21:37:53 true colour: max r 255 g 255 b 255, shift r 16
g 8 b 0
> 23/09/2014 21:37:53 no translation needed
> 23/09/2014 21:37:53 Enabling Desktop Size protocol extension for client
> 192.168.1.9
> 23/09/2014 21:37:53 Enabling Extended Desktop Size protocol extension
for client
> 192.168.1.9
> 23/09/2014 21:37:53 rfbProcessClientNormalMessage: ignoring unknown
encoding -307 (fffffecd)
> 23/09/2014 21:37:53 Enabling LastRect protocol extension for client
192.168.1.9
> 23/09/2014 21:37:53 Enabling Continuous Updates protocol extension
for client 192.168.1.9
> 23/09/2014 21:37:53 Enabling Fence protocol extension for client
192.168.1.9
> 23/09/2014 21:37:53 Using tight encoding for client 192.168.1.9
> 23/09/2014 21:37:53 Using JPEG subsampling 2, Q42 for client 192.168.1.9
> 23/09/2014 21:37:53 Using JPEG quality 30 for client 192.168.1.9
> 23/09/2014 21:37:53 Using JPEG subsampling 1 for client 192.168.1.9
> 23/09/2014 21:37:53 Using Tight compression level 1 for client
192.168.1.9
> Segmentation fault at address (nil)
>
> Fatal server error:
> Caught signal 11 (Segmentation fault). Server aborting
> XIO: fatal IO error 11 (Resource temporarily unavailable) on X
server ":1"
> after 14 requests (14 known processed) with 0 events remaining.
What is wrong?
Thanks, D.
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
TurboVNC-Users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/turbovnc-users
