myonlinestuff

I'm extremely pleased to report that the keyboard redirection issues I originally reported are now gone baby gone after installing 2026.3.2.1!

Operating System: Linux Mint 22.3 (Cinnamon)

Kernel: Linux 7.0.0-42-generic

Architecture: x86-64

Hello Christoph,

Thank you for testing 2026.3.1.1 and for the detailed results, this is very helpful.

You are right: the issue where the Windows key and Alt+Tab are not passed to the RDP session is not resolved in 2026.3.1.1. That release fixed other keyboard issues (Alt key getting stuck in SSH sessions, some shortcuts, German layout in RDP), but this specific behavior is still being worked on by our development team. Sorry for the confusion caused by the "fixed" label on this topic.

Your observation about the keyboard grab toggle also matches our findings: it currently does not change how the Windows key and Alt+Tab are handled.

We will update this topic as soon as a version with the fix is released.

Best regards,

Stephan

@Stephan Haupt

You are right: the issue where the Windows key and Alt+Tab are not passed to the RDP session is not resolved in 2026.3.1.1.

I hope this is fixed soon - thank you for continuing to improve this free software, still using an older version (2026.2.2.2 64-bit) which is working fine for keyboard redirection.

Hello,

Thank you for the detailed report, and also for the kind words about our Linux work. Feedback like this is very helpful.

Your observations are consistent with similar reports we have received since the 2026.3.0.5 release.

One setting worth checking is Grab the keyboard input, available in the status bar at the bottom of the application window. This setting controls how keyboard input and shortcuts are handled between Remote Desktop Manager and the active session.

It is documented here:

https://docs.devolutions.net/rdm/user-interface/status-bar/

To help us narrow down what may have changed in this version, could you please confirm the following?

1. Is the Grab the keyboard input toggle visible in your status bar? If so, does switching it on or off make any difference for the Super key or Alt+Tab? A screenshot of the status bar would also be helpful.

2. Do other Remote Desktop Manager shortcuts still work? For example:

   • Ctrl+E to edit a selected entry

   • F2 to rename

   • Ctrl+Page Up / Ctrl+Page Down to switch tabs

3. Also, under File > Settings > Keyboard, do you see the list of configured shortcuts, or is the list empty?

4. Are you running an X11 or Wayland session?

5. In the RDP entry properties, under Connection > Local resources, what is the Keyboard setting currently set to?

Thank you again for the detailed information and for helping us investigate this.

Best regards,

Stephan

@Stephan Haupt

Hi, unfortunately I had to roll back to the previous version as I use these shortcuts so regularly it was difficult to work, but I'll answer where I can.

My environment is running X11.

I did not check to see if Grab the keyboard input was selected but I did check that keyboard combinations were being sent to the remote machine.

Thank you for responding and hopefully others might be able to provide the feedback you're looking for!

I just upgraded to 2026.3.0.5 64-bit and have since not been able to use the Special key as it brings up my host OS's Application Menu. It used to be that I could press Right Ctrl to toggle between the host OS and remote RDP session if this occurred but that is not working. I ran through various options in the application and wasn't able to find anything to address this. Standard keyboard input is fine, but even combinations like Alt+Tab are kept on the local host OS.

Your team has been pretty awesome in continuing to develop this software on Linux so I hope this is a helpful bug report!

Hi, sorry for such a delay in my reply!

I've tried it with the default setting which I think is 60 seconds and my screen was still timing out/going in active. I tried changing it to 15 seconds and still had the timeout issues. (Linux Mint 22.3, RDM 2026.1.0.8 64-bit.)

Perhaps we could introduce a secondary feature, which instead of jiggling the mouse, it sends a keystroke? e.g. "Ctrl" every X seconds....

Some feedback while I have a moment: The small window that pops up to monitor the connection is application modal, preventing the user from being able to go back into RDM and interact with other open hosts. This effectively makes RDM inaccessible. RDM for windows allows you to minimize the tool until the system is back online and connected to.

I also couldn't find a way to launch this tool for more than one remote system at a time. I have only tested this with Windows based Remote Desktop clients. Perhaps this thread could still work out to be a feature request of sorts :)

Ohhh now I feel dumb! Hahaha, at least we agree this is a great feature to have!!! Thank you for your support!

In the Win version of RDM:

• Select a system in the navigation pane

• Under the Macros/Scripts/Tools Tab

• There is a feature to "Check if the host is online".

It continually pings the host and checks if its remote access port is responding, showing a red X if its not responding and green check when it is. Then you can "Connect when available" or "Connect after a failed scan".

I use basically everything this function does daily. A common example is to auto reconnect to a remote system after booting/rebooting it.

Cheers and thanks for your time!

Having this feature would allow me to uninstall Remmina as I have one use case where this is needed, hope to see it soon!

Hello,

Thank you for being so patient!

I'm pleased to inform you that a new version of RDM Linux (2026.1.0.8) has been released, featuring the fix for your issue.

Latest Version: Download RDM

Please let us know if this works or if you encounter any issues.

Best regards,

@Maxim Robert

Very happy to report that I've upgraded to the latest version and tested reconnecting from my secondary display and it works beautifully now! I will admit I was hesitant to report the issue thinking it might not matter enough but you guys totally listened, reproduced the issue and sorted it out - thank you!

Hello myonlinestuff,

I managed to reproduce the issue where the wrong connection would be reconnected, and a fix will be released soon in the next version (2026.1).

Regards,

@Gabriel Dubois

Wow that's so cool to see you were able to reproduce is AND release a fix!! Awesome!

Unfortunately I'm unable to get far enough in the connection process to reproduce the issue since upgrading to the latest version, as every time I connect to that system (Windows Server 2022 via RDP), if it lets me connect on my main monitor, it then crashes RDM when I move it to my secondary monitor. I'll continue to try this after a reboot/patch of my OS and hopefully it will allow me to get the screenshot you've requested.

Where can I find the crash log? I was able to find this in the application log:

System.TimeoutException: Timed out connecting to pipe 'rdm-now-agent-dvc-9a2bd6d8-a5a1-48b7-94ec-97a6cd18c5b4'.

at Devolutions.RemoteDesktopManager.Business.NowAgent.NowProtoPipeTransport.Connect(String pipeName, Nullable`1 timeout, CancellationToken cancellationToken)

at Devolutions.RemoteDesktopManager.Business.NowAgent.NowAgent.Connect(Guid sessionId)

at Client.Views.Embedded.EmbeddedRDPView.<>c__DisplayClass64_0.<<OnConnect>b__1>d.MoveNext()

Thanks for your support!

I noticed others posting a newer version than I had installed. I checked for updates before posting and it self reported it was up to date (a bug). So I downloaded the latest deb package and installed it (2025.3.2.3).

I then tried to reproduce the reconnect issue described in the OP, however, RDM crashes anytime I try to connect to a specific system. It's a Windows Server 2022 host. My other hosts connect fine including another Windows Server 2022 host. If it helps the developers I can send more specific information privately.

I'll add that every time I open RDM, I change the settings to "Simplified Ribbon" and "Show Tabs Only" to maximize the usable screen space on the remote desktop.

Hi all, I'm running Linux Mint 22.3 with RDM 2025.3.1.1.

I have dual monitors and nothing but RDP sessions on my Linux box. I keep some RDP sessions on the primary monitor and some on the secondary. Occasionally, I'll lose my connection to a system on the secondary monitor and I'd like to reconnect, so I use "Reconnect" from the right click menu of the tab for that system, but it winds up reconnecting to a system on my primary monitor. This doesn't always happen, especially if I have very recently made my initial connection to the system on my secondary display, the reconnect function works as it should. But after some time and use, the systems on the primary monitor only seem to allow me to use reconnect. The current work around I'm using is to go to "Window > Show Navigation > Right click the system > Reconnect". It would be great if this was resolved, or if I'm just doing something wrong :)