Support

@Everyone, Even if Ubuntu is the only officially supported distro for RDM, we know Linux is all about choices and we wouldn't want to change that. In that optic, here's a little guide to help you install RDM on your preferred, unsupported distro. First of all, dependancies. glibc 2.27 libwebkit2gtk-4.0 ca-certificates libsecret-1-0 gnome-keyring If you are installing RDM on a distro supporting .deb files, you are done. Simply install the deb package and everything should be good to go. You can start RDM using the menu icon or the remotedesktopmanager terminal command. You can also opt to install the net.devolutions.RDM or net.devolutions.RDMFree flatpak package from flathub. Otherwise, you can manually install RDM using the following steps Extract deb file content. (ar x RemoteDesktopManager_x.x.x.x_amd64.deb) Extract data.tar.xz content. (tar -xf data.tar.xz) Copy bin/remotedesktopmananger to /bin Copy usr/lib/devolutions/RemoteDesktopManager to /usr/lib/devolutions/RemoteDesktopManager You can now start RDM using the remotedesktopmanager terminal command. Let us know if you still have issues running RDM on your preferred distro. Known issues. On platform running non-gnome desktop environment, the splash screen might prevent entering your serial when launching RDM for the first time. Simply press the 'Cancel' button to close the dialog, that should make the splash screen disappear. You can then use the Help menu tab to access the registration form again.

Hi, We recently switch our backend from mono to .net6. Since this switch, a number of our users are experiencing SSL errors while connecting to their data source. The reason being .net6, out of the box, is stricter when it comes to TLS support. With these following steps, you can relax SSL minimum requirements (in effects allowing TLS 1.1) In /etc/ssl/opensll.cnf Place this at the top of the file openssl_conf = default_conf Then place this anywhere in the file [ default_conf ] ssl_conf = ssl_sect [ ssl_sect ] system_default = system_default_sect [ system_default_sect ] MinProtocol = TLSv1 CipherString = DEFAULT@SECLEVEL=1

hi, Anyone which got luck with the AI Assistant? When I'm trying Claude, I am getting: Invalid Anthropic API Key despite I'm 100% sure the key is correct

Greetings all, First post. My goto Linux terminal application is Midnight Commander. I've used it, or a variant (Norton Commander) for longer than I care to admit. The issue is it doesn't behave nicely with RDM. Mouse support is wonky, keyboard support is wonky, yadda, yadda, yadda. I'm running RDM in Pop!_OS Cosmic (on two separate machines actually) , and MC is run on Ubuntu server and RaspberryPi's if that makes any difference. Is there a magic decoder ring of settings for using MC in RDM? Thank you chris

I just wanted to take a moment to thank the Devolutions team for creating a Linux version of Remote Desktop Manager. Even though our Remote Desktop Manager servers still run on Windows for now, having a native Linux client on our workstations is fantastic. For those of us working daily on Linux, this makes a real difference. Of course, like any software, it’s still evolving—but that’s completely normal. The important thing is that it exists and continues to improve. So a sincere thank you to the Devolutions team for investing in Linux support. It’s greatly appreciated!

Hi. Tools->Terminal What exactly does it launch? I was expecting my linux terminal in tab inside RDM but it seems that is not the case as contents of directories does not match. How can I change that?

Hi Support Team, I have a centralized question regarding troubleshooting: Where can I activate and view the application logs in the Linux version of RDM? I have been using RDM on Windows since the beginning of my project, but I recently switched my desktop environment to Linux. My goal is to replicate my Windows workflow, but I’ve already noticed that the Linux version has fewer features. I want to approach this step-by-step. Currently, I primarily use RDM for server administration via web interfaces (Proxmox VE, PBS, TrueNAS, etc.) and SSH. I am trying to use embedded tabbed browsing with automatic login (Username/Password), but it is not working as expected. To better understand what is happening under the hood, I would like to start by analyzing the logs. Could you please point me to the log settings and the log file location on Linux? ========== DIAGNOSTIC ========== cachyos rolling Kernel version [6.19.5.3] Container [None] Desktop environment [KDE] Display server [wayland] Architecture [X64] Support local password saving [Ok] Is administrator [Ok] Is a system administrator [Ok] Is a database administrator [Ok] Is elevated privilege [No] Workspace size [1646 / 753] Is the Internet connected [Ok] Allow multiple instances [Ok] Allow drag and drop [Ok] Auto-refresh [No] Debug level [262143] Running since [Running since: 28 min 27 sec] ========== DATA SOURCE ========== Data source ID: **** Repositories (count): 0 Data source type: Devolutions Hub Personal Data source settings size: 2.6 KB User specific settings count: 0 User specific settings size: 0 Bytes Connection protocol: Caching/Offline: ReadOnly (File, OpenMCDFv2) Allow connection states: True Repository (ID): **** Repository size: 2 MB Entries/Items: 301/301 Sessions: 223 Data entries: 0 Credentials: 6 Sub entries: 0 Documents: 0 Contacts: 0 -->Sub total: 229 Session tools: 0 Folders: 72 --> Total: 301 Entries with variables: 0 Virtual folders: 0 Custom images: 0 Custom images (legacy): 20 RTF notes: 0 Connection client version: ****

