I just updated to 2020.2.17.0 and connected to a Linux box. I use vim a lot to edit text files and had to notice that I can no longer escape to the vim normal mode using the ESC key. This used to work before.
Can you confirm this? And if yes, how soon can this be corrected? Is there a workaround?
Hello,
Thank you for contacting us on that matter!
That being said, are you currently using the Free or the Enterprise edition of RDM? Also, what type of Data Source are you currently using?
Furthermore, would it be possible for you to upgrade to the latest version of RDM and see if this issue persists? It can be downloaded here:
https://remotedesktopmanager.com/
Best regards,
James Lafleur
Hi James,
Enterprise, SQL Server as data source.
I just upgraded to the last version (2020.2.19.0 64 bit), and the issue persists.
Best regards,
Vic
Hello Vic,
Thank you for your quick reply!
In order to be able to troubleshoot this issue, our engineering department will need the following:
1- Go in the Properties of one of your SSH Shell entry under the "Advanced" tab
2- Check "Verbose"
3- Check "Enable Logging"
4- Use the ellipsis to select a path to create your log
5- Make sure that your "Log Mode" is set to "Event"
Once this configuration has been made, launch your SSH Shell entry and send us the log that will be created at ticket@devolutions.net. In doing so, a ticket will be created automatically in our system. Just make sure to mention the URL of this forum in your email.
Best regards,
James Lafleur
Hi James,
Under the advanced tab, I don't have a check box next to Verbose, I can only set a number. It's currently set to 0. I increased it to 9.
Further, there is a separate tab for Logging, it's not under Advanced.
Anyway, I did that, there is no sensitive information in the file so I'll attach it here if alright with you.
Best regards,
Vic
ssh_log.log
Hello Vic,
My apologies, I though that you were using the SSH Shell entry type. Since this is not the case, could you please provide us screenshots of the configuration of your entry?
Also, would it be possible for you to create an SSH Shell entry instead and see if the same issue occurs? Since this entry type uses our own SSH engine, it gives us more flexibility when comes the time to fix or implement new features.
Best regards,
James Lafleur
Hi James,
I'm not sure I follow. These are just regular entries of the type "SSH Shell". I don't have anything else.
Best regards,
Viktor
Hello,
My apologies for the confusion, I would like you to do the following:
1- Go in the properties of your SSH Shell entry, under the Advanced Section and set the "Verbose" to "1":
2- Go under the "Logs" tab, check the "Enable Logging" option and make sure to configure a "Log Path" to save the log that will be created when you will launch your SSH Shell entry:
3- Once this is done, launch your SSH Shell connection once more, use the ESC Key, close the connection and send us the log that will be created. This log should also us to find why the ESC key is not sent correctly to your terminal.
Best regards,
James Lafleur
Logpath.png
Hi James,
the first log file I sent you has this exact information already included. I just did a second log file, it looks identical.
Anyway, I can't explain why, but the problem is just gone after having rebooted my computer.
Thanks for your efforts.
Best regards,
Vic
Hello Vic,
Thank you for this information! I am glad to see that you are no longer experiencing this issue.
Do not hesitate to contact us again if you require further assistance.
Best regards,
James Lafleur