This should correctly be listed as an issue with tsclient. I am changing
the affected project now.
To reproduce (in Ubuntu Hardy beta using US english settings):
Go to System > Preferences > Keyboard
click Layouts tab and then click Layout Options button below
In the dialog window that opens, expand Ctrl key position
click "swap ctrl and CapsLock" (or probably any other non-default option)
test locally that the keys have been swapped
open tsclient and log on to Windows server
test the control key behavior. You should find that it is very screwed up. I
have seen several different scenarios. My current one is that the old capslock
(which is the ctrl key at the client now) is not the ctrl key nor the caps lock
key at the server. The right ctrl key doesn't work on the server at all and
the left ctrl key (which is correctly acting as the capslock on the client) is
back to being a ctrl key on the remote server.
With other keyboard layout options (such as make capslock an addtitional
ctrl key) I have found that none of the keys will send a ctrl signal to
the server.
** Also affects: tsclient
Importance: Undecided
Status: New
** Summary changed:
- Control key not sent to Windows Server by rdesktop
+ Incorrect keys sent to Windows Server by tsclient
** Tags added: keyboard layout server terminal tsclient
--
Incorrect keys sent to Windows Server by tsclient
https://bugs.launchpad.net/bugs/210094
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