I apologize if this is only happening to me but ever since I upgraded to the latest version from the previous 2025 version, I have been unable to use RDP. I believe it connects but all I get is a black background/window. Doing journalctl when trying to connect showed RDM unable to find a specific cisco h264 file. I have .8 and it was looking for .7 so I symlinked it in the directory and that error went away. That said, the issue persists. I am attaching the the journalctl entries on an RDP connection in case it points to something obvious that I haven't found. [image] Thanks in advance for the help.

Hi, Is it possible to copy text/files from a Linux host to a remote Windows via RDP using RDM for Linux ? Thanks

I've just installed the flatpack version of Remote Deskop Manager on opensuse tumbleweed but I can't open any connections since I get the error "xfreerdp not found" even though I have it installed. I have also tried installing the flatpack version of xfreerdp but that didn't help. Is there a way to specify the location of xfreerdp?

Hi, I am trying to remote into another Ubuntu Desktop which is running an instance of rustdesk as well. Both machines are Ubuntu Desktop. I have Remote Desktop Manager for Ubuntu desktop installed updated to the latest version. I cannot see the Rustdesk session in RDM for Ubuntu. I cannot see an Add-ons button as well. Only a checkbox saying "show deprecated". Rustdesk is probably the best remote desktop solution for linux machines. I think it should definitely be included in the RDM package for Ubuntu Desktop versions. Is this not currently supported? Is there another way to connect to a Rustdesk instance via RDM on Ubuntu. Thank you.

Dear RDM team, I'm reviving the topic on RDM for Linux feature parity when compared to RDM for Windows. RDM has become the only tool that prevents me from migrating off Windows to Linux, which I'm planning for quite some time already. I appreciate that you released native RDM for Linux, but its features are... incomplete. Because of that I tried running RDM for Windows in a Windows virtual machine on Linux, but the virtualization/hardware emulation so that Windows runs great on Linux is... less than ideal. It's slow, and RDM, being quite a big app is even slower. And... having Remote Desktop within a VM screen, inside my primary display is also not going to be working well, no matter what. I would like you to somehow rearchitect your development process so that most or all features added to RDM on Windows also end up in RDM on Linux. That would provide Linux community with the best remote management tool that ever existed on Linux so far, with the greatest features and versatility. As for my priorities it would be remote management entries, such as RDP, SSH, Web, maybe Mikrotik Winbox (they now have Winbox 4 multi platform); credentials entries, and handling Hub. I don't care about VPN entries that much. But to be able to launch the above entries with doubleclick, having credentials entered, just like in RDM on Windows, is a must have. Great SSH agent, password generator and other shared tools would be nice, too. There's business justification to that as well. I think fully-featured RDM on Linux would attract many Linux-only users (of which majority are technically skilled, working in IT industry), and certainly some of them can become paying customers. Please think about that. Thanks in advance!

Hello Please forgive me for such a dramatic subject, but the reality is is that the Remote Desktop Manager leaves a lot to desire. I have been a Mac User - NOT fan boy! I use Windows for my work via RDP and have no issues with Windows 11, Linux or any other OS. I just started my journey into Linux a few months ago, and I thnik that I have tried 25+ different distributions and the only thing that is consistently bad is "Remote Desktop Manager", on every distribution there is something that is funny.. As mentioned I use RDP for my work, so from my mac I rdp into a VM in my homelab and from there I connect a vpn to my customer and then a new RDP to the customer, this has been working for years. Now, my MacBook Pro M1 Max is up for reneval so I was looking into maybe switching to a Intel PC and use Linux. My current pc is a Minisforum MS-01 I9 with 32gb memory and 1tb nvme, so not low spec IMO first thing I notice was that UI of Remote Desktop Manager looks funny, so I wanted to submit a ticket... Pressing the 'Submit support ticket" brings up a dialog... but the dialog is not in focus so I need to grab my mouse to activate the dialog.... Why ?? what I wanted to report was the UI of "Remote Desktop Manager", pleas look at the screenshot why is the UI not consistent, after all these years [image] look at how small the icons and text is Now the worst part is, that connecting to a windows 11 VM that I have been using for the last year does not work - sure you could say that I misconfigured something, but I can connect to another, and I can connect to the specific VM from my ipad, from windows and from my mac, but not from Linux using "Remote desktop manager" - this vm is setup to ask for password, but for some reason it does not work - no error, no log nothing, it simply flashes the screen and then nothing.. why ?

