Only usable Input method 2 - sends suspend or halt when using dead-keys (accents or ñ)

[jcsogo]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

I am connected to a Linux desktop remote client (either Lubuntu VPS or Linux Mint laptop), with a physical keyboard layout in Spanish in the computer accessing the linuxserver.io RustDesk image, both with Linux and Windows.

1. I have to use Input Source 2 - none of the methods of Input Source 1 works
2. The moment that I enter whatever deadkey combination (á é í ó ú) o the letter ñ, the remote is either shutdown (the VPS) or suspended (Linux Mint laptop). It is an instant 'halt'.

It is like any of these triggers the Alt+SysReq+B combination, or similar.

Expected Behavior

A letter should be entered.

Steps To Reproduce

1. Configure your keyboard layout to Spanish in the physical computer
2. Run RustDesk image
3. Connect through it to the remote
4. Issue whatever combination of deadkey letters or the letter ñ
5. The remote should suspend/halt

Environment

- OS: Linux Mint and Windows for the physical computer. Remotes are lubuntu and Linux Mint.
- Browser: Google Chrome
- How docker service was installed: docker compose in Debian LXC in Proxmox

CPU architecture

x86-64

Docker creation

rustdesk:
    image: lscr.io/linuxserver/rustdesk:latest
    container_name: rustdesk
    devices:
      - /dev/dri:/dev/dri
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/Madrid
      - PIXELFLUX_WAYLAND=true
      # Optional: Specify device if multiple exist (IE: /dev/dri/renderD129)
      - DRINODE=/dev/dri/renderD128
      - DRI_NODE=/dev/dri/renderD128
    volumes:
      - /opt/stacks/rustdesk:/config
    shm_size: "1gb"

Container logs

docker logs rustdesk doesn't show anything relevant to the problem

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[thelamer]

So how input works is it is universal, this makes it so the user does not need to configure the server in order to use their client keyboard layout.

But any non Latin character will be piped through a shell exec and wtype. What this means is that the character will type but you can't do key combos like ctrl+non Latin character.

We bypass this for Cyrillic by maintaining a map https://github.com/selkies-project/selkies/blob/lsio/src/selkies/input_handler.py#L145 , then when the user is sending a key combo we send the Latin equivalent.

So that leads me to AI existing and every container being an RDE (rapid development environment you change the code you see the change in the session) you can activate this with:

git clone https://github.com/selkies-project/selkies.git
cd selkies
git checkout -f lsio
docker run --rm -it \
  --shm-size=1gb \
  -e DEV_MODE=selkies-dashboard \
  -e PUID=1000 \
  -e PGID=1000 \
  -v $(pwd):/config/src \
  -p 3001:3001 ghcr.io/linuxserver/rustdesk bash

If you find what works, PRs are welcome.

[jcsogo]

I don't fully understand the proposal. Are you suggesting that every map layout will need a translation table? In addition, a solution that only allows to send regular characters won't work long term. Only is a patch to avoid the remote desktop to halt or be suspended, but in a regular use the use will need to be able to input dead-key combinations, as well as other characters in their keyboard.

This is something that was not a problem with kasmVNC.

[thelamer]

That is precisely my proposal, and you are free to maintain or ask Kasmtech to maintain a rustdesk image. I make the base as general purpose as I can with the tools that are available for Linux. I have prioritised things like speed, GPU acceleration, and server load VS running a remote desktop client in a remote session. Multi layer input oddities are not on my radar so I have tried to guide you to the path of fixing your specific issue and shown you how it is achieved with a Cyrillic layout.

[jcsogo]

Don't get me wrong. I will always thank anyone spending a minute on contributing to opensource as we all benefit from it. I was just kind of surprised on the approach. I understand that the issue comes from the layering of a remote session on a remote desktop client, and maybe the issue is not even on your side, but in rustdesk's.

Other images that are based on selkies work great, so it is just this one that breaks.