Fedora 43 KDE, RDM flatpak, RDM crashes when leveraging an SSH tunnel to connect to a remote RDP system

Backlog

Fedora 43 KDE, RDM flatpak, RDM crashes when leveraging an SSH tunnel to connect to a remote RDP system

avatar

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:

  1. My client system is Fedora 43 KDE.
  2. My VM host is Fedora 43 KDE.
  3. My VMs are networked with libvirt's NAT network type on the VM host.
  4. So, like this: Client --> RDM (SSH tunnel to VM host) --> Internet --> VM host (10/8) --> NAT --> VMs (192.168/16)
  5. I set up an SSH tunnel to get me to the VM host (10/8).
  6. Then I RDP into the VMs using the NAT'd addresses (192.168/16).
  7. 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.

All Comments (7)

avatar

Hello,

Thank you for the detailed description of your setup .

To help us narrow this down, could you please try the following:

  1. Test with the RPM build If possible, please install Remote Desktop Manager using the .rpm package and test the same connection using the SSH tunnel.
  • Let us know whether the crash also occurs with the RPM build, or if it only happens with the Flatpak version.


  1. Collect console logs Please try launching Remote Desktop Manager from a terminal so we can review any error output: remotedesktopmanager


If the application crashes, please copy and send us the terminal output.

This will help us determine whether the issue is specific to the Flatpak runtime or affects Linux builds in general.

Thank you for your cooperation, and we’ll continue investigating as soon as we have this information.

Best regards,

Carl Marien

avatar

Greetings,

I have tested the RPM build, same issue.


There appears to be 2 issues here.

  1. The crashing.
  2. With the RPM version, sometimes when I attempt to connect to my RDP session (via the SSH tunnel connection that auto-launches), it says there was a connection error, like I'm using the wrong address.


To get these messages, I had to start the SSH tunnel manually, then start the RDP session, otherwise I was just getting the connection error message. Though on my first try of the RPM version, it crashed upon launching only the RDP session. It is not consistent.

Here is the console log:

$ remotedesktopmanager
[13:45:11:353] [92481:00016b93] [INFO][Devolutions.Rdp.Credentials] - [Parse]: parsing "a*******", "" (Mstsc) => "Username: "a*******" Domain: """
[13:45:11:356] [92481:00016b93] [ERROR][com.freerdp.channels.virtual.channel] - [virtchan_virtual_channel_init_event_ex]: Unhandled event type 0
[13:45:11:356] [92481:00016b93] [ERROR][com.freerdp.channels.virtual.channel] - [virtchan_virtual_channel_init_event_ex]: Unhandled event type 0
[13:45:11:356] [92481:00016b93] [ERROR][com.freerdp.channels.virtual.channel] - [virtchan_virtual_channel_init_event_ex]: Unhandled event type 0
[13:45:11:359] [92481:00016b93] [ERROR][com.winpr.library] - [LoadLibraryA]: failed with libopenh264.so.7: cannot open shared object file: No such file or directory
[13:45:11:359] [92481:00016b93] [ERROR][com.winpr.library] - [LoadLibraryA]: failed with libopenh264.so.2.5.0: cannot open shared object file: No such file or directory
[13:45:11:359] [92481:00016b93] [ERROR][com.winpr.library] - [LoadLibraryA]: failed with libopenh264.so.2.4.1: cannot open shared object file: No such file or directory
[13:45:11:359] [92481:00016b93] [ERROR][com.winpr.library] - [LoadLibraryA]: failed with libopenh264.so.2.4.0: cannot open shared object file: No such file or directory
[13:45:11:359] [92481:00016b93] [ERROR][com.winpr.library] - [LoadLibraryA]: failed with libopenh264.so.2.3.1: cannot open shared object file: No such file or directory
[13:45:11:359] [92481:00016b93] [ERROR][com.winpr.library] - [LoadLibraryA]: failed with libopenh264.so.2.3.0: cannot open shared object file: No such file or directory
[13:45:11:359] [92481:00016b93] [ERROR][com.winpr.library] - [LoadLibraryA]: failed with libopenh264.so: cannot open shared object file: No such file or directory
[13:45:11:359] [92481:00016b93] [WARN][com.freerdp.core.codecs] - [freerdp_client_codecs_prepare]: Failed to create h264 codec context
[13:45:11:392] [92481:00016b93] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x7f8ae000e370]: *************************************************
[13:45:11:392] [92481:00016b93] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x7f8ae000e370]: This build is using [runtime-check] build options:
[13:45:11:392] [92481:00016b93] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x7f8ae000e370]: * 'WITH_VERBOSE_WINPR_ASSERT=ON'
[13:45:11:392] [92481:00016b93] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x7f8ae000e370]: 
[13:45:11:392] [92481:00016b93] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x7f8ae000e370]: [runtime-check] build options might slow down the application
[13:45:11:392] [92481:00016b93] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x7f8ae000e370]: *************************************************
[13:45:11:392] [92481:00016b93] [WARN][com.freerdp.core.rdp] - [log_build_warn_cipher][0x7f8ae000e370]: *************************************************
[13:45:11:392] [92481:00016b93] [WARN][com.freerdp.core.rdp] - [log_build_warn_cipher][0x7f8ae000e370]: [SSL] {Cipher} build or configuration missing:
[13:45:11:392] [92481:00016b93] [WARN][com.freerdp.core.rdp] - [log_build_warn_cipher][0x7f8ae000e370]: * des-ede3-cbc: RDP security FIPS mode will not work
[13:45:11:392] [92481:00016b93] [WARN][com.freerdp.core.rdp] - [log_build_warn_cipher][0x7f8ae000e370]: *************************************************
[13:45:11:392] [92481:00016b93] [WARN][com.freerdp.core.nego] - [nego_enable_aad]: This build does not support AAD security, disabling.