I have a recurring problem with the clipboard and RDM, both on Windows and Linux, the clipboard is shared between different remote sessions, I explain ... I have several sessions open from my host RDM (both Linux and Windows) to several Windows servers, can be 2012 as 2019, etc .... and to these sessions some colleagues connect with teamviewer or anydesk, i launch the connection to them and they connect while i keep the sessions open on my RDM, because what the remote user copies in the RDM2 session appears to him when i paste to the remote user of the RDM3 session or even to me on my host, when I do ctrl+c and then do ctrl+v if I take a little while to do ctrl+v I get what the user 1 or 2 had copied in their session, this is a problem both security and functional, and as I comment happens to me both in Windows and Linux for a long time in successive versions RDM And another problem that I have only in Linux and that also affects the clipboard, is that for some reason now only works in RDMctrl+c and ctrl+v if I do it with the ctrl located on the right side of the keyboard, if I do it with the left side I only get the c or v, the clipboard does not work, and the clipboard only works with text, with images I have to upload the capture from my host. of course before entering RDM ctrl+c and ctrl+v works perfectly

Hello everyone! Desperately looking for help here.. So I've got a bunch of Windows Server 2019/2022 machines in my LAN. I've also got two instances of RDM, one is on my Windows 11 PC, another is on my Arch Linux laptop. The Windows 11 RDM connects to these Windows Server machines via RDP with 0 issues. All I had is to enter the host/username/password and all worked like a charm! Unfortunately it's been everything but similar experience when I installed (using yay) RDM on my Arch. The system is fully updated. RDM version is 2025.3.2.2 After creating the session entry the same way I always did, I'm getting an error: [image] That's what the console gives me out: ~ ❯ remotedesktopmanager [22:10:20:498] [46753:0000b6b5] [INFO][Devolutions.Rdp.Credentials] - [Parse]: parsing "A************", "" (Mstsc) => "Username: "A************" Domain: """ [22:10:20:504] [46753:0000b6b5] [WARN][com.freerdp.settings] - [freerdp_settings_print_warnings]: [experimental] enabled GlyphSupportLevel GLYPH_SUPPORT_FULL[0x00000002], expect visual artefacts! [22:10:20:505] [46753:0000b6b5] [ERROR][com.freerdp.channels.virtual.channel] - [virtchan_virtual_channel_init_event_ex]: Unhandled event type 0 [22:10:20:505] [46753:0000b6b5] [ERROR][com.freerdp.channels.virtual.channel] - [virtchan_virtual_channel_init_event_ex]: Unhandled event type 0 [22:10:20:505] [46753:0000b6b5] [ERROR][com.freerdp.channels.virtual.channel] - [virtchan_virtual_channel_init_event_ex]: Unhandled event type 0 [22:10:20:513] [46753:0000b6b5] [INFO][com.freerdp.codec] - [openh264_load_functionpointers]: loaded libopenh264.so.7 2.6.0 [22:10:20:529] [46753:0000b6b5] [INFO][com.freerdp.codec] - [openh264_load_functionpointers]: loaded libopenh264.so.7 2.6.0 [22:10:20:533] [46753:0000b6b5] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x7f5f583115e0]: ************************************************* [22:10:20:533] [46753:0000b6b5] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x7f5f583115e0]: This build is using [runtime-check] build options: [22:10:20:533] [46753:0000b6b5] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x7f5f583115e0]: * 'WITH_VERBOSE_WINPR_ASSERT=ON' [22:10:20:533] [46753:0000b6b5] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x7f5f583115e0]: * [22:10:20:533] [46753:0000b6b5] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x7f5f583115e0]: [runtime-check] build options might slow down the application [22:10:20:533] [46753:0000b6b5] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x7f5f583115e0]: ************************************************* [22:10:20:533] [46753:0000b6b5] [WARN][com.freerdp.core.rdp] - [log_build_warn_cipher][0x7f5f583115e0]: ************************************************* [22:10:20:533] [46753:0000b6b5] [WARN][com.freerdp.core.rdp] - [log_build_warn_cipher][0x7f5f583115e0]: [SSL] {Cipher} build or configuration missing: [22:10:20:533] [46753:0000b6b5] [WARN][com.freerdp.core.rdp] - [log_build_warn_cipher][0x7f5f583115e0]: * des-ede3-cbc: RDP security FIPS mode will not work [22:10:20:534] [46753:0000b6b5] [WARN][com.freerdp.core.rdp] - [log_build_warn_cipher][0x7f5f583115e0]: ************************************************* [22:10:20:534] [46753:0000b6b5] [WARN][com.freerdp.core.nego] - [nego_enable_aad]: This build does not support AAD security, disabling. [22:10:20:546] [46753:0000b6b5] [ERROR][com.freerdp.core] - [rdp_client_connect]: ERRCONNECT_SECURITY_NEGO_CONNECT_FAILED [0x0002000C] [22:10:20:546] [46753:0000b6b5] [ERROR][com.freerdp.core.connection] - [rdp_client_connect]: Error: protocol security negotiation or connection failure [22:10:20:556] [46753:0000b6b5] [INFO][Devolutions.Rdp.Credentials] - [Parse]: parsing "A************", "" (Mstsc) => "Username: "A************" Domain: """ [22:10:20:557] [46753:0000b6b5] [WARN][com.freerdp.settings] - [freerdp_settings_print_warnings]: [experimental] enabled GlyphSupportLevel GLYPH_SUPPORT_FULL[0x00000002], expect visual artefacts! [22:10:20:557] [46753:0000b6b5] [ERROR][com.freerdp.channels.virtual.channel] - [virtchan_virtual_channel_init_event_ex]: Unhandled event type 0 [22:10:20:557] [46753:0000b6b5] [ERROR][com.freerdp.channels.virtual.channel] - [virtchan_virtual_channel_init_event_ex]: Unhandled event type 0 [22:10:20:557] [46753:0000b6b5] [ERROR][com.freerdp.channels.virtual.channel] - [virtchan_virtual_channel_init_event_ex]: Unhandled event type 0 [22:10:20:566] [46753:0000b6b5] [INFO][com.freerdp.codec] - [openh264_load_functionpointers]: loaded libopenh264.so.7 2.6.0 [22:10:20:578] [46753:0000b6b5] [INFO][com.freerdp.codec] - [openh264_load_functionpointers]: loaded libopenh264.so.7 2.6.0 [22:10:20:579] [46753:0000b6b5] [WARN][com.freerdp.core.nego] - [nego_enable_aad]: This build does not support AAD security, disabling. [22:10:20:588] [46753:0000b6b5] [WARN][com.freerdp.core.nego] - [nego_process_negotiation_failure]: Error: HYBRID_REQUIRED_BY_SERVER [0x00000005] [22:10:20:588] [46753:0000b6b5] [ERROR][com.freerdp.core.nego] - [nego_connect]: Protocol Security Negotiation Failure [22:10:20:588] [46753:0000b6b5] [ERROR][com.freerdp.core] - [rdp_client_connect]: ERRCONNECT_SECURITY_NEGO_CONNECT_FAILED [0x0002000C] [22:10:20:588] [46753:0000b6b5] [ERROR][com.freerdp.core.connection] - [rdp_client_connect]: Error: protocol security negotiation or connection failure Not sure if that's helpful, but I've also made TLS Diagnostics and here are results: [image] What I've tried so far: Switching back and forth every possible checkbox/option in the RDP session settings as well as global RDP settings in RDM. On a Windows Server machine itself I tried removing NLA (network level authentication) requirement. I tried exporting my working sessions from Windows 11 RDM and importing them to Linux instance. The behaviour is the same. At the same time on the same Linux machine, running 'xfreerdp3 /v:10.10.10.123 /u:Administrator /d:. /p:'mycoolpassword' /sec:nla /cert:ignore '/auth-pkg-list:!kerberos' lets me connect successfully (this was suggested when I tried troubleshooting with AI) Also, installing remmina and connecting through it works like a charm. But I'm so used to use RDM in Windows, I want it also to be running in Linux. If anyone can provide any useful info, I'd greatly appreciate that! If you need any additional logs/info, I'll happily provide that. Thanks in advance! Victor

