Summary: | Caps Lock and Num Lock LED no longer function with x11-base/xorg-server-1.5.3-r5 | ||
---|---|---|---|
Product: | Gentoo Infrastructure | Reporter: | junkmail |
Component: | Bugzilla | Assignee: | Gentoo X packagers <x11> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | vmware+disabled |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
URL: | http://communities.vmware.com/thread/226879 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
junkmail
2009-05-06 15:36:24 UTC
I don't see a bug here. You said yourself: When using evdev and hal I had to put the following line into /etc/vmware/config to get functioning number pad and caps lock: xkeymap.nokeycodeMap = true For a better reference: http://lists.freedesktop.org/archives/xorg/2009-May/045462.html http://lists.freedesktop.org/archives/xorg/2009-May/045476.html (In reply to comment #1) > I don't see a bug here. > You said yourself: > When using evdev and hal I had to put the following line into > /etc/vmware/config to get functioning number pad and caps lock: > > xkeymap.nokeycodeMap = true Sorry, I didn't make it clear what I meant by this. The above line in /etc/vmware/config is required to make the num lock & caps lock keys function using hal/evdev, but when this fix is applied, pressing those keys still fails to change the LED status. I have no idea what vmware does wrt X input and I don't see how I could figure it out. If your Gentoo host system works as usual when vmware is not running (ie a standard desktop session), then there's nothing for the X11 herd to fix. Thanks (In reply to comment #3) The keyboard functions perfectly in the Gentoo host, regardless of whether vmware is running or not. It's just in the clients that the problem arises, and this only started with the update of xorg-server. I can understand how it would be difficult for a Gentoo developer to sort this, but wanted to report it here first before going to vmware. I am surprised that no-one else appears to be affected by this though. As I suggested in comment #3, please file a bug in vmware's bug tracker as I have no idea what's going on. Thanks vmware bug reporting is very confusing. Anyway, I've posted a message at: http://communities.vmware.com/thread/226879 Have you been able to reproduce the bug? No, I don't use vmware. That's why I requested you open the bug, it's much faster if you do so yourself :) Thanks And closing with the proper resolution. Thanks for the feedback, we greatly appreciate it :) |