(RemoteDesktopManager:92481): Gtk-WARNING **: 13:45:11.400: Invalid text buffer iterator: either the iterator is uninitialized, or the characters/pixbufs/widgets in the buffer have been modified since the iterator was created.
You must use marks, character numbers, or line numbers to preserve a position across buffer modifications.
You can apply tags and insert marks without invalidating your iterators,
but any mutation that affects 'indexable' buffer contents (contents that can be referred to by character offset)
will invalidate all outstanding iterators

(RemoteDesktopManager:92481): Gtk-WARNING **: 13:45:11.400: Invalid text buffer iterator: either the iterator is uninitialized, or the characters/pixbufs/widgets in the buffer have been modified since the iterator was created.
You must use marks, character numbers, or line numbers to preserve a position across buffer modifications.
You can apply tags and insert marks without invalidating your iterators,
but any mutation that affects 'indexable' buffer contents (contents that can be referred to by character offset)
will invalidate all outstanding iterators
Segmentation fault         (core dumped) remotedesktopmanager

avatar

Hello,

Thank you for sharing the logs. Unfortunately, they do not provide enough information to determine the cause of the crash.

To investigate this further, we will need a core dump from the time of the crash so our developers can analyze where the segmentation fault occurs.

If you are able to provide a core dump, please let us know and I will send you a secure link so you can safely share the file with us via private message.

Thank you for your cooperation and for your patience.

Best regards,

Carl Marien

avatar

Sure I can send anything you need - can you be a little more specific on where I'd find the necessary logs (or how to enable them), and where the core dumps go when they are generated?

avatar

Hello,

Please follow these steps:

1) Open a terminal and run:
ulimit -c unlimited && flatpak run com.devolutions.remotedesktopmanager

2) Recreate the issue, then locate the core dump using coredumpctl:
coredumpctl list --reverse | head

3) Export the dump to a file you can upload (replace <PID> with the crashing PID from the list):
coredumpctl dump <PID> > rdm.core

Best regards,

Carl Marien

avatar

Greetings,

I have uploaded a couple coredumps.

avatar

Hello,

Thank you for taking the time to generate and upload the core dumps we really appreciate it.

I’ve forwarded the core dump files and the console output to our development team so they can analyze the exact point where the segmentation fault occurs.
We’ll get back to you as soon as we have an update from them.

Best regards,

Carl Marien