I have installed RDM 2025.3.2.3 on a notebook (ThinkPad X1 Yoga Gen 3) with Linux Mint 22.3 (Cinnamon). The notebook has a 14 inch display with 2560x1440 pixels When "Monitor scaling" in Mint is set to 150%, the ribbon is not scaled accordingly When "Monitor scaling" in Mint is set to 100%, the ribbon is correct I haven't found any setting in RDM where I could change this Is this a known issue? Is there a way to work around this? Many thanks in advance. [image]

I atempted to do an import from my remmina configuration files. The import seemed to work fine, fodlers were created etc. When I launched on of the imported entries it asked about an installation path, I chose default and set that as the default. Now the entry throws an xfreerdp not found. If I create an entry manually it works. I even tried exporting an entry from Remmina as a .rdp file, that also gives the same error. While I don't have a problem manually recreating al my connection, importing them would have been nice. All I need is host name and folder, did I do something wrong when being promppted for the installation path?

Greetings, This function used to work, but now causes RDM to crash. So I don't think there's a configuration issue. Unfortunately, I don't use the feature often, so I can't say when it broke. Setup: My client system is Fedora 43 KDE. My VM host is Fedora 43 KDE. My VMs are networked with libvirt's NAT network type on the VM host. So, like this: Client --> RDM (SSH tunnel to VM host) --> Internet --> VM host (10/8) --> NAT --> VMs (192.168/16) I set up an SSH tunnel to get me to the VM host (10/8). Then I RDP into the VMs using the NAT'd addresses (192.168/16). When I launch the RDP connection, RDM crashes after ~5 seconds. The RDP connections are generic with no special options. The SSH tunnel is set to connect to the remote system, with an outgoing tunnel of dynamic mode and source ip:port of 127.0.0.1:3390. Are there any logs I can provide to help track this down? I have two systems that I can use this configuration with, both are broken. They were both previously working.

Greetings, After updating to the recently released version, I am no longer able to open any RDP connections. KRDC, Remmina working fine. Steps to reproduce: 1) Create a new RDP connection with default settings. 2) Observe that it doesn't work (Unable to connect to host <host>).

Hi guys, does RDP works? I've installed RDM from flatpak, it does not connect to any RDP session I add compared if I do the same in Windows, where it works fine. [image]

Hi guys, After last update of RDM all my opened tabs are going closed when I do an exit command or CTRL+D on a linux terminal. Is there any configuration to avoid it? Thanks!

Hi, I'm wondering if there is any chance to update the freerdp used by RDM to freerdp3. This is much better, from my point of view. Better graphics, better clipboard aso. If I configure it as external app, it works, but that is not what RDM is for. It would be great if it could be embedded in the main window. Kind regards Alexander (System is Kubuntu 24.10 with KDE Plasma 6.1.5, Wayland)

Problem: Starting any RDP session causes Remote Desktop Manager to immediately crash. OS: Arch Linux Last known good version: 2025.2.1.5 AUR Git commit hash: bc726c148d2681207126a5d49ce70770a1d42758 Affected versions: All versions after 2025.2.1.5 Steps to reproduce: Launch Remote Desktop Manager versions greater than 2025.2.1.5 on Arch. Start any RDP session. Observe that RDM crashes instantly. Additional information: Debug level is set to 1. No logs appear under Help → Application Logs when the crash occurs. This issue is consistent across all attempts with affected versions. If there are any tests you would like me to run, let me know.

This seems a bit of a weird one, but hopefully a solution can be found. I'm using the flatpak image from flathub, 2025.3.1.1 We use a official VPN client that has a very buggy linux package. This creates a 'gpd0' interface. When using this then RDM connects as expected to RDP, SSH etc. Theres an unofficial VPN client that creates a 'tun0' interface. None of the bugs of the official client and communication outside of RDM works fine - ping, traceroute, and browser to internal web services I've tested with KDE's KRDC which connects to RDP fine. This proves the VPN tunnel is correctly working. I've restarted RDM after establishing the VPN tunnel too incase RDM only queries at startup but no fix there either. So, Why is RDM having issues via the tun0 interface but accessing resources from other software working fine? Is there a setting i could change to allow this?

When i start RDM in plasma environment KDE fedora 43 all i see is blank window and no application. Does this have anything to do with new desktop environment that is using Wayland? Is Wayland supported with Plasma?