Crashing upon starting RDP session

Crashing upon starting RDP session

avatar

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:

  1. Launch Remote Desktop Manager versions greater than 2025.2.1.5 on Arch.
  2. Start any RDP session.
  3. 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.

All Comments (6)

avatar

Hello Kyle,

Can you try launching Remote Desktop Manager with this environment variable set? This should print more RDP-related details in the terminal.

WLOG_LEVEL=DEBUG remotedesktopmanager

Best regards,

Simon Duguay Létourneau

avatar

Alright, interesting findings.


I updated and tested on version 2025.3.1.1:

Lauch via .desktop file:

  • crash upon launching RDP session.


Launch via terminal using remotedesktopmanager which is /usr/bin/remotedesktopmanager

  • crashes upon launching RDP
  • terminal output.
[10:21:33:980] [3677221:003823a2] [WARN][com.freerdp.core.rdp] - [log_build_warn_cipher][0x7fb36000fcd0]: *************************************************
[10:21:33:980] [3677221:003823a2] [WARN][com.freerdp.core.nego] - [nego_enable_aad]: This build does not support AAD security, disabling.

(RemoteDesktopManager:3677221): Gtk-WARNING **: 10:21:33.985: 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:3677221): Gtk-WARNING **: 10:21:33.985: 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


Launch via WLOG_LEVEL=DEBUG remotedesktopmanager

  • Able to launch RDP sessions without crashing.



Additional Info:

  • RDP session goes through a proxyjump host/gateway. Connecting to the proxyjump host directly without activating a RDP session does not crash RDM at all.


GTK Version: Version : 1:3.24.51-1

avatar

Just a update. I have since tried just running WLOG_LEVEL=DEBUG remotedesktopmanager on version 2025.3.1.1. And I still got crash. It does not happen I'd say it happens about 50% of the time now upon opening a RDP session.

here is the terminal output. I also am not seeing any log get created.

[10:08:41:954] [1302725:001418bd] [DEBUG][com.freerdp.core.rdp] - [rdp_client_transition_to_state][0x7f5a4800cf20]: CONNECTION_STATE_INITIAL --> CONNECTION_STATE_NEGO
[10:08:41:954] [1302725:001418bd] [DEBUG][com.freerdp.core] - [freerdp_tcp_is_hostname_resolvable]: resetting error state
[10:08:41:955] [1302725:001418bd] [DEBUG][com.freerdp.core] - [freerdp_tcp_default_connect]: resetting error state
[10:08:41:955] [1302725:001418bd] [DEBUG][com.freerdp.core] - [freerdp_tcp_default_connect]: connecting to peer ::1
[10:08:41:955] [1302725:001418bd] [DEBUG][com.freerdp.core.nego] - [nego_connect]: state: NEGO_STATE_NLA
[10:08:41:955] [1302725:001418bd] [DEBUG][com.freerdp.core.nego] - [nego_attempt_nla]: Attempting NLA security
[10:08:41:955] [1302725:001418bd] [DEBUG][com.freerdp.core.nego] - [nego_send_negotiation_request]: RequestedProtocols: [SSL|HYBRID][0x00000003]

(RemoteDesktopManager:1302725): Gtk-WARNING **: 10:08:41.965: 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:1302725): Gtk-WARNING **: 10:08:41.965: 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) WLOG_LEVEL=DEBUG remotedesktopmanager

avatar

Hello Kyle,

I’m not sure why you’re seeing the Gtk-WARNING: Invalid text buffer iterator message.

Does it only appear when launching an RDP session? Also, are you using the performance profiler under Help → Performance profiling?

Regards,

Simon Duguay Létourneau

avatar

@Simon Duguay Létourneau

Does it only appear when launching an RDP session?


Yes. I can launch a tunnel, and a ssh connection to a gateway without issue, only upon launching a RDP session.

Also, are you using the performance profiler under Help → Performance profiling?


I am not. This is the output from the terminal window that I am launching RDM from. I have just tried to use the Performance profiling, and upon running it, I saw a few messages regarding openvpn. The same messages I see on version 2.1.5 that works.

Here is a portion of the terminal output, that appears on version 2.1.5, this is where the crash is happening on newer versions, but continues on without issue on 2.1.5.

