Noticing an issue when outputting to command line using things like the command 'cat', 'tail', etc.
Normally my shell prompt is configured like the following-
user @ hostname in /path/to/folder ➜ |<cursor here to type next command>
I have noticed that when I send output of a file/log/etc to the screen, sometimes at the end there is an errant '%' character and it causes the shell prompt to become corrupted. The cursor ends up on a line BELOW where it should be. You can still type commands and run them, but when you start typing, what you type does not display what you typed or where you typed.
Example-
user @ hostname in /path/to/folder
➜ tail -F /var/log/auth.log
...
Oct 2 11:27:51 hostname systemd-logind[8719]: Session 612 logged out. Waiting for processes to exit.
Oct 2 11:27:51 hostname systemd-logind[8719]: Removed session 612.
^C%
user @ hostname in /path/to/folder
➜
|<cursor end up here to type next command>
The only way to clear this issue is to log out of the session and log back in and hope you don't trigger this issue again. As mentioned above when you type commands in this state they do not display properly on the terminal but you can still type them in an run the commands (but you cannot see what you're typing).
Example (typing 'exit' to end session)-
user @ hostname in /path/to/folder
➜ e
|<cursor ends up here and only first letter typed is displayed on the line ABOVE the cursor>Another example-
user @ hostname in /path/to/folder
➜ cat /path/to/some/config.conf
...
"https": "true,
"interface": "0.0.0.0"
}%
user @ hostname in /path/to/folder
➜
|<cursor ends up here>The config file used above has the following control characters on the last lines of the file (Linux LF format).
/path/to/some/config.conf ... "https": "true,<LF> "interface": "0.0.0.0"<LF> }
Hello,
Thank you for contacting the Devolutions service desk!
Allow me to ask you a few questions to help us investigate this issue :
Best regards,
Gabriel Degrandpré
Here is some additional info.
The % appears to be a control character of some kind. Normally text is white foreground with a black background (normal text) but this character is inverted. The background is white and the foreground (text) is black - normally control characters show up this way.
Hello,
Thank you for your response!
In order to gather some additional information about the issue you are experiencing, we would appreciate if you could provide us logs from your SSH Shell session by following the steps below :
1. In your SSH session's properties, under the Logs tab, check "Enable Logging"
2. Set "Verbose" to 2
3. Use the ellipsis button to select a path to save your log
4. Make sure that your "Log Mode" is set to "Event"
5. Launch your SSH session and trigger the issue
Once this is done, please send us the log this will create. I will shortly send you a ShareFile link by private message so you can share us the logs.
I will then be able to assign this case to our engineering department in order to find the possible cause of this issue.
Best regards,
Gabriel Degrandpré
Logs uploaded
Hello,
Thank you for your response.
I did some digging up and can't seem to find your logs. I'm sorry for the inconvenience, but would it be possible to re-send them via the same ShareFile link I provided in my private message at the start of the week? Again, we would simply need you to include the thread number 38100 in the file name to make sure we can link your file with your case.
Best regards,
Gabriel Degrandpré
Uploaded again, filename 38100_SSH_Output.log
Hello,
Thank you, I just received the log! I'm sharing it with our engineering team right away, and will get back to you as soon as I have news.
Best regards,
Gabriel Degrandpré
Hello,
In order to further investigate the issue you reported, our engineering team would appreciate if you could follow the steps below to generate a .trp recording of your session and the issue.
Here are the steps to enable the .trp recording :
1. In the properties of your SSH Shell entry, go to the the "Session Recording" section
2. Set the mode to "Required"
3. Set the destination to "Custom"
4. Use the ellipsis button to choose the path where the recording file will be saved
5. Set the filename to "Entry Name + Date/Time
Once that is done, please trigger the issue, then close the session and provide us the resulting .trp file.
Best regards,
Gabriel Degrandpré
Hello,
I have been notified of a fix available in RDM versions 2022.3.16.0 and more recent that should resolve the issue you reported.
Would you be interested in trying our the latest version of RDM to verify if this fix does solve the problem? If you are, you can use the link below to download the installer for the latest version of RDM.
https://devolutions.net/remote-desktop-manager/home/thankyou/rdmsetup
If you try it out, let us know how that goes!
Best regards,
Gabriel Degrandpré