RDM on Debian 13, wrong keyboard layout

Same issue here, using a BE Azerty keyboard. Ubuntu setup as Azerty as well as the remote server. Tried changing the settings of the connecting under general => local resources => keyboard to force azerty and send input as unicode but neither worked. Only thing that works is rolling back to version 2026.2.2.2.

Tried same server from a windows machine with 2026.3.0.5 and this does work, so it is something linux/wayland based i'm guessing?

Hello,

This is a known issue in RDM for Linux 2026.3.0.5. Our development team has already received a bug report and is investigating it.

We will update this thread when more information or a fix becomes available.

Best regards,

Hi @Carl Marien

Is there an update on this topic or not yet? :)

Hello,

This issue has been fixed, and the correction is planned for RDM for Linux version 2026.3.1.0.

I will let you know as soon as the fixed version becomes available.

Best regards,

@Carl Marien

Thanks! :)

Hello,

Confirming the same issue with the Hungarian layout on Kubuntu (Wayland, RDM started with GDK_BACKEND=x11):
y/z swapped, 0 -> ö, - -> ü in RDP sessions on 2026.3.0.5.
2026.2.2.2 works fine, and xfreerdp3 with /kbd:layout:0x40E also types correctly.
Looking forward to 2026.3.1.0.

Gabor

Same issue here, with a Spanish (Latin American) layout.

Environment
- RDM Linux 2026.3.0.5 (AUR package), CachyOS (Arch), GNOME on Wayland (RDM runs under XWayland)
- Local layout: latam. Remote Windows layout: Spanish (Latin America)

Symptoms (embedded RDP tab)
- : (Shift+.) and ; (Shift+,) both type Ñ
- ? and other shifted symbols come out wrong
- Dead keys don't work: ´ + a types a instead of á

What I tried (none helped)
- Send input as Unicode = Yes, both per entry and globally
- Setting the entry keyboard layout explicitly
- Opening the session as External (xfreerdp3)

Regression confirmed: downgrading to 2026.2.2.2 fixes everything. All symbols and dead keys work correctly with the
same entries and the same remote host.

Likely cause: in 2026.3 the embedded RDP session is hosted in the new AvaloniaRdpSessionControl. It appears to build
the virtual key from the logical key (KeyEventArgs.Key, which depends on the produced symbol) and then send it as a
US-layout scancode. For example, : maps to VK_OEM_1, which is scancode 0x27, and that key is Ñ on a Spanish layout.
This path seems to ignore both the "Send input as Unicode" setting and the keyboard layout setting. The previous
GTK path sent the physical hardware keycode, which is why 2026.2 works. Using KeyEventArgs.PhysicalKey for every key
would probably fix it. The control already does this for Shift, Ctrl, Alt and Win.

For now I've pinned 2026.2.2.2.

Hello,

Thank you for the additional information and for confirming that you are experiencing the same issue.

The fix is planned for RDM for Linux 2026.3.1.0. I will keep you informed and update this thread as soon as the version containing the fix is available.

Thank you for your patience.

Best regards,

Confirmed its working in version 2026.3.1.1! Thanks @Carl Marien :)