VirtualBox

Ticket #2263 (closed defect: fixed)

Opened 1 year ago

Last modified 1 year ago

Some keys on Japanese keyboard are not recoginzed on Solaris host.

Reported by: sayama Assigned to:
Priority: major Component: other
Version: VirtualBox 2.0.2 Keywords:
Cc: Guest type: other
Host type: Solaris

Description

VirtualBox2.0.0 improved the problem that some keys on localized keyboard are not recognized. However, some keys on Japanese keyboard are not worked correctly on Solaris yet because the meaning of key code is bit different. I tried to test it on OpenSolaris? nv_97 with using xev command.

  • <Katakana/Hiragana> key is recogized as <Kanji>
  • <Henkan> key and <Muhenkan> key are not recogized.

I looked the file under src/VBox/Frontends/VirtualBox4/src/linux/keyboard-types.h and found that these are not correctly mapped. I created the patch for this issue and attached it. Could you please merge it if it is OK?

Attachments

VBoxKeyboard-jp106-sun.patch (0.9 kB) - added by sayama on 2008-09-18 03:53:45.
Patch for this problem

Change History

2008-09-18 03:53:45 changed by sayama

  • attachment VBoxKeyboard-jp106-sun.patch added.

Patch for this problem

2008-09-18 06:37:00 changed by sayama

I should have added the different keycode information between Xorg on Solaris and Xorg on Linux. Here is the table for this and I created the patch based on it.

Xorg on SolarisXorg on Linux
Katakana/Hiragana (AT scan=70)keycode=129keycode=208
Muhenkan (AT scan=7B)keycode=139keycode=131
Henkan (AT scan=79)keycode=138keycode=129

2008-09-18 09:41:38 changed by michael

Thanks for your patch. This is already fixed in a different way for VirtualBox 2.1, but I will include your patch (which is a less invasive change) in the stable 2.0.4 release, if we do one. Could you please just confirm that your patch is MIT-licenced to keep the legal people happy?

2008-09-18 12:35:58 changed by sayama

It's good news that this is already fixed in VirtualBox 2.1 and my patch will be included in 2.0.4 release. Thank you very much for your good information. Yes, I confirm that it is MIT-licenced.

2008-09-19 15:28:00 changed by michael

  • status changed from new to closed.
  • resolution set to fixed.

Done. Thanks a lot.


Contact – Privacy policy