Issue with Gnome Connection Manager v1.2.1 and MikroTik Devices

[The-First-King]

I'm writing to report an issue I've been experiencing with Gnome Connection Manager (GCM) version 1.2.1 when connecting to MikroTik devices via SSH.

Initially, GCM v1.2.1 worked without any issues with MikroTik devices. However, approximately a year or two ago, I began encountering frequent freezing of SSH sessions. It seems like the SSH connection is only partially functional, as the Keep-Alive values configured in GCM do not seem to alleviate the issue.

When connecting to a MikroTik device, the session appears as active on the MikroTik device itself. However, within GCM, the cursor becomes frozen, and no input is possible. Despite the session being marked as active on the MikroTik device, the connection remains unresponsive in GCM.

During the SSHd session debugging, while troubleshooting on the MikroTik device, I observed that the session became inactive subsequent to the occurrence of the 243 log entries similar to displayed below.

Apr 17 01:26:16 MikroTik ssh: ----- recieved -----
Apr 17 01:26:16 MikroTik ssh: => offset:50 [0x50]
Apr 17 01:26:16 MikroTik ssh: => size:50 [0x50]
Apr 17 01:26:16 MikroTik ssh: --------------------
Apr 17 01:26:16 MikroTik ssh: chan req: window-change 0
Apr 17 01:26:16 MikroTik ssh: packet create: 94

I suspect that a change may have been made in a RouterOS release at some point or OpenSSH version update, as I cannot identify any other reasons why this issue would suddenly arise. Interestingly, when using Remmina with default settings or Linux terminal, I do not encounter any issues, and the connection works as expected. Furthermore, log entries mentioned above are not present.

Could you please provide assistance in troubleshooting and resolving this issue with Gnome Connection Manager? Any insights or recommendations you can offer would be greatly appreciated. Thank you for your attention to this matter.

[The-First-King]

Interestingly, I've observed that adding the '-v' option in the 'Extra arguments' field within the 'Edit Host' window prevents the capture of the problem. As a workaround, I've decided to leave this option enabled permanently for now.