ssh copy / paste text and crashing issue in 2019.2.14.0

Hi,

For the copy issue, I think the problem you have is due to the way some application output text to the terminal: some end the lines with carriage return, in that case everything is fine. Some end the lines with spaces, so, if you paste the text in a smaller notepad, the spaces are wrapped which result in "empty" lines. We added an option to control how copy is made, it is the fifth icon from the left at the top of the terminal window (tool tip: preserve formatting on copy). If you select this option, the formatting will be preserved by stripping lines of the spaces. It will also preserve the way lines are broken too, this is why it is an option: since some application will output long lines (that get wrapped by the terminal) it is desirable to preserve the long lines and let the other text editor wrap the lines as needed.

As for the crash, I will investigate. If I understand correctly, you login to a gateway, and then login manually to the target host. That is the only way I see you would need to log out twice. Because if you login using the jump host option, logging out once will log you out of both the target host and the gateway. But either way, I'll run some tests to try to reproduce this bug. Thanks for the feedback.

Regards.

Hi Denis

Thanks - I'll take a look at the option you mention with 2019.2.14.0 - Worthy mention however, I never have such issues in putty, MobaXterm or RDMF v5.1.3.0 - I work 8 hours a day in ssh sessions to Linux hosts from a Windows 10 PC.


Correct, I don't use the jump host option. As I'm moving back to the current release, I'll share any other information on the crashing issue I have experienced.

Regards
Angus

Hi Denis,

RDMF 2019.2.21.0


I have 2 different situations where I can recreate some copy/paste issues. It appears that "Preserve formatting on copy" does fix the issue however I can't help thinking that this might not be required if conditions like the two I bring up here can be addressed. Other ssh clients don't require such additional options (putty in the given example below) however I do not know all the conditions you were looking to address when you added the preserve button.

Example 1
1) I type the command

2) use up arrow to repeat the command

3) use up arrow again, backspace the asterisk and re-type the asterisk.

Example 2 - piping to grep.

I also show the same examples with "Preserve formatting on copy" enabled (all ok) and from putty. For all tests, I copied by highlighting text and pasted into the same notepad document and then highlighted everything in notepad so that you can see where additional spaces to end of line (edge of window) have been added on certain lines.


Hope this helps.

Regards

Angus

Hi Angus,

Thanks for the info, I will look into it and see what I can do.

Regards

Hi again,

I have made a little correction, I think it should fix the 2 issues you reported. If it not in the next version, it will be in the next.

Regards

Hi Denis

Again, not beta related - using RDMF 2019.2.21.0

I'm still experiencing a lot of application crashes with this release, 2 or 3 crashes per week - I never had this amount of crashes prior to release 2019.2.14.0. Are there any logs I can capture for you? Start app in debug mode or the like?

Cheers
Angus

Hi Angus,

We can try a session recording. In the property page for SSH entries, in the list on the left, select "Session Recording". There, set the "Mode" field to "Required" and set the "Destination" and "Filename" fields appropriately for the recording file to be saved where you can find it. The session recording will result in a .trp file, you can send me this file in private.
We can also try the session log: in the "Advanced" tab, check the "Enable logging" option, set the "Log mode" to "Event" and set the "Log path" appropriately. But this would be useful only in the situation where the crashes happen on closing the session. Maybe.
Here are a few questions I have: What type of servers are the jump and target hosts? (which kind of linux, or is it a device) Do you use agent forwarding? Have you noticed a pattern about when a crash occurs? Is there a command in particular that makes RDM crash?
I don't expect this bug to be easy to fix, but I will find it. Thanks in advance for your input as well as your patience.

Regards

Hi Angus,

Thanks for the info you sent to me in private. With this, I am going to investigate the agent forwarding, I think it is the most plausible source of this problem. I'll let you know when I find something.

Regards.

Hi Angus,

I made some corrections to agent forwarding. I did find some inconsistencies, they were not causing problems in my environment but it could be different for you. Those changes will be available in the next version. I am not 100% sure this will fix you problem, so let me know if it changes anything.

Regards

I look forward to trying, thanks for the update Denis.

Hi Denis

I just downloaded RDMF 2020.1.10.0 zip version, imported my settings from file, imported my config from file, enabled "allow SSH authentication agent forwarding" for the SSH gateway entry and then ...

1) opened the SSH gateway session and logged into the SSH gateway (we do not use ssh keys to access this first host)
2) SSH'ed from there to a second server - agent forwarding applied and I was logged in without prompting for passphrase (all good)

3) logged out of that 2nd Linux server (with CTRL-D) - CRASH!

Let me know if I can give you any more information.

Regards
Angus

Thanks for the info, I will get back to figuring out what could go wrong. I will let you know when I have a solution to try. Sorry if it takes so long to fix but it is a good one.

Regards.

Hi Angus,

I think I found the bug this time. The fix will be available in the next release. Let me know how it works out for you.

Regards

Sounds promising Denis!

I just experienced a similar crash in 2020-01-13 Denis :(

Sorry to hear that, I will continue investigating. I would like you to send me a log of the failing close. For that, in the properties of the SSH entry, int the "Advanced" tab, check the "Verbose" option, check the "Enable logging" option and set an appropriate "Log path", the log mode must be set to "Event". I will post here when there is a fix available.

I have received your logs and I think I have located the problem. I am currently working on a solution.

Regards!

Hi,

I have fixed the problem. It will be available in the next release. Like always, let me know how it works out for you.

Regards.