Sorry, I don't have a solution. Only things I can say:<br><br>1. When I VNC'd to VM's managed by ESX, I experienced something similar (but with the tab key, not the parenthesis). Simply put, tab did not work via VNC. If I did Remote Desktop, no problems. My guess is that I simply had too many of virtuality that the combo of the products was simply imature to handle all.<br>
<br>2. Sometimes I would VNC to a Linux (RHEL) host and then simply telnet to my target VM. In such way I was able to bypass limitations. (Of course, if that VM was Windows, scratch that...)<br><br>3. I saw cases where restarting vncserver helped move things in the right way (but I can't remember the specifics).<br>
<br>Sorry that's all I've got. Best of luck.<br><br clear="all">-- Asher <br>
<br><br><div class="gmail_quote">On Tue, Jul 21, 2009 at 9:34 AM, JK <span dir="ltr"><<a href="mailto:jknapka@kneuro.net">jknapka@kneuro.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi folks,<br>
<br>
I need a ticket for the clue train...<br>
<br>
Yesterday I upgraded by Ubuntu 8.10 box to Ubuntu 9. It all went well.<br>
<br>
I've noticed a weird issue, though. I run several virtual Windows machines<br>
in VirtualBox. When I connect to the Ubuntu host machine via VNC and then<br>
try to interact with one of the virtual machines, the keyboard acts strangely.<br>
Specifically, I cannot type paren characters ()! Those keys simply do<br>
nothing at all when (a) typed over the VNC connection, and (b) the foreground<br>
window on the server is a VirtualBox VM window. Which is a PITA, since<br>
I am trying to write code on one of the virtual machines, and those<br>
characters therefore take on a disproportionate importance.<br>
<br>
If I connect to the same VM using the Remote Desktop server provided<br>
by VirtualBox, I don't have this problem. I also don't have it when connecting<br>
via VNC *directly* to the VM (that is, both the host OS and the guest OS<br>
are running VNC, and I only have the problem when connecting to the<br>
host and interacting with the VirtualBox window on the host machine's<br>
desktop).<br>
<br>
I don't have any idea where to even begin looking for a solution to<br>
this. There don't seem to be any keyboard-related options in either<br>
the VNC or VirtualBox configurations that look relevant, so I'm<br>
wondering if it could be something related to the X keyboard mapping.<br>
However, I *do not* have any problem when interacting with the<br>
VMs when I'm physically at the host machine, so that seems unlikely.<br>
<br>
Google says some vague things about keyboard layout settings in<br>
VirtualBox, but nothing very helpful.<br>
<br>
This problem definitely seems to have started with the upgrade<br>
to Jaunty. I know I could successfully type parens last week.<br>
<br>
Any ideas?<br>
<br>
Thanks,<br>
<font color="#888888"><br>
-- JK<br>
_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
</font></blockquote></div><br>