Problems getting TurboVNC to work with Oracle Linux 8.

[Stephen Carville]

I started testing TurboVNC on OL8 this weekend.  Immediately I noticed it seem to start up gnome exclusively,  Hoiw can I get it to start MATE or Xfce? I did this readily with TigerVNC and ~/.vnc/xstartup but TurboVNC seems to use a different approach.  Even a link to some documentation would be appreciated.

Also when I try to connect using the version of vncviewer included.

/opt/TurboVNC/bin/vncviewer -via uek8desktop01 localhost:1001

I get the error:

Could not create SSH tunnel
java net.UnknownHostException uek8desktop01

I am guessing this is because TurboVNC's vncviewer does not use ~/.ssh/config file to expand the alias.  The TigerVNC version connects as expected which is how I know that TurboVNC is starting up Gnome

I am using version 2.2.6-20210221 from the yum repo.

[osmark]

For Mate windows manager please use: 

vncserver -geometry 1920x1080 -wm mate-session

--
You received this message because you are subscribed to the Google Groups "TurboVNC User Discussion/Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to turbovnc-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/turbovnc-users/73532588-b033-4bf0-bd98-6c55a8809902n%40googlegroups.com.

[Stephen Carville]

That worked.  Thank you.

[DRC]

I am out of the office right now but will double check our support of the OpenSSH config file when I get back. What you describe should work with TurboVNC 2.2.6.

On Nov 6, 2021, at 8:47 AM, Stephen Carville <stephen....@gmail.com> wrote:

That worked.  Thank you.

To view this discussion on the web visit https://groups.google.com/d/msgid/turbovnc-users/d656c501-49c6-4091-aec5-a5b1109b4eben%40googlegroups.com.

[DRC]

I can't reproduce the issue.  If I add, for example:

Host my_fake_server_name
  HostName {my_server_ip_address_or_real_server_name}
  User drc

to ~/.ssh/config, then executing

  /opt/TurboVNC/bin/vncviewer -via my_fake_server_name localhost:{my_display_number}

works as expected.  Can you post the relevant entry from your ~/.ssh/config file?  Perhaps there is a bug that I'm not encountering for some reason.

DRC

[Stephen Carville]

Sure.  I use a bastion host with ProxyJump.  (I hope the formatting comes out OK)

Host  ovpn

  Hostname        bastion.lereta.com
  User            stephen
  Protocol        2
  Port            8022
  ControlMaster   auto
  ControlPath     ~/.ssh/master-%r@%h:%p
  ControlPersist  3600
 
Host uek8desktop01
  ProxyJump       ovpn

[DRC]

Ah, OK.  The built-in SSH client in the TurboVNC Viewer won't support that, but you should still be able to use OpenSSH by passing -extssh to /opt/TurboVNC/bin/vncviewer.  That will mimic the behavior of TigerVNC, since it also uses the external SSH client.

DRC

To view this discussion on the web visit https://groups.google.com/d/msgid/turbovnc-users/de7a8c0b-686a-42dc-9d2c-d21c4bc4ec97n%40googlegroups.com.

[Stephen Carville]

Afraid not.  I tried a few variation then turned up the logging level.

$ /opt/TurboVNC/bin/vncviewer  -loglevel 110 -extssh -via uek8desktop01 localhost:1001

libjawt.so path: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.312.b07-1.el8_4.x86_64/jre/lib/amd64

Log setting: 110
main: start called
Tunnel: SSH command line: /usr/bin/ssh -f -L 39577:localhost:1001 uek8desktop01 sleep 20
CConn: connected to host localhost port 39577
CConnection: reading protocol version
(repeat the above about 9000 times)

This is probably because the -L forwarding is going to the wrong port.  Connecting using the TigerVNC viewer I see:

$ sudo ss -natp|grep Xvnc
LISTEN     0      5               127.0.0.1:6801         0.0.0.0:*     users:(("Xvnc",pid=186214,fd=7))                         
LISTEN     0      5               127.0.0.1:6901         0.0.0.0:*     users:(("Xvnc",pid=186214,fd=6))                         
ESTAB      0      0               127.0.0.1:6901       127.0.0.1:38462 users:(("Xvnc",pid=186214,fd=13))                        

