VirtualBox

Ticket #13216 (closed defect: fixed)

Opened 3 years ago

Last modified 3 years ago

Keyboard mapping missing Alt-Gr -> fixed in 4.3.x and later releases after 18 Nov 2014

Reported by: Korkman Owned by:
Priority: major Component: other
Version: VirtualBox 4.3.14 Keywords: keyboard
Cc: Guest type: Linux
Host type: Windows

Description

  • Host
    • German Keyboard Layout (probably others as well)
    • Windows 8.1
  • Guest
    • Ubuntu Trusty based Distro
      • Tested: Linux Mint 17 Xfce both live and installed
      • Tested: Distro Guest Additions 4.3.10
      • Tested: Uninstalled Distro Guest Additions, installed included 4.3.14
    • German Keyboard Layout

Alt-Gr key does not work, disabling Pipe- and At-symbols (very annoying). Included 4.3.14 Guest Additions seem to work on first boot only, any guest reboot disables Alt-Gr again.

Change History

comment:1 Changed 3 years ago by michael

Could anyone experiencing this please give the "keylook" tool attached to ticket #12138 a try and post the output that it gives when you press AltGr? It would also be great if you could check whether AltGr works for you before but not after a guest reboot.

comment:2 Changed 3 years ago by michael

I have also seen reports that releasing keyboard capturing makes AltGr work. Can people test this too? Anyone who provides information, please mention at least once which version of Windows you are using and what your host key is set to.

comment:3 Changed 3 years ago by michael

And anyone running an X11-based guest with AltGr problems please run xev in the guest and tell me what is says when you press AltGr.

comment:4 Changed 3 years ago by f456

host: win7 sp1 x64

keyboard: german notebook

guest: ubuntu 14.04, cinnamon desktop

xev:

one second

Last edited 3 years ago by f456 (previous) (diff)

comment:5 Changed 3 years ago by michael

f456: now I am slightly confused - that is almost identical to what I get on my Linux host (also German layout), and it looks like the guest is seeing the AltGr key press correctly. What symptoms of the problem are you seeing in the guest?

comment:6 Changed 3 years ago by dannyM

Same issue here. But AltGr+4 results in "1/4" and AltGr+5 in "1/5" - any many more of this...

xev gives:

KeyPress event, serial 37, synthetic NO, window 0x3a00001,
    root 0x173, subw 0x0, time 365159, (166,-12), root:(1029,400),
    state 0x10, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyPress event, serial 37, synthetic NO, window 0x3a00001,
    root 0x173, subw 0x0, time 365159, (166,-12), root:(1029,400),
    state 0x14, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES,
    XKeysymToKeycode returns keycode: 92
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyRelease event, serial 37, synthetic NO, window 0x3a00001,
    root 0x173, subw 0x0, time 365215, (166,-12), root:(1029,400),
    state 0x94, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyRelease event, serial 37, synthetic NO, window 0x3a00001,
    root 0x173, subw 0x0, time 365217, (166,-12), root:(1029,400),
    state 0x90, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES,
    XKeysymToKeycode returns keycode: 92
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False

comment:7 Changed 3 years ago by michael

dannyM: again, the same questions: which version of Windows are you using for a host, and does un-capturing the keyboard make things work?

comment:8 Changed 3 years ago by michael

Here is a test build which may just fix the issue. I have an idea as to what the problem might be, but given that I don't even have a Windows system handy to try this out on I do not even know if it will run. Be that as it may, feel free to give it a try.

https://www.virtualbox.org/download/testcase/VirtualBox-4.3.15-95141-Win.exe

comment:9 Changed 3 years ago by DasLeo

dannyM: again, the same questions: which version of Windows are you using for a host, and >does un-capturing the keyboard make things work?

Hi Michael,

I'm also having the same problem, but only on my Windows 8.1 u1 machine. On my Gentoo Linux it's working.

Here are the facts:

  • Disabling auto capture made AltGr to work
  • re-enabling auto capture made it to not work

I'm now downloading your testbuild and will give you response in a few minutes.

