Can anyone confirm whether this problem is related to the problem in tsclient where a custom keyboard layout sends the wrong keys to the Windows server?
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. -- Error message on ending VNC session https://bugs.launchpad.net/bugs/8422 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
