Embedded VNC: Unable to highlight text on the default text editor.

Hello,
I will assign this to one of our dev for investigation.

Regards

Hi,

I've tried to replicate your issue on what I have available but, unfortunately, was not able.
My setup does not match yours so I've ask your IT department to build a server as close to your specs as possible.
That being said, would it be possible for you to provide a restricted access to one of your server?
That might be the easiest way to me to replicate your issue.

Regards

Hello,

i'm using RDM for personal use on my private servers.

Unfortunately i can't provide you with a test server; i can try to replicate my setup on a linux virtual machine and share that virtual machine with you, but i can only to it in my spare time so it will take a while.

Regards.

I'll take you up on that vm offer.
If we are able to reproduce your issue before you have time to work on a vm, I'll let you know.

Regards

Hello,

i was able to reproduce all the three issue i have found so far, that is:

a) Embedded VNC: Unable to highlight text on the default text editor: https://forum.devolutions.net/topic32003-embedded-vnc-unable-to-highlight-text-on-the-default-text-editor.aspx
b) Embedded VNC: Unable to type special character which require pressing ALT+KEY: https://forum.devolutions.net/topic31924-embedded-vnc-unable-to-type-special-character-which-require-pressing-a.aspx
c) Embedded VNC and Mate environment: Stuck on the first connection if screen is locked: https://forum.devolutions.net/topic31904-embedded-vnc-and-mate-environment-stuck-on-the-first-connection-if-scr.aspx

in a Virtual Box 6.0.8 Virtual Machine with Ubuntu Mate 18.04.2 and TigerVNC server 1.7.0; the virtual machine is configured to use a Bridge Network Adapater, so you have to change the name of the physical network adapter you want to bridge in the VM network setting page.

This is necessary to allow LAN connections to the virtual machine.

To replicate problem a) and b) you have to:

1.1) Start the virtual machine, the login password is "test" (without quotes);
1.2) In the virtual machine, read the ip assigned by your router to the virtual machine;
1.3) In the virtual machine, open the terminal and start the VNC server with the command: vncserver -depth 24 -geometry 1920x1080 -localhost no -SecurityTypes VncAuth :55 (you can find it in the last used commands by pressing the UP key in the terminal);
1.4) Open RDM and configure an embedded VNC session with the ip read in point 1.2), port equal to 5955, and VNC password equal to test12;
1.5) Start the VNC session and inside that session, open the text editor and try to select some text or write some special characters (you can check also that with the embedded UltraVNC viewer there is no problem at all).

Problem c) is not always present like in my server, but with some patience you can recreate it by doing this:

2.1) Start the virtual machine, the login password is "test" (without quotes);
2.2) In the virtual machine, read the ip assigned by your router to the virtual machine;
2.3) In the virtual machine, open the terminal and start the VNC server with the command: vncserver -depth 24 -geometry 1920x1080 -localhost no -SecurityTypes VncAuth :55 (you can find it in the last used commands by pressing the UP key in the terminal);
2.4) Open RDM and configure an embedded VNC session with the ip read in point 2.2), port equal to 5955, and VNC password equal to test12;
2.5) Start the VNC session and inside that session, lock the screen using the button on the top of the screen;
2.6) If the login field doesn't appears it mean that the bug has been recreated, if not proceed with the following points;
2.7) In the virtual machine, open the terminal and kill the VNC server with the command: vncserver -kill :55 (you can find it in the last used commands pressing the UP key in the terminal);
2.8) In the virtual machine, open the terminal and start the VNC server with the command: vncserver -depth 24 -geometry 1920x1080 -localhost no -SecurityTypes VncAuth :55 (you can find it in the last used commands by pressing the UP key in the terminal);
2.9) Start the VNC session and inside that session, lock the screen using the button on the top of the screen;
2.10) If the login field doesn't appears it mean that the bug has been recreated, if not redo step 2.7), 2.8), 2.9), 2.10) (in my test the problem occurs after a few try);

The virtual machine image is a 1.6GB compressed file (15GB decompressed); how do you want me to send it to you (file sharing site, FTP, etc.)?

Let me know if you have any problem recreating the above bugs.

Regards.

Hello,

Thank you for your cooperation!


Please use the sharefile link below to send us these files:
https://devolutions.sharefile.com/filedrop


Best regards,

Hello,

file uploaded (Ubuntu Mate.7z).

Regards.

Hello,

Thank you for your file! It has been provided to our engineering department.
We will contact you as soon as we will have more information on that matter!

Best regards,

Hi,

Thank you for sharing the vm with us.
I was able to reproduce 2 of your issues and fix them.
Point 'a' and 'b' should now be working properly.

I was not able to reproduce point 'c' but fixes for text selection might have fixed this point too.
If you still encounter problems when the screen is locked, let me know.

A beta version that hopefully solves your issues should be available our website later today.

Regards

Hi,

i can confirm that all the problems (a & b & c) are solved in the latest version.

Thank you very much for your support.

Regards.

Hello,

in the last versions of RDM for windows there is a regression: when selecting/highlighting some test, both with mouse or SHIFT+ ARROW for example on the default text editor, the embedded VNC client immediately get stuck (image freeze) and it is no more usable.

A disconnection and a reconnection is necessary to get again the remote control of the machine; any subsequent try to highlight the text cause an immediate stuck of the connection.

The problem occurs on the same linux servers described on the first post of this topic.

Thanlks.

Hi Raptor,

I was able to reproduce the regression issue concerning text selection.
My connection didn't hang but I lost text selection randomly.

I will look into it.

Regards

Has your setup changed since the time your sent us a VM?
That could include software update and configuration modifications.

Hi Jonathan,

no major changes, only apt update & apt upgrade for this two server:

- Ubuntu 18.04 with MATE desktop environment and TigerVNC server
- Ubuntu 16.04 with LXDE desktop environment and TigerVNC server

A major change (Debian 9 to Debian 10) for this server:

- Raspbian September 2019 Update with PIXEL desktop environment and RealVNC server


The same problem (hang) occurs on all the servers above.

Have you been able to recreate the issue on the VM i sent to you? I don't have that VM anymore so i can't try by myself.

Hi,

No, I wasn't able to replicate the hang issue with the VM, that's why I wanted to know if any changes were made.
I will apt update and upgrade in case a software update is causing the problem.

Progress.

Your issue seems to only happen in RDM 32bits, would that be right?
Does connecting using RemoteDesktopManager64.exe prevent this from happening?

Hi,

yes with the 64bit version i don't have this problem.

Hi,

I've fixed the issue in RDM 32bits.
It will be included in the next release of RDM.

Regards,