mirror of
https://github.com/rustdesk/rustdesk.git
synced 2026-03-02 19:26:56 -05:00
Mac to Windows - Keyboard input not working #2272
Labels
No labels
bug
documentation
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
question
unreproducible
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/rustdesk-rustdesk#2272
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jbhewitt on GitHub (Nov 8, 2023).
Bug Description
No alphanumeric keyboard inputs working from a macOS installed rust desk 1.2.3 to a Windows machine.
The "meta" keys work (shift, ctrl, etc) but ABC123, etc does not register at all.
Works fine using TeamViewer or Anydesk, but RustDesk is currently not working.
How to Reproduce
Install Rustdesk 1.2.3 on macOS 14.1 and Windows 11 machine
On host Mac grant privacy Accessibility Keyboard access.
Connect to a windows client and try and type.
Expected Behavior
Keyboard inputs should be replicated on the client, but currently not working.
Operating system(s) on local side and remote side
macOS 14.1 -> Windows
RustDesk Version(s) on local side and remote side
1.2.3 -> 1.2.3
Screenshots
https://github.com/rustdesk/rustdesk/assets/98652/9b01a6a3-82a7-422d-8fb2-6cc660930379
Additional Context
I'm using an Australian Mac keyboard which is similar to US standard.
@rustdesk commented on GitHub (Nov 9, 2023):
Please try out different mode, https://github.com/rustdesk/rustdesk/wiki/FAQ#keyboard-translation-modes
@VHett commented on GitHub (Nov 9, 2023):
This just happened to me while trying to connect to a Windows Server. MacOS 13.6 and Windows Server 2020 both in German. Sending Ctrl-Alt-Del worked but I could not enter a password. Reinstalling Rust Desk solved the problem.
@jbhewitt commented on GitHub (Nov 9, 2023):
Updating the mac to 14.1.1 seems to have "fixed" the problem.
@rustdesk i did try switching keyboard modes in Rust and no changes happened
@jbhewitt commented on GitHub (Nov 12, 2023):
Happened again on macOS 14.1.1 ...... restarting the Mac seems to make it work - but it's bugging regularly
@beelchester commented on GitHub (Nov 12, 2023):
I tested a 90 min session Mac -> Windows (1.2.3 both) but could not reproduce this issue :(
For some reason, windows went to sleep at around 80 min but after starting back & reconnecting the keyboard input was still working.
https://github.com/rustdesk/rustdesk/assets/73148455/30b5973f-5903-4d37-a86e-4691fea06b5a
@jv2k4ever commented on GitHub (Nov 15, 2023):
Same bug keeps happening to me, albeit it fixes itself after restarting my Mac but ONLY after that. I have a MacBook Pro M2 Pro and I regularly connect to Linux VMs and Windows 10 machines. Sometimes if I close my lid or leave the Rustdesk screen open longer than an hour connected when I come back my Mac keyboard is not recognized on either VM or the local remote computers.
I have tried changing the Keyboard layout formatting , restarting Rustdesk, nothing works aside from physically restarting my Mac every time. It happens daily and is very frustrating
@jbhewitt commented on GitHub (Nov 15, 2023):
Yes for me this is happening on a daily basis now - incredibly frustrating.
Not sure if there is any further diagnostics I can do to assist.
@beelchester commented on GitHub (Nov 15, 2023):
https://github.com/rustdesk/rustdesk/issues/974
Please try:
And restart mac once.
@jbhewitt commented on GitHub (Nov 15, 2023):
Ok have tried this - will wait and see and report back
@jbhewitt commented on GitHub (Nov 16, 2023):
Unfortunately I did try these steps and after 24hours I'm having the same issue. Rustdesk won't work without me rebooting my Mac.
@jbhewitt commented on GitHub (Nov 22, 2023):
I'm not sure what next-steps to do here. We're paying for rustdesk pro - but if we can't find a stable solution for Macs it will be a challenge to continue
@beelchester commented on GitHub (Nov 23, 2023):
It seems like a rdev issue
https://github.com/Narsil/rdev/issues/74
https://github.com/Narsil/rdev/issues/59
https://github.com/Narsil/rdev/issues/86
They suggest it occurs only if we invoke listen/grab on a new thread
Doc:
@fufesou Can this part of the code be related to this issue?
github.com/rustdesk/rustdesk@34fa82f72c/src/keyboard.rs (L305-L311)@fufesou commented on GitHub (Nov 23, 2023):
Yes,
rdev::set_is_main_thread(false);is used to avoid the segment fault issue.@fufesou commented on GitHub (Nov 23, 2023):
But this issue doesn't seem to be a segfault.
@rustdesk commented on GitHub (Nov 23, 2023):
@fufesou take over this issue and dig out.
@rustdesk commented on GitHub (Nov 23, 2023):
@sahilyeole Thanks for your investigation.
@fufesou commented on GitHub (Nov 23, 2023):
@jbhewitt @jv2k4ever Sorry for frustrating
Can you please try rustdesk-1.2.4-x86_64.dmg here https://github.com/fufesou/rustdesk/releases/tag/tmp
It is built from the latest commit and there are no changes for this issue except some additional logs.
You can reproduce the issue using this build.
If you reproduce the issue, please attach the logs here.
I've been running RustDesk on "macOS -> Windows" but I'm not sure if I can reproduce it.
@ViniciusAndradex commented on GitHub (Nov 23, 2023):
Hi guys, I'm having this same problem in the current version of the code but in my case linux -> linux, even though the keyboard and mouse is enabled, the only thing that is working is the mouse.
I would like to take this opportunity to request this verification, I do not yet have enough knowledge to make this change on my own. Thanks.
@fufesou commented on GitHub (Nov 23, 2023):
@ViniciusAndradex Hi, which distro and version do you use on both sides?
Can you please try:
echo $XDG_SESSION_TYPEon both sides, to see if X11 or Wayland is used@ViniciusAndradex commented on GitHub (Nov 24, 2023):
@fufesou Sorry for the inconvenience, the error really was this Wayland issue, I hadn't seen it in the documentation. I made the change and it worked.
@jbhewitt commented on GitHub (Nov 25, 2023):
Heya I tried to download this and run it - but unfortunately it does not run on my Mac (for what it's worth I use a M1 based machine)
Translated Report (Full Report Below)
@fufesou commented on GitHub (Nov 25, 2023):
@jbhewitt Hi, maybe there're some issues with nightly build, on some machines like yours.
The temp build runs fine on @21pages 's and my machines.
Can you please try the nightly build? https://github.com/rustdesk/rustdesk/releases/tag/nightly
I'll build a version rustdesk-1.2.3-x86_64.dmg based on 1.2.3
https://github.com/fufesou/rustdesk/releases
https://github.com/fufesou/rustdesk/actions/runs/6987440509/job/19013986153
@fufesou commented on GitHub (Nov 25, 2023):
RustDesk should work fine on Wayland.
I've tested both 1.2.3 and the latest ngihtly version (both Ubuntu 22.04.3, Wayland), they work fine.
@ViniciusAndradex Hi, can you please give more details?
@jbhewitt commented on GitHub (Nov 25, 2023):
Hi team,
I have downloaded the nightly and unfortunately I am seeing the same error.
@fufesou commented on GitHub (Nov 25, 2023):
@jbhewitt Thanks for you feedback.
Can you please also try this build?
If you reproduce the issue, please attach the logs here.
@fufesou commented on GitHub (Nov 25, 2023):
@jbhewitt Hi, did you use the M1 based machine when you see this issue?
Have you ever run RustDesk on the M1 based machine before?
https://github.com/rustdesk/rustdesk/discussions/3683#discussioncomment-6212995
I'm not sure if CPU architecture matters. Maybe we need a new github workflow if possible.
@rustdesk commented on GitHub (Nov 25, 2023):
You can run x86 on M1 after turning on Rosetta, https://support.apple.com/en-sg/HT211861
@fufesou commented on GitHub (Nov 27, 2023):
@jbhewitt @jv2k4ever Sorry for disturbing again.
But can you please try https://github.com/rustdesk/rustdesk/issues/6335#issuecomment-1824589128
For the "Library not loaded" error, please refer to the previous comment.
I tried mac -> win these days, but failed to reproduce this issue.
@ViniciusAndradex commented on GitHub (Nov 27, 2023):
@fufesou Sorry for the delay, I only work with the project on the company's machines.
What OS and version do you use on both sides?
1. Ubuntu 22.04.3 and 22.04.2
Which version of RustDesk do you use on both sides?

2. I tested on 1.2.3 and 1.2.4 in both cases I had a problem with wayland. In this case, one of the machines is X11 and the other is wayland. The machine that has Wayland can make the connection but cannot write with the keyboard, while the machine that has X11 cannot even connect. I'll share the image of the error.
It is even possible to make connections without problems from 1.2.3 to 1.2.4 and vice versa, as long as both are on x11.
Can you please switch the controlling sides?
3. Yes, the test was done. Fall into the same questions as above
Or use X11 on one side and Wayland on the other side,
4. Yes, as stated in the second item regarding certain problems.
Or use another machine to check if the issue is from the control side or the controlled side.
@fufesou commented on GitHub (Nov 27, 2023):
@ViniciusAndradex Thanks for your detailed feedback.
https://github.com/flatpak/flatpak/issues/2446#issuecomment-448618648
Can you please run
It's wired that
grep xdg-desktop-portalshould be installed properly on Ubuntu22 default Desktop.There seems to be sth wrong on your Wayland desktop env.
For the input issue:
RustDesk uses flutter
Focus->onKeyhttps://api.flutter.dev/flutter/widgets/Focus/onKey.html to grab key events.There seems to be a problem here too. (Maybe the same Wayland desktop env problem)
@creuter27 commented on GitHub (Nov 28, 2023):
Same issue here running 1.2.3 on M1 Macbook Pro.
It happens after running fine for some days and then suddenly out of the blue, it doesn't accept any keys anymore. Very frustrating.
Most times when it happens it works again without a restart after removing and re-adding Rustdesk in the security settings but sometimes a full reboot is the only cure.
I've had this issue from day one when I started using Rustdesk on the Macbook. That was more than a year ago and it is super frustrating that this is still unresolved.
How can I install the Intel - version on my M1 so I can try with Rosetta?
@rustdesk commented on GitHub (Nov 28, 2023):
Thanks for your this mention, we are getting a solution.
@ViniciusAndradex commented on GitHub (Nov 28, 2023):
@fufesou

The commands failed and I couldn't resolve it but searching for these names in the general list they weren't found, I did the same connection test for a Macbook and everything went well, both X11 and Wayland.
@beelchester commented on GitHub (Nov 28, 2023):
@ViniciusAndradex
It should have been pre-installed I think but try manually installing
xdg-desktop-portal&xdg-desktop-portal-gtkusing apt@intoku commented on GitHub (Nov 28, 2023):
After update on the Montrey Mac(1.2.3)->Windows i also experienced similar keyboard issues. Also that the keyboard page has changed to QWERTY (im using QWERTZ) - and im unable to change it anywhere. Only "Legacy mode" is there, and no other options;
@fufesou commented on GitHub (Nov 28, 2023):
@intoku Thanks for your feedback.
Do you also use M1?
Do you use 1.1.9 on the remote side(Windows)?
Please follow these steps to enable the input grabbing https://github.com/rustdesk/rustdesk/issues/6335#issuecomment-1813728446
If you have the same issue. We're working on it.
Can you please try https://github.com/rustdesk/rustdesk/issues/6335#issuecomment-1824589128 , and give us more feedbacks?
Please install at least 1.2.3 on the remote side.
@jbhewitt commented on GitHub (Nov 28, 2023):
I am struggling getting the nightlies to work on my Mac - each one crashes including the 1.2.3 custom version you shot me :(
@rustdesk commented on GitHub (Nov 29, 2023):
Have two fixes https://github.com/rustdesk/rustdesk/pull/6561
#1 fix: you can try out
input source 2.#2 fix: may fix the problem of
input source 1(the input source you are using now), but not sure.@jbhewitt commented on GitHub (Nov 30, 2023):
@rustdesk keen to try out - but I'm unsure how to build a copy with the input sources feature 😨
@intoku commented on GitHub (Dec 1, 2023):
No, macbookpro 2016
@rustdesk commented on GitHub (Dec 2, 2023):
Close as fix merged, will reopen if anymore report again with the latest nightly build.