Opened 10 years ago
Closed 10 years ago
#13639 closed defect (wontfix)
Windows client does not respect linux host xmodmap settings -> working as designed
| Reported by: | Will Everett | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 4.3.16 |
| Keywords: | xmodmap, keyboard | Cc: | |
| Guest type: | Windows | Host type: | Linux |
Description
Under Debian I have xmodmap swap the left control and caps lock. When using a Windows 7 client, this swap is ignored by the client but still recognized by the host. So while the keyboard is captured by the W7 VM if I press the physical Ctrl_L+S keys (to save a document), it will save the document AND activate the caps lock. If I press the physical Caps_Lock+S keys, it will type a capital S (but will not activate caps lock on either host or client).
I have just noticed this problem as I don't use a remapped keyboard very often. I'm having the problem with 4.3.18 with a Debian Jessie host and Win 7 client, but here's a question on superuser where the person is using 4.3.16 with a Windows 8 client and it looks like he caught the bug more quickly.
Change History (1)
comment:1 by , 10 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
| Summary: | Windows client does not respect linux host xmodmap settings → Windows client does not respect linux host xmodmap settings -> working as designed |
I'm sorry, but this is working as designed. While we previously tried to get host keyboard remapping passed through to the guest correctly, we decided at some point that it was simpler and more consistent to just require the user to set up the guest keyboard correctly, as they must already do for the keyboard layout. If we did have proper keyboard layout pass-through then this would make sense, but we do not. I will update the StackExchange question too.