Some keys not recognized in OOD Remote Desktop

Get Help
1

The OOD Remote Desktop application fails to recognize the single quote, double quote, and tilde keys. This appears to impact solely Wayland-based Linux distributions and desktops. X11-based systems function adequately.

OOD Version is 4.1.4
Remote Desktop software is TurbVNC

What I have done so far to test the issue:

  1. • Conducted tests on four distinct machines:
    a) Two instances of KDE Neon (Plasma 6.7, based on Ubuntu 24.04), both fully updated and operating exclusively on Wayland across different networks.
    b) One instance of vanilla Ubuntu 24.04 with the Gnome desktop environment.
    c) One virtual machine hosted in our cloud environment, running Ubuntu 22.04 with X11 and XFCE4.

  2. • Tested on 5 different browsers:
    a) Chrome / XWayland (on 1a and 1b)
    b) Waterfox / XWayland (on 1a and 1b)
    c) Firefox / Wayland (on 1a and 1b)
    d) Falkon / Wayland (on 1a and 1b)
    e) Konqueror / Wayland (on 1a and 1b)
    f) Firefox / X11 (on c)

  3. Evaluated four distinct keyboards on machines 1a and 1b: the integrated keyboards of each device and external mechanical keyboards for both machines.

  4. On 1a, I tested different keyboard layouts on XFCE on the remote.

  5. On 1a, I changed the compression and quality settings on OOD to high compression, low quality. The initials were low compression (0) and high quality (works nicely on our network)

Results:

Consistently, on all Wayland-based systems, the keystrokes for double and single quotes, as well as the tilde, are not displayed, regardless of the operating system, hardware, browsers, or quality/compression settings. The X11-based virtual machine and an X11-based Arch Linux constructed by a colleague did not exhibit this issue.

My question
What are the requirements for an effective bug report? Please be advised that I am a user, not an administrator.

Looking forward to hearing from you,

Enric

Edit: I forgot to mention that I exclusively use US physical keyboards with US UTF-8 settings: $LANG = en_US.UTF-8

2

I think you’ve got a good start, but I wonder who’s bug it is? The flow would be noVNC -(over websockets) -> websockify -> Wayland.

I guess I would

  • confirm if it’s the same keycode/hex value being passed through noVNC for both Wayland and X11.

But beyond that I’d have to dig into the guts of websockify and Wayland.

That said - googling wayland not recognizing ' " or ~ characters does provide an answer - One answer for Gnome is to Change your layout from *English (US, intl., with dead keys)* to **English (US)**. There’s also a KEYMAP environment variable at play I guess.

3

Already done that.
I also use English US by default, on both, my 3 local machines and XFCE4 on the cluster.
I played around a few hours with that, but I can redo the tests to provide the results.

4

Seems like it would be a cluster/server setting, especially if it works on your X11 based systems.