[12:44:11:987] [1933977:001d82fb] [DEBUG][com.freerdp.core.nego] - [nego_connect]: state: NEGO_STATE_NLA
[12:44:11:987] [1933977:001d82fb] [DEBUG][com.freerdp.core.nego] - [nego_attempt_nla]: Attempting NLA security
[12:44:11:987] [1933977:001d82fb] [DEBUG][com.freerdp.core.nego] - [nego_send_negotiation_request]: RequestedProtocols: [SSL|HYBRID][0x00000003]
[12:44:11:085] [1933977:001d82fb] [DEBUG][com.freerdp.core.nego] - [nego_process_negotiation_response]: RDP_NEG_RSP::flags = { [0x1f] |EXTENDED_CLIENT_DATA_SUPPORTED|DYNVC_GFX_PROTOCOL_SUPPORTED|RDP_NEGRSP_RESERVED|RESTRICTED_ADMIN_MODE_SUPPORTED|REDIRECTED_AUTHENTICATION_MODE_SUPPORTED }
[12:44:11:085] [1933977:001d82fb] [DEBUG][com.freerdp.core.nego] - [nego_recv]: selected_protocol: [HYBRID][0x00000002]
[12:44:11:085] [1933977:001d82fb] [DEBUG][com.freerdp.core.nego] - [nego_attempt_nla]: state: NEGO_STATE_FINAL
[12:44:11:085] [1933977:001d82fb] [DEBUG][com.freerdp.core.nego] - [nego_connect]: Negotiated [HYBRID][0x00000002] security
[12:44:11:085] [1933977:001d82fb] [DEBUG][com.freerdp.core.nego] - [nego_try_connect]: nego_security_connect with PROTOCOL_HYBRID
[12:44:11:258] [1933977:001d82fb] [DEBUG][com.freerdp.core.nla] - [nla_set_early_user_auth]: Early User Auth active: false
[12:44:11:258] [1933977:001d82fb] [DEBUG][com.freerdp.core.nla] - [nla_set_state]: -- NLA_STATE_INITIAL	--> NLA_STATE_INITIAL
[12:44:11:258] [1933977:001d82fb] [DEBUG][com.winpr.sspi] - [InitSecurityInterfaceExA]: InitSecurityInterfaceExA
[12:44:11:258] [1933977:001d82fb] [DEBUG][com.freerdp.core.auth] - [credssp_auth_init]: Using package: Negotiate (cbMaxToken: 12256 bytes)
[12:44:11:258] [1933977:001d82fb] [DEBUG][com.freerdp.core.auth] - [credssp_auth_setup_client]: Acquired client credentials
[12:44:11:258] [1933977:001d82fb] [DEBUG][com.winpr.sspi.NTLM] - [ntlm_change_state]: change state from NTLM_STATE_INITIAL to NTLM_STATE_INITIAL
[12:44:11:258] [1933977:001d82fb] [DEBUG][com.winpr.sspi.NTLM] - [ntlm_change_state]: change state from NTLM_STATE_INITIAL to NTLM_STATE_NEGOTIATE
[12:44:11:258] [1933977:001d82fb] [DEBUG][com.winpr.sspi.NTLM] - [ntlm_write_negotiate_flags]: Write flags [0xe20882b7] NTLMSSP_NEGOTIATE_UNICODE|NTLMSSP_NEGOTIATE_OEM|NTLMSSP_REQUEST_TARGET|NTLMSSP_NEGOTIATE_SIGN|NTLMSSP_NEGOTIATE_SEAL|NTLMSSP_NEGOTIATE_LM_KEY|NTLMSSP_NEGOTIATE_NTLM|NTLMSSP_NEGOTIATE_ALWAYS_SIGN|NTLMSSP_NEGOTIATE_EXTENDED_SESSION_SECURITY|NTLMSSP_NEGOTIATE_VERSION|NTLMSSP_NEGOTIATE_128|NTLMSSP_NEGOTIATE_KEY_EXCH

avatar

Hello,

Thanks a lot for the detailed testing and logs this is really helpful.

At this point, the developer would like to get a core file from the crash. This will allow us to better understand exactly what’s happening at the moment Remote Desktop Manager crashes when starting an RDP session.

I’ll be sending you a SafeLink via private message that you can use to upload the dump file securely.

If anything is unclear while generating the dump, feel free to let us know and we’ll be happy to help.

Thanks again for your cooperation it’s very appreciated.

Best regards,

Carl Marien