However changing the command line to use the actual listening port does not work either:

$ /opt/TurboVNC/bin/vncviewer -loglevel 110 -extssh -via uek8desktop01 localhost:5901

libjawt.so path: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.312.b07-1.el8_4.x86_64/jre/lib/amd64
Log setting: 110
main: start called
Tunnel: SSH command line: /usr/bin/ssh -f -L 45311:localhost:5901 uek8desktop01 sleep 20
CConn: connected to host localhost port 45311
CConnection: reading protocol version
(repeat the above about 9000 times)

Sorry if the above is hard to read.  I am new to Google Groups and haven't figured out how to get their editor to format anything correctly.

[DRC]

Try

    /opt/TurboVNC/bin/vncviewer -loglevel 110 -extssh -via
uek8desktop01 localhost:1

or

    /opt/TurboVNC/bin/vncviewer -loglevel 110 -extssh -via
uek8desktop01 localhost::5901

You have to use two colons if you are specifying a TCP port rather than
a display number.

DRC

[Stephen Carville]

Sorry it took so long to get back to you.

The first command does not work possibly because the display requested (1) does not match the display expected (1001)

The second one, however, does work:

libjawt.so path: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.312.b07-2.el8_5.x86_64/jre/lib/amd64

Log setting: 110
main: start called

Tunnel: SSH command line: /usr/bin/ssh -f -L 38161:localhost:6901 uek8desktop01 sleep 20
CConn: connected to host localhost port 38161
CConnection: reading protocol version (repeats 743 times)
CConnection: Server supports RFB protocol version 3.8
CConnection: Using RFB protocol version 3.8
CConnection: processing security types message
CConnection: Server offers security type None(1)
CConnection: Server offers security type Tight(16)
CConnection: Choosing security type Tight(16)
CConnection: processing security message
Tight: Choosing security type None(1)
CConnection: processing security result message (repeats 1411 times)
CConnection: Authentication success!
CConnection: reading server initialisation
CConnection: initialisation done
DesktopWindow: GraphicsDevice supports HW acceleration.
PlatformPixelBuffer: Native pixel format is depth 24 (32bpp) little-endian rgb888
PlatformPixelBuffer: Native pixel format is depth 24 (32bpp) little-endian rgb888
CConn: Using pixel format depth 24 (32bpp) little-endian rgb888
CConn: Requesting Tight encoding
CConn: Screen 0 work area: 0, 33 1920 x 1134
CConn: Spanned work area: 0, 33 1920 x 1134
Viewport: Set geometry to 0, 33 1920 x 1134
CMsgReaderV3: Server supports GII version 1
CConn: Enabling GII
ScreenSet: LAYOUT RECEIVED:
ScreenSet:     64 (0x40): 1912x1083+0+0 (flags 0x0)
ScreenSet: LAYOUT SENT:
ScreenSet:     64 (0x40): 1912x1083+0+0 (flags 0x0)
CConn: Enabling continuous updates
ScreenSet: LAYOUT RECEIVED:
ScreenSet:     64 (0x40): 1912x1083+0+0 (flags 0x0)
TurboVNC Helper: Disabling X11 full-screen mode for window 0x03800027
No extended input devices.

[DRC]

I misunderstood your intent, because your previous message suggested that you were trying to connect to port 5901 (Display :1).  If you need to connect to Display :1001, then do:

    /opt/TurboVNC/bin/vncviewer -loglevel 110 -extssh -via

uek8desktop01 localhost:1001

or

    /opt/TurboVNC/bin/vncviewer -loglevel 110 -extssh -via

uek8desktop01 localhost::6901

--

You received this message because you are subscribed to the Google Groups "TurboVNC User Discussion/Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to turbovnc-user...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/turbovnc-users/bc11ef0b-4a54-4001-93ef-7c67582fc392n%40googlegroups.com.