Last edited 3 years ago by DasLeo (previous) (diff)

comment:10 Changed 3 years ago by DasLeo

https://www.virtualbox.org/download/testcase/VirtualBox-4.3.15-95141-Win.exe

The test build fixed my problem. Thx Michael, I really needed the pipe symbol and backslash.

comment:11 Changed 3 years ago by pschneider1968

Hi Michael,

KEYLOOK.EXE output from host, Win7 Prof. 64bit SP1 + all current patches (keyboard is a plain ordinary Logitech K120):

WM_KEYDOWN 17 1 29 No No Up Down

WM_KEYDOWN 18 1 56 Yes Yes Up Down

WM_SYSKEYUP 17 1 29 No Yes Down Up

WM_KEYUP 18 1 56 Yes No Down Up

xev output from guest VM, CentOS 6.5 64bit, all current patches (in the VM, I can't compose any characters with AltGR):

KeyPress event, serial 33, synthetic NO, window 0x1a00001,

root 0xea, subw 0x0, time 1741349, (921,533), root:(925,581), state 0x10, keycode 37 (keysym 0xffe3, Control_L), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False

KeyPress event, serial 33, synthetic NO, window 0x1a00001,

root 0xea, subw 0x0, time 1741349, (921,533), root:(925,581), state 0x14, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES, XKeysymToKeycode returns keycode: 92 XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False

KeyRelease event, serial 33, synthetic NO, window 0x1a00001,

root 0xea, subw 0x0, time 1741436, (921,533), root:(925,581), state 0x94, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES, XKeysymToKeycode returns keycode: 92 XLookupString gives 0 bytes: XFilterEvent returns: False

Now I also have a Win7 guest VM (Win7 Enterprise 64bit SP1, patch level unknown, demo/training VM for a pre-packaged commercial application I just got yesterday; Windows currently not activated due to VM import to VirtualBox from VMWare Player setup). Interestingly, in this guest VM I do NOT have this problem. I.e. AltGR composing works in here. KEYLOOK.EXE output from this VM:

WM_KEYDOWN 17 1 29 No No Up Down

WM_KEYDOWN 18 1 56 Yes Yes Up Down

WM_SYSKEYUP 17 1 29 No Yes Down Up

WM_SYSKEYUP 17 1 29 No Yes Up Up

WM_KEYUP 18 1 56 Yes No Down Up

Hope this helps, thanks for your effort.

Regards Peter

comment:12 follow-up: ↓ 17 Changed 3 years ago by michael

Peter, thanks for the feedback. Could you also please test to see if the problem goes away when you release keyboard capturing (by pressing the "host key") on your host? And could you give the test build a try and tell me if it fixes the problem?

I would also be interested in feedback from all as to whether the test build also works as it should when the keyboard is not captured. I expect it to, but knowing is better!

comment:13 Changed 3 years ago by dannyM

Sorry Michael for not providing all the requested information...

The good news: it works again with the testcase (4.3.15) and new guest additions. Thanks!

Host: Windows 8.1 u1, German keyboard (both Dell Laptop internal and Microsoft external) Guest: Ubuntu 14, Germany keyboard layout (pc105/de/nodeadkeys)

With old 4.3.14 (and its guest additionas) host capture status had NO effect on AltGr. With new 4.3.15 is HAS effect, i.e. it works only with capture on.

comment:14 Changed 3 years ago by michael

dannyM: thank you. I will double check, as that information was slightly unexpected: does xev in the guest show no difference between capturing on and off on the host (as shown by the icon in the bottom status bar) with the old build and between capturing off with the new build?

Also, which key are you using as the host key?

comment:15 Changed 3 years ago by dannyM

Michael, host key is right Ctrl.

For v14, xev shows key press and release events as included above in my first comment, no difference depending on capture state.

However, for v15 the output is the same only when capture is off.

When capture is on, the events for Control_L are missing and only the ISO_Level3_Shift events are shown. Seems that this makes the difference...

For completeness, here is the output of keylook:

Message      Key  Char  Repeat  Scan  Ext  Prev  Tran
WM_KEYDOWN   17              1    29   No    Up  Down
WM_KEYDOWN   18              1    56  Yes    Up  Down
WM_SYSKEYUP  17              1    29   No  Down    Up
WM_KEYUP     18              1    56  Yes  Down    Up
Last edited 3 years ago by dannyM (previous) (diff)

comment:16 Changed 3 years ago by michael

dannyM: that is interesting. Do you have any idea why your system might be acting differently regarding keyboard events to the systems of many other people? Perhaps some additional software doing something with key presses?

comment:17 in reply to: ↑ 12 Changed 3 years ago by pschneider1968

Replying to michael:

Peter, thanks for the feedback. Could you also please test to see if the problem goes away when you release keyboard capturing (by pressing the "host key") on your host? And could you give the test build a try and tell me if it fixes the problem?

I would also be interested in feedback from all as to whether the test build also works as it should when the keyboard is not captured. I expect it to, but knowing is better!

Michael, pressing the host key (left Windows in my case) solves the problem for me. Also, the 4.3.15 test build works fine, without the need to press the host key.

For the time being, I have downgraded to 4.3.12 as I don't want to permanently use a test build that is not officially release. 4.3.12 works fine for me.

I hope a final fix for this issue will eventually be included in an upcoming 4.3.16.

Thanks Peter

comment:18 Changed 3 years ago by michael

Peter, this fix will be in any future 4.3 releases. While I am not allowed to say this officially, I don't see any advantage to using 4.3.12 over the test build, unless you know of some concrete problem. As for a final fix, the issue seems to be fixed for most people, but at least dannyM still seems to be having it with the test build.

comment:19 follow-up: ↓ 32 Changed 3 years ago by michael

Also, T800 was possibly seeing a related but slightly different problem<1>. Since they have not commented I do not know if it is fixed or not.

<1> https://www.virtualbox.org/ticket/2537#comment:26

comment:20 Changed 3 years ago by dannyM

Michael: there is only the "Microsoft Mouse Keyboard Center" software installed. Otherwise, the system should be normal (virus scan is negativ, Win 8.1 host and Ubuntu guest are quite fresh installs). Unfortunately, I don't have time right now to move the VM to another host or to install another VM. Thus and since it seems I'm the only one with this strange behaviour I suggest closing this ticket. Thanks a lot!

comment:21 Changed 3 years ago by michael

Is it possible to try disabling "Microsoft Mouse Keyboard Center" to see if that makes a difference? Of course, if you say you do not want to pursue this further we can leave it, otherwise I would still be interested to try to find out what is going wrong.

comment:22 follow-ups: ↓ 24 ↓ 36 Changed 3 years ago by michael

You could also give this build a try, which is another semi-shot-in-the-dark:

https://www.virtualbox.org/download/testcase/VirtualBox-4.3.15-95284-Win.exe

comment:23 Changed 3 years ago by KI

I'm hitting also this bug. AltGr does not work in Linux guests in Windows 8.1 using Finnish keyboard.

Issue seemingly started with this 4.2.14, don't recall seeing it with 4.2.12.

comment:24 in reply to: ↑ 22 ; follow-up: ↓ 26 Changed 3 years ago by chw

Replying to michael:

You could also give this build a try, which is another semi-shot-in-the-dark:

https://www.virtualbox.org/download/testcase/VirtualBox-4.3.15-95284-Win.exe

For me that build fixed the issue.

comment:25 Changed 3 years ago by dannyM

Michael, behaviour does not change build 95284 (i.e. AltGr-Q -> @ works only when capture on). After this, I uninstalled the Microsoft Mouse and Keyboard Center - no change in behaviour.

Instead, when I first tried the new build and ran xev VirtualBox crashed with "The Instruction at 0xb5d40961 referenced memory at 0x03e4f085. The memory could not be read" This did not happen in further tests...

comment:26 in reply to: ↑ 24 Changed 3 years ago by saamorim

Replying to chw:

Replying to michael:

You could also give this build a try, which is another semi-shot-in-the-dark:

https://www.virtualbox.org/download/testcase/VirtualBox-4.3.15-95284-Win.exe

For me that build fixed the issue.

Confirm bug correction with the version. I only had this problem on 4.3.14, didn't detect this problem on previous versions. (Windows Host with Lubuntu Guest)

comment:27 Changed 3 years ago by BennyA

Hello, I am new to this site, but would like to contribute a little. I am danish and just installed Virtualbox-4.3.14 on my Win 7 Enterprise x64 with SP1. Guest is Linux Mint 17 Xfce.

I have been reading this page and wondered about the host key and what should happen. I could not get the AltGr characters in any way, and this is of course a major problem since we scandinavians need AltGr for all those pipe and braces and brackets and so on.

I have found that a Windows setting does make the problem worse. It is Control Panel > Mouse > Pointer Options > Show location of pointer when I press the CTRL key.

I had this Windows setting active and then I could not get AltGr characters in any way. When I turn it off I can reproduce the behaviour, so I can not enter AltGr charcters when mouse integration is on (green arrow on mouse icon) and keypress goes to guest OS (green down arrow on key icon). When i press RIGHT CTRL once and keep focus in VM then I get black arrow on key icon and can enter AltGr characters.

With this knowlegde I think I will keep the VirtualBox 4.3.14 r95030 until an official update comes along.

I hope this has helped someonw.

Best regards BennyA

comment:28 Changed 3 years ago by KI

Tried both builds: (Windows 8.1 host, OpenSuse guest, Finnish keyboard, Asus laptop)

VirtualBox-4.3.15-95141-Win.exe

  • didn't work at all; starting virtual machines just failed

VirtualBox-4.3.15-95284-Win.exe

  • with this built my loved AltGr worked to get pipe. Lovely!

comment:29 Changed 3 years ago by macamacho

I have the same issue here. LatinAmerica Keyboard. AltGr it's needed to get "@" "¬" and many other characters. Only 4.3.14 version it's affected by this issue.

Last edited 3 years ago by macamacho (previous) (diff)

comment:30 follow-up: ↓ 31 Changed 3 years ago by macamacho

Only for information:

Host: Windows 7 Professional x64 Guest: Oracle Linux 6.5 x32

Trying 4.3.15 version.....

comment:31 in reply to: ↑ 30 Changed 3 years ago by macamacho

Hi.

I've tried "VirtualBox-4.3.15-95284-Win.exe" and the AltGr key it's working again.

So, it's confirmed that the AltGr issue is a bug for 4.3.14.

Thanks!

Mike

Replying to macamacho:

Only for information:

Host: Windows 7 Professional x64 Guest: Oracle Linux 6.5 x32

Trying 4.3.15 version.....

comment:32 in reply to: ↑ 19 Changed 3 years ago by T800

Replying to michael:

Also, T800 was possibly seeing a related but slightly different problem<1>. Since they have not commented I do not know if it is fixed or not.

<1> https://www.virtualbox.org/ticket/2537#comment:26


Dear Michael,

Sorry for the somewhat late reply and thank you for your efforts, because the test build seemingly fixed this issue, in my case too.

Kind regards, T800

comment:33 Changed 3 years ago by jablo

I have this problem on a Windows 8.1 (HP Zbook 15, Windows 8 install and upgrade to 8.1). The only application this box runs is Checkpoint VPN and Virtualbox (don't ask) Guest O/S is Ubuntu 14.04. Danish keyboard. The AltGr key behaves very strange

  • sometimes is works, AltGr+2 gives me an at sign @
  • xev shows that AltGr send ISO_LEVEL3_Shift

However, if I use Chrome web browser (maybe some other programs too), and then type AltGr+2, then Chrome believes I types Alt-2 and switches tab. When this happens, xev tells me that AltGr sends Control_L and ISO_Level3_Shift simultaneously.

Playing around with the keyboard programs and settings in Ubuntu then sometimes reset the keyboard, and AltGr starts working again. Up until I try and type @ in Chrome....

I just installed "VirtualBox-4.3.15-95141-Win.exe" from the link above, and can confirm that it seems to correct this issue. I'll be using this version from now on, and will report here if I find problems.

Thanks for that fix, it has saved my (working-)day

Last edited 3 years ago by jablo (previous) (diff)

comment:34 Changed 3 years ago by michael

dannyM: I wonder whether you have any other applications installed which might intercept keystrokes in any unusual ways?

comment:35 Changed 3 years ago by Azollyx -- Clivia bleu

Hi,

I'm here to post you a feedback: I had the same issue; [Alt Gr] not working in the virtual machine only (so, no pipes, no at signs...).

That build fixed the issue:

https://www.virtualbox.org/download/testcase/VirtualBox-4.3.15-95141-Win.exe

(it's the lone I tested).

Thanks! Rémy.

  • Host: Windows 8.1 / i7-4700HQ / SteelSeries Keyboard (French layout);
  • Guest: lasted Arch Linux.

comment:36 in reply to: ↑ 22 Changed 3 years ago by forestie

Replying to michael:

You could also give this build a try, which is another semi-shot-in-the-dark:

https://www.virtualbox.org/download/testcase/VirtualBox-4.3.15-95284-Win.exe

I can confirm I had the exact same issues as original reporter (and many others). Symptoms were AltGr key not working at all, key presses generating 2 events, one being ISO level 3 and the other being left Ctrl.

Setup is:

-Host: Windows 7 Professional 64 bits, KVM switch Avocent DVI ("Scroll lock" key to switch monitors so unlikely to interfere). Swiss-French Logitech Media Desktop K200 USB keyboard.

-Guest: Mageia 4.1 64bits (Linux). Desktop environment is XFCE.

I hadn't used VirtualBox for a while (latest use was probably on a 4.1.x or 4.2.x version), had never had problems with AltGr key or similar that I can remember of. Since I've started using VirtualBox again I upgraded my setup to 4.3.14.

I initially installed the guest in VMWare Workstation 8.x originally, but due to issues with VMWare SW support on Mageia, installed Mageia distributed VirtualBox guest additions for VB 4.3.10 while on VMWare, then shutdown in VMWare, reused the VMDK in a newly created VirtualBox 4.3.14 VM and issue was present with AltGR. Then, uninstalled Mageia-shipped VBox additions and installed the 4.3.14 ones from the VBox additions ISO, Alt GR issue still there. Tried all sort of combinations of capturing-decapturing keyboard, changing layouts in guest etc, no solution.

Installing the above build 95284 of pre-4.3.15 VBox solved the issue instantly for me.

comment:37 Changed 3 years ago by jože

I also had the problems as reported by the others in version 4.3.14: AltGr key not working at all, key presses generating 2 events, one being ISO level 3 and the other being left Ctrl.

I'm running windows 7 64 bit host with ubuntu 12 as guest. The problems occur in version 4.3.14 when the host uses a keyboard layout (for virtualbox process) that uses altgr key (e.g. Slovenian - Slovenia or German - Germany). The problem don't occur when the host uses keyboard layout (for virtual box process) that doesn't assign any special processing to right-alt key (e.g. English - United States).

Yet another workaround when the altgr doesn't work, e.g. to get altgr-q combination: press and release either ctrl key after the altgr has been pressed.

The build VirtualBox-4.3.15-95284-Win.exe solved problems also for me.

Last edited 3 years ago by jože (previous) (diff)

comment:38 Changed 3 years ago by Soukyuu

https://www.virtualbox.org/download/testcase/VirtualBox-4.3.15-95284-Win.exe fixes the issue, but sometimes pressing altgr now crashes the VM for me. Last time it happened I pressed altgr+'.', but also altgr+'+' ('~' on German keyboard). I don't have the exact error message, but will write it down when it happens again.

comment:39 Changed 3 years ago by hamelg2

I just upgraded to 4.3.14 and encounter this bug :(

the link is dead : https://www.virtualbox.org/download/testcase/VirtualBox-4.3.15-95284-Win.exe

Please, could you provide a fix, or may I downgrade to 4.3.13 ?

Edit : downgrading to 4.3.12 is another workaround  http://download.virtualbox.org/virtualbox/4.3.12/VirtualBox-4.3.12-93733-Win.exe

Last edited 3 years ago by hamelg2 (previous) (diff)

comment:40 Changed 3 years ago by jedie

https://www.virtualbox.org/download/testcase/VirtualBox-4.3.15-95713-Win.exe fixed it for me. I must not update the guest additions.

This test release is linked here:  https://forums.virtualbox.org/viewtopic.php?f=6&t=62615

comment:41 Changed 3 years ago by michael

Soukyuu: could you also try to get a crash dump?

https://www.virtualbox.org/wiki/Core_dump

comment:42 Changed 3 years ago by vladdu

When can we expect an official 4.3.16? The links to test builds are no longer available and the brackets and pipes still need to be typed! :-)

Last edited 3 years ago by vladdu (previous) (diff)

comment:43 Changed 3 years ago by michael

Can't give you any dates I'm afraid, but in the mean-time:

https://www.virtualbox.org/download/testcase/VBoxGuestAdditions_4.3.15-95679.iso

comment:44 Changed 3 years ago by mikeshow

Hi, I had the very same problem since I installed 4.3.14, installing VirtualBox 4.3.15 and VBoxGuestAdditions 4.3.15 from links above solved the problem for me. Thanks.

comment:45 Changed 3 years ago by frank

  • Status changed from new to closed
  • Resolution set to fixed

Fix is part of VBox 4.3.16.

comment:46 Changed 3 years ago by hamelg2

Hello,

I have just upgraded to 4.3.16 : virtualbox, guest additions and extension pack. Unfortunately, I still encounter this bug, I get the same behaviour. My host is running windows7 and my guest archlinux. I have downgraded to 4.3.12 :(

comment:47 Changed 3 years ago by michael

hamelg2: if you would like to try to solve this, could you please attach the output of "xev" in the guest when you press AltGr? By the way, what host and guest layout are you using? Are you using keyboard capturing? Are you using any tools on the host that might be monitoring the keyboard?

comment:48 Changed 3 years ago by hamelg2

thank you michael.

Here is the xev output.

KeyPress event, serial 34, synthetic NO, window 0x3400001,

root 0x173, subw 0x0, time 60057, (-181,75), root:(413,364), state 0x10, keycode 37 (keysym 0xffe3, Control_L), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False

KeyPress event, serial 34, synthetic NO, window 0x3400001,

root 0x173, subw 0x0, time 60057, (-181,75), root:(413,364), state 0x14, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES, XKeysymToKeycode returns keycode: 92 XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False

KeyRelease event, serial 37, synthetic NO, window 0x3400001,

root 0x173, subw 0x0, time 60246, (-181,75), root:(413,364), state 0x94, keycode 37 (keysym 0xffe3, Control_L), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False

KeyRelease event, serial 37, synthetic NO, window 0x3400001,

root 0x173, subw 0x0, time 60247, (-181,75), root:(413,364), state 0x90, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES, XKeysymToKeycode returns keycode: 92 XLookupString gives 0 bytes: XFilterEvent returns: False

I am using a French keyboard layout on host and guest. I am not using keyboard capturing and had no tools monitoring the keyboard.

Reverting to 4.3.12 fixes the issue.

Edit: I found out a strange behaviour. To fix temporary the key Alt-Gr, I must press Alt-Gr, then press and release Ctrl Right key. It works until I leave and enter again in virtualbox windows.

Last edited 3 years ago by hamelg2 (previous) (diff)

comment:49 Changed 3 years ago by michael

Please give this build a try. I hope it should solve this issue for the remaining people who still experience it.

https://www.virtualbox.org/download/testcase/VirtualBox-4.3.17-96232-Win.exe

It should be as stable as a release build, so if it works for you you can continue using it. I would be very happy if other people gave it a try too, since there is a good chance that the code will end up in a release soon, so better to know beforehand if there are any problems!

comment:50 Changed 3 years ago by hamelg2

Thank you so much for your awesome support ! Here, the build 4.3.17-96232 has definitively fixed the issue :)

comment:51 Changed 3 years ago by hamelg2

Hello Michael,

I have just upgraded to 4.3.18 and this issue is back again :( Thanks for your help

comment:52 Changed 3 years ago by Oskar

Had the problem in earlier version, upgraded to 4.3.18 r96516 and the problem is still there. Please reopen this bug and solve it because it is very hard to be efficient without pipe in Linux. Running Virtual box on Windows 7 with Linux Mint as guest.

comment:53 Changed 3 years ago by hamelg2

Why the fix in 4.3.17 is not present in 4.3.18 ? I have no choice to downgrade to 4.3.17.

comment:54 Changed 3 years ago by hamelg2

  • Status changed from closed to reopened
  • Resolution fixed deleted

comment:55 Changed 3 years ago by michael

Could anyone still experiencing AltGr issues on a Windows host try this build?

https://www.virtualbox.org/download/testcase/VirtualBox-4.3.19-96800-Win.exe

It would also be great if people who previously had issues which were fixed in the meantime could try it too, to make sure it does not break anything again.

comment:56 Changed 3 years ago by hamelg2

Here, the build 4.3.19-96800 has fixed again the issue. by hoping that this fix will be ported in 4.3.20. Thank you

comment:57 Changed 3 years ago by michael

I certainly plan to back-port it. Once again, please can people for whom this currently works test as well, to be sure that nothing is broken?

comment:58 Changed 3 years ago by mhanor

With the test build, using Debian and Windows as guests, the Scroll Lock LED indicator doesn't turn on or off, to reflect the key state, if I press Scroll Lock inside the guest. The same indicator doesn't reflect the guest key state after pressing it in the host, then returning to the guest (Linux, console mode).

Having enabled Toggle Keys (accessibility feature) in Windows 8.1, after pressing Caps Lock to enable it , the guest OS emits a "key disabled" sound every time. Then, after enabling it, if I press a character key, it emits the correct "key enabled" sound. With NumLock, it consistently emits the wrong sound on enabling/disabling the key, and a proper "key enabled" sound after pressing a character key.

The Caps Lock LED indicator doesn't reflect the key state in the guest, after pressing the Caps Lock in the host, then returning to the guest (Linux console mode only, not under the X server). Right after booting the guest (Linux), if I switch right away to the text mode console, without pressing CapsLock, returning to the host, pressing the CapsLock in the host to enable it, returning again to the console of the guest, pressing a letter key prints a capital letter, but the next ones are lower case.
Linux=Debian 7 x86, Lubuntu live 14.04.1 x86.

I don't know if all of the above issues are regressions. Host OS Win8.1 x64

Last edited 3 years ago by mhanor (previous) (diff)

comment:59 Changed 3 years ago by michael

Just to be sure that it is my change, could you check that you see that issue with my test build and not with the current one on the test builds page<1>? Thanks!

<1> https://www.virtualbox.org/wiki/Testbuilds

comment:60 Changed 3 years ago by mhanor

I can reproduce the above issues with 4.3.19-96825 and 4.3.18-96516. Maybe I should open a new bug.

comment:61 Changed 3 years ago by michael

Sounds like a good idea. Thanks for testing.

comment:62 Changed 3 years ago by michael

  • Summary changed from Keyboard mapping missing Alt-Gr to Keyboard mapping missing Alt-Gr -> fixed in 4.3.x and later releases after 18 Nov 2014

As of now, test builds<1> should contain this fix. Once again, any testing before the next release is very welcome to help ensure that we don't have new people affected after the release.

<1> https://www.virtualbox.org/wiki/Testbuilds

comment:63 Changed 3 years ago by frank

  • Status changed from reopened to closed
  • Resolution set to fixed

Fixed in VBox 4.3.20. I hope we can finally close this ticket.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use