Dear Maintainer, I upgraded my desktop from Bookworm to Trixie, taking remmina from 1.4.29 to 1.4.39, and found that when I connect to systems over SSH my input is not echoed, but is sent as I can enter commands and see the results. The target systems run bookworm, and when accessed from another system, still running bookworm, behave as normal. I downloaded remmina and remmina-common 1.4.40 and installed them and have the same result. Making ssh connections to the same hosts via the ssh command from my desktop does echo input.
I upgraded my laptop to trixie, and had the same symptoms, and then installed the flatpak version to my desktop. That behaved the same, suggesting an upstream bug. Note that 1.4.29 - on another desktop, a Rapberry Pi 5, running bookworm, still works as expected to the same target systems. Installing the flatpak version (1.4.40) on that system has exactly the same symptoms.
For remmina on bookworm with ssh connection to a Debian host (this one running trixie, but the result depends on the remmina version of the client, not the target - have tested with targets of real debian bookworm, and Raspian bookworm, and MotionEye cameras etc. **** stty on remmina 1.4.29 john@harmony:~$ stty speed 38400 baud; line = 0; -brkint -imaxbel john@harmony:~$ note the stty command is echoed. **** stty on remmmina 1.4.40 For remmina on trixie, with ssh to the same host. john@harmony:~$ speed 38400 baud; line = 0; lnext = <undef>; discard = <undef>; min = 1; time = 0; -brkint -icrnl -imaxbel iutf8 -icanon -echo john@harmony:~$ note there was an stty commnand which was not echoed. Following an 'stty echo' - not echoed, then get john@harmony:~$ stty speed 38400 baud; line = 0; lnext = <undef>; discard = <undef>; min = 1; time = 0; -brkint -icrnl -imaxbel iutf8 -icanon john@harmony:~$ **** stty on local terminal For completeness - on a normal terminal on the same host, no remmina involved john@harmony:~$ stty speed 38400 baud; line = 0; -brkint -imaxbel iutf8 john@harmony:~$ As it is too late in Trixie release for this to go to upstream for a fix I suggest a NEWS item with the workaround of entering the stty echo command if needed.