Forum / NoMachine for Mac / Mac -> Linux Keyboard layout problems
Tagged: Apple Keyboard
- This topic has 12 replies, 3 voices, and was last updated 8 months, 2 weeks ago by cjw34882e.
-
AuthorPosts
-
March 4, 2023 at 18:30 #43207inortonParticipant
Hi, I have the latest NoMachine client on my Mac and the latest server on my Linux desktop. I also have a Windows desktop client with the latest software but have a problem with one single key not working correctly from my Mac client.
I have a KVM setup for my two client machines so they both share the same keyboard.
My keyboard is a USB 102 key UK QWERTY keyboard.
All keys on the keyboard work correctly on local Mac and Windows. I can correctly type all keys into native Windows/Apple apps on both machines and get the correct keys.
On my Linux machine, I have the keyboard layout set correctly to the same 102 key UK English layout.
If I connect from Windows to my Linux NX server. All keys work correctly.
If I connect from my mac to my Linux NX server, all keys except the backslash key (bottom left key between shift and Z) work.
From the Mac, when I press this key, it sends the exact same keystroke as the backtick key (key on the top row to the left of “1”).
I have tried many different keyboard mappings on the server, but NoMachine never sends that keystroke as a unique key, it is always the same values as for the top left key with and without shift.
I suspect this is an Apple input problem rather than a server problem.
March 6, 2023 at 18:06 #43234inortonParticipantPlease see attached screenshots of keyboard events coming from the Mac client and the Windows client.
Attachments:
March 7, 2023 at 09:51 #43253BritgirlKeymasterHi, thanks for the screenshot. The second one failed to upload, could you send it to forum[at]nomachine[dot]com and I will add it separately. Thanks!
March 8, 2023 at 20:04 #43299inortonParticipantattach screenshot with mac client output
Attachments:
March 8, 2023 at 20:19 #43301inortonParticipantHi, I’ve done some more experimentataion today. And can confirm that from my mac, using my external keyboard, no matter what keyboard map is selected on the server, the mac client always sends the same key codes for those two keys.
The keys correctly produce different keystrokes in all other mac applications.
March 8, 2023 at 22:01 #43304inortonParticipantHi again, in the last few mins I’ve been able to check everything from my Mac using xrdp and the Mac microsoft RDP client. So I can confirm that my Mac client and my Linux desktop have the correct keyboard settings and all the keys work correctly, its only NoMachine that is having this issue. I’d much prefer to use NX instead of XRDP as it is much faster but I can’t really work well without a pipe key
March 9, 2023 at 09:14 #43313BritgirlKeymasterI sent you an email requesting output (for the file that didn’t attach, I am not sure if was a txt file or an image), anyway, we no longer need it.
The problem you are encountering is known. There is an API on Mac that the player (but also the agent, when the Mac is on server side) calls to detect if the keyboard is ISO or ANSI. These two keyboard types only differ in one key, the one that you report that is not working.
In some cases we observed that this API reports the wrong information. We are currently investigating possible solutions.
Can you tell us the exact keyboard model you are using on the Mac client-side?March 23, 2023 at 12:20 #43559inortonParticipantHi, I’m using a standard 102 key UK-English USB PC keyboard.
March 27, 2023 at 07:52 #43590inortonParticipantAre you planning to allow users to manually specify that value?
May 17, 2023 at 18:17 #44295inortonParticipantHi, is there any ETA on a fix or workaround for this?
thanks
May 29, 2023 at 18:00 #44449BritgirlKeymasterCheck your inbox inorton 🙂
April 11, 2024 at 10:40 #47691BritgirlKeymasterWe investigated with the specific logitech keyboard and opened the Trouble Report here https://kb.nomachine.com/TR02V11091. It will be in the next maintenance release.
April 13, 2024 at 15:56 #47757cjw34882eParticipantI’m encountering the same problem, but the solution/workaround from the KB does not solve the issue.
-
AuthorPosts
This topic was marked as solved, you can't post.