error creating JAVA virtual machine with option -d32

[Victor Chechik]

I am trying to install TurboVNC on 32-bit Lubuntu but it exits with an error "Unrecognized option: -d32 Error: Could not create the Java Virtual Machine." Running java -version gives

openjdk version "11.0.19" 2023-04-18
OpenJDK Runtime Environment (build 11.0.19+7-post-Ubuntu-0ubuntu118.04.1)
OpenJDK Server VM (build 11.0.19+7-post-Ubuntu-0ubuntu118.04.1, mixed mode, sharing)

Can this be resolved?

[DRC]

Did you install the i386 .deb? If so, install the amd64 .deb instead. i386 packages are included for legacy systems only. (TurboVNC 3.1 will no longer include them.) Those packages do not have an embedded JRE, whereas the amd64 packages do. (In other words, the amd64 packages do not require Java to be installed.)

On May 22, 2023, at 1:20 PM, 'Victor Chechik' via TurboVNC User Discussion/Support <turbovn...@googlegroups.com> wrote:

I am trying to install TurboVNC on 32-bit Lubuntu but it exits with an error "Unrecognized option: -d32 Error: Could not create the Java Virtual Machine." Running java -version gives

--
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/60d7d505-9b9e-471b-8c66-de5f877a22dbn%40googlegroups.com.

[Victor Chechik]

Thanks! I am on i386 architecture so I can't use 64-bit installer. I simply deleted the deprecated -d32 option from the vncviewer bash start file and everything works fine now. 

I am running TurboVNC viewer on Ubuntu which connects to a Windows 10 VNC server. Do I understand it correctly that TurboVNC viewer's SSH session is not compatible with UltraVNC server on Windows? In other words, I cannot use  TurboVNC viewer to tell UltraVNC server to use a specific display (I have a multi-display Windows system)? Unfortunately this cannot be set in the UltraVNC server. Everything works fine with TightVNC server on Windows though as I can specify which display to use on the server side.

Thanks again!

[DRC]

I should probably remove -d32 from the script, then. Didn’t realize it was no longer supported.

The TurboVNC Session Manager (which I assume is what you mean by 

“SSH session”) is only compatible with the TurboVNC Server. For other servers, you have to specify the display number. For instance, with the UltraVNC Server, you would connect to <host>:0, since the server listens on display 0 (port 5900) by default.

On May 23, 2023, at 12:51 PM, 'Victor Chechik' via TurboVNC User Discussion/Support <turbovn...@googlegroups.com> wrote:

Thanks! I am on i386 architecture so I can't use 64-bit installer. I simply deleted the deprecated -d32 option from the vncviewer bash start file and everything works fine now. 

To view this discussion on the web visit https://groups.google.com/d/msgid/turbovnc-users/a72aed41-dfd1-4f88-88d5-21d35a741a65n%40googlegroups.com.

[Victor Chechik]

Thanks again. Yes please just remove -d32 from the script.

Somehow what you suggest does not work for me: I cannot use TurboVNC viewer to connect to host:display from UltraVNC (nothing happens, the script seems to freeze) but I can connect to host::5900 from UltraVNC (but then I can't change the display). Everything works fine with TightVNC server though.   

[DRC]

-d32 has been removed.  Sorry for the delay.

To view this discussion on the web visit https://groups.google.com/d/msgid/turbovnc-users/753c8c8d-7ac9-41c7-b198-36648a321f02n%40googlegroups.com.