RDM Linux - Crash during clipboard operation

A fix for this issue has been implemented in version 2026.1.2.2
Implemented Performance

RDM Linux - Crash during clipboard operation

avatar

Hello,

This post is a follow-up to a crash reported separately from the sleep/resume issue in the original thread. The crash described here was observed while actively using an RDP connection, with no obvious trigger at the time, though clipboard activity had been occurring.

Symptom:
RDM aborts during or shortly after a clipboard set operation while an RDP session is active.

What the core dump shows:
The crash is a Signal 6 (ABRT), not a segfault. The crashing thread was executing RDM's clipboard code via the .NET runtime (libcoreclr.so), calling into gtk_clipboard_set_with_data through GTK/GDK/libX11/libxcb. At that point, glibc's memory allocator detected a corrupted heap chunk (tcache_get_n -> malloc_printerr -> abort).

This is a distinct crash from the sleep/resume one and is being tracked separately by the same user.
https://forum.devolutions.net/topics/52610/frequent-but-seemingly-random-segfaults?user=46946

Environment:
Product: Remote Desktop Manager for Linux
Version: 2026.1.1.1
Install type: .deb
OS: Linux (amd64)
Kernel: 6.17.0-20
glibc: 2.42

Thank you,

Carl Marien

All Comments (3)

avatar

Hello veehexx1,

I have opened a separate investigation for this crash and will attempt to reproduce it on my end.

If you have any steps that consistently or occasionally lead to the crash, sharing them would be very helpful in narrowing down the cause.

Best regards,

Carl Marien

avatar

Hello,

Good News !!!

We were able to reproduce the crash on our end and have escalated the issue to our development team for further investigation.

I will follow up as soon as I have an update from them.

Best regards,

Carl Marien

avatar

Hello,

Thank you for being so patient!

I'm pleased to inform you that a new version of RDM Linux (2026.1.2.2) 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

A fix for this issue has been implemented in version 2026.1.2.2