Dual monitor focus for reconnect (RDP)

A fix for this issue has been implemented in version 2026.1.0.8

Dual monitor focus for reconnect (RDP)

avatar

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 :)

All Comments (8)

avatar

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.

avatar

Hello.

Thank you for the detailed report.

On our side, we’re not able to reproduce the freeze/crash or the reconnect behavior you described. Everything is reconnecting normally in our Linux test environment.
Could you please send us a screenshot of where you are clicking Reconnect (for example, from the tab right-click menu)? That will help us make sure we are testing the exact same workflow as you.

Also, just to clarify: RDM does not remember which monitor a session was originally opened on. When reconnecting, the session may open on the current active monitor or follow the window focus behavior of the application, rather than the original screen where it was first launched.

If you’re able to provide:

  • A screenshot of the reconnect action
  • Whether the RDM main window is on the primary or secondary monitor at the time of reconnect
  • Any crash log (for the Windows Server 2022 issue)


That would help us investigate further.

Looking forward to your feedback.

Best regard,

Carl Marien

avatar

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!

avatar

Hello,

Thank you for the detailed information and for sharing the timeout exception that’s very helpful.

I will forward this issue, along with the error you provided, to our development team for further investigation.

I’ll keep you updated as soon as I receive feedback from them.

Best regards,

Carl Marien

avatar

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

avatar

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

avatar
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!

avatar
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!

A fix for this issue has been implemented in version 2026.1.0.8