Opened 17 years ago
Closed 17 years ago
#1817 closed defect (fixed)
At least one key not working => fixed in the upcoming version
Reported by: | Craig Turner | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 1.5.6 |
Keywords: | Cc: | ||
Guest type: | other | Host type: | Linux |
Description
Running VB 1.5.6_OSE as downloaded from the available repositories in ubuntu Hardy Heron.
Have installed a windows 2000 server guest.
The three key on the top row of my keyboard seems to be ignored by the guest operating system. Using the key on the number pad of my keyboard does work however.
Have also tried with a Windows Vista guest, and the same problem is present in that.
Change History (6)
comment:1 by , 17 years ago
comment:2 by , 17 years ago
Are you using a German keyboard layout which produces a paragraph sign (¶) instead of a section sign (§) when you do shift-"3"? If so this will be fixed in the next version and you can work around it for now by changing to a different host layout (e.g. one with a section sign).
comment:3 by , 17 years ago
Host type: | other → Linux |
---|---|
Version: | VirtualBox 1.6.2 → VirtualBox 1.5.6 |
comment:4 by , 17 years ago
Note that it may be a while before Ubuntu provides the next version. It will be available as a binary Ubuntu package from virtualbox.org as soon as it is released of course.
comment:5 by , 17 years ago
No, i'm using a UK keyboard layout, although having tested it, I'm unable to type a pound sign using shift 3 on the host machine either, so it may be something to do with my settings in ubuntu.
comment:6 by , 17 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Summary: | At least one key not working → At least one key not working => fixed in the upcoming version |
If that key does not work properly in the host then it will not work in the guest either, as the way we currently determine which key is which is by looking at the symbols it produces with and without shift held down. (Unfortunately I don't know of any good way to work out which physical key produces which X11 keycode). The next version will contain a back up algorithm which should work correctly in your case. You can also fix this issue with your current version if you can fix your host layout.
My apologies. I selected the wrong version in the dropdown list. If someone could correct it, that would be appreciated.