Updates?

Hello,
We already have a beta opened and we are about to release a new preview.

https://blog.devolutions.net/2020/02/get-an-early-access-preview-of-remote-desktop-manager-for-linux

Regards

Hi David,

I'm already part of the early access preview (and filed a bunch of bugs/feature requests), I was just wondering if there were going to be any updates for that release or if the next release we'll see are the june preview. Is there a changelog for the next release you can share? Wondering when we'll see SSH connections and private vault configs (which are the minimums I'll need to not have to use my RDM Wine install anymore)

Hi tmashos

There probably won't be an official changelog for the upcoming preview build but, spoilers, SSH Shell entries will be supported (some advanced feautres might be missing but basic SSH should be working) and you should be able to use your private vault's connections.

Regards

Sorry for my confusion. The next release (expected this later this week or maybe early next week) will contain this.. oups Jo was faster than me

Nice, thanks for the info guys!

Was the release pushed back or did I miss the announcement/email?

You didn't miss it.
We are ironing out some quirks. It should drop very soon.

I just installed the linux preview and so far it looks good. However, I have a question about the preview. If I connect to an existing SQL database, should I be able to open a session in that datasource? So far, when I attempt to open anything, RDM closes unexpectedly without error. I can create and open an RDP session just fine so far.

So far we support RDP, VNC and ARD sessions.
SSH will be in the upcoming preview that will be released soon.

Other session types will not work but shouldn't crash the app either.
If you run RDM in a terminal by launcher remotedesktopmanager, you should get a callstack.
Could you post it here please?

@tom_minerd

Make sure you are clicking on the server then clicking the open session button on the right (rather than right clicking on the server and trying to open it from there). I logged a bug on that earlier.

It always happens when I click the session. I don't get a chance to click open session as RDM crashes.

Here's what I got when starting from the terminal:

(RemoteDesktopManager:5795): GLib-GObject-CRITICAL **: 15:59:59.926: g_signal_connect_data: assertion 'c_handler != NULL' failed

(RemoteDesktopManager:5795): GLib-GObject-CRITICAL **: 15:59:59.965: g_signal_connect_data: assertion 'c_handler != NULL' failed

(RemoteDesktopManager:5795): GLib-GObject-CRITICAL **: 15:59:59.971: g_signal_connect_data: assertion 'c_handler != NULL' failed

(RemoteDesktopManager:5795): Gtk-CRITICAL **: 16:00:00.169: gtk_tree_store_iter_has_child: assertion 'iter->user_data != NULL' failed

Have you tried again running RDM Linux 2020.2.0.0?
The download is now available on our website.

If it's still happening in 2020.2.0.0, would it be possible for you to export your session (without any sensitive information) and send it to me?

With the latest version,RDM doesn't crash. However, from the SQL datasource, I am unable to launch an RDP session. It's possible that it may be the way it is set up that is not supported since I am using a credential repository to launch the session.

With the latest version,RDM doesn't crash. However, from the SQL datasource, I am unable to launch an RDP session. It's possible that it may be the way it is set up that is not supported since I am using a credential repository to launch the session.

FWIW, I use a SQL data source and private vault credentials and it works

I'm actually using Private Vault credentials through Private Vault search. However, in the linux version of RDM, you cannot type in a Private Vault Search string which may be why it's failing.

Yep, I'm using private vault search here too.

Then it has to be some other setting for my RDP session that won't allow it to connect. It tries to open the session but then fails.

If properly configured (like in your case on another version of RDM) then even though the UI is missing, our backend should still be able to resolve your credentials.
RDM Linux doesn' yet support RDP debug logging (I'll address that) but you should still be able to get some logs from the console.
If you launch RDM in a terminal, do you have any error message related to RDP?

I was getting NLA errors in the terminal. I had to uncheck that option to get the session to connect. It's working now.

Glad it now works.
I'll take a look nonetheless.
Tha's something we should be able to detect and fix on fly so you don't have to change all your sessions.