Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Characters sent via Linux compose key are not processed #6784

Closed
Tracked by #4367
64kramsystem opened this issue Jan 3, 2024 · 1 comment
Closed
Tracked by #4367

Characters sent via Linux compose key are not processed #6784

64kramsystem opened this issue Jan 3, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@64kramsystem
Copy link
Contributor

64kramsystem commented Jan 3, 2024

Bug Description

Characters sent via Linux compose key are not processed.

When trying to compose one, I hear the error bell, and the character is not composed/sent on the remote side.

This is independent of the keyboard mode (I've tried both map and translate).

How to Reproduce

Assuming that:

  • both client and remote side are Linux
  • the compose key is Caps lock
  • trying to compose ä

The steps are (on a connected):

  1. tap Caps lock
  2. tap a
  3. the compose sequence is initiated (an underscore cursor will display)
  4. tap "
  5. the error bell will ring (probably this is on the client side), and the compose sequence is cancelled

Expected Behavior

On point (5), the character ä should be sent.

Operating system(s) on local side and remote side

Ubuntu -> Ubuntu

RustDesk Version(s) on local side and remote side

1.2.3 -> 1.2.3

Screenshots

(none)

Additional Context

No response

@64kramsystem 64kramsystem added the bug Something isn't working label Jan 3, 2024
@rustdesk
Copy link
Owner

rustdesk commented Jan 3, 2024

tracked by #4367

@rustdesk rustdesk closed this as completed Jan 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants