SSH, update screen does not work

[BurtGummer]

Version 0.7.2.8 (https://github.com/1Remote/1Remote/releases/tag/0.7.2.8), Windows 10 Pro up2date.

I have 2 SSH-Tabs open, Tab1 and Tab2. If I enter a command in Tab1 and switch to Tab2, wait a time and switch back to Tab1, the tab/window is not updatet:

If i mark the output, its updatet:

but only the marked text. Any ideas?

I try a new Kitty-version kitty_portable-0.76.1.12.exe and select it in 1Remote, but its the same problem. If I mark the text, the screen updates the text. With putty I have never such problems.

Oh, and the "u" command is a alias for:

aptitude update && aptitude upgrade ; echo "";date;echo ""

[BurtGummer]

Maybe one more example, I enter the command and switch to a other Tab, wait until the command is ready and switch back to the last Tab:

If I mark the text:

[VShawn]

I have noticed this issue, but I haven't figured out the root cause yet. Since I'm an occasional SSH user, my investigation progress is quite slow.

[BurtGummer]

Is there anything I can do to help solve the problem? Otherwise 1Remote would be useless for me, which would be a real pity.

Same problem with version 1Remote-1.0.0.0-beta.06-net6-x64-nightly-20230831-6ac680

[VShawn]

This issue often occurs when opening two SSH sessions, and I have always suspected that it is caused by Kitty being placed in the background. I haven't encountered this problem when only one SSH session is open.

and i have not fix the problem on latest version yet.

[VShawn]

I've found that once I use the SetParent API to set the parent window of Kitty to 1REMOTE, and if the SSH session is in the background of the tab, this issue occurs. The point is, if I don't call SetParent, I won't be able to integrate KiTTY into 1REMOTE. I'm planning to look into how mRemoteNG handles this situation.

[VShawn]

After a weekend of investigation, here are the results:

• Using Kitty as an SSH client and opening multiple SSH sessions simultaneously in the same tab, the SSH session in the background experiences the mentioned bug.
• Switching to PuTTY resolves the bug and it doesn't occur.
• The official PuTTY version doesn't have the ability to remove the software's window frame.
  
• mRemoteNG has forked the official PuTTY, added some features, and removed the window frame.
• Switching back to PuTTY from Kitty may result in losing some CLI commands, especially -cmd: to define a startup auto-command. http://www.9bis.net/kitty/#!pages/CommandLine.md

@BurtGummer Can you help test if putty is properly?

just donwload putty and creat a runner

[BurtGummer]

Thank you very much!
I setup a new runner with PuttyNG, but it works only if I store the password from the connection, without password I got:

"Putty Fatal Error
Configured password was not accepted"

I only save the username, the passwords I like to store in a Keepass2 container. But with saved passwords, there are no screen tearing anymore.
Maybe we should write a bugreport: https://github.com/cyd01/KiTTY/issues ?

[VShawn]

no response from kitty #510 :(

[fs30000]

It is a Kitty problem. I have the same issue using MTPutty. I opened an issue, just like you, but also no reply.

cyd01/KiTTY#514