x11-drivers/xf86-input-evdev-1.2.0 keyboard problem

[mschmarck]

Hi!

I've got the same problems that Genetic has reported; ie. when I press <Cursor Up>, a screenshot in Gnome is taken. Ie. it seems as if the system thinks, that <Print Screen> key has been pressed. But unlike Genetic, I do not want to go the route of unmerging evdev and sticking with kbd.

In my xorg.conf, I've got:

[fredor]

Try using <Option "Name" " ? "> instead of <Option "Device" "/dev/input/event3">
"Name" can be obtained from 'cat /proc/bus/input/devices'

[mschmarck]

Hello!

I tried to use "Name", but this didn't work for me When I used Name instead of Device for mouse, the pointer would not work.

[fredor]

I have a Logitech MX1000 mouse and I have had no trouble with this. The Name in my case is 'Logitech USB reciever' probably because it is a wireless version.
I have the same program versions as you and have had no problems with the mouse except when I tried xorg-server -hal. Then it didn't work at all.

My problems have been with the keyboard. I have tried with the 'fdi' files and this worked to some extent but I still needed the xorg.conf components.
I have modified the file /usr/share/hal/fdi/policy/10osvendor/10-keymap.fdi changing "us" to "gb". This may be overwritten with "hal" updates so it may be better to copy it to /etc/hal/policy/fdi/

I see you have another mouse component - Does this not work also?
_________________
Gentoo /amd64/2007.0
AMD Athlon64 X2 4200+
ASUS M2N32-SLI Deluxe

[ajc158]

The solution to the keyboard issue is as follows:

The problem is the window manager / desktop environment overriding evdev to pc105, this causes up to be assigned to print screen. Simply disable the printscreen functionality of the window manager (gconf-editor -> apps -> metacity -> something...) for gnome using metacity, in my case ccsm for compiz-fusion. Remove the command issued when printscreen is hit and you will get your cursor back (but no printscreen function).

This is only a workaround, but the issue is known about, and at least KDE that I have read of has fixed it for the next version.

Alex

[mschmarck]

[fredor]

Have you tried the external keyboard this is the same as mine:-

Name="AT Translated Set 2 keyboard"

Go to /usr/share/hal/fdi/policy/10osvendor/10-keymap.fdi
and change "<merge key="input.xkb.layout" type="string">us</merge>"
to "<merge key="input.xkb.layout" type="string">ch</merge>"
with a text editor. In my case it is line 19.

If this works you can copy the file to "/etc/hal/fdi/policy/" or it may be changed with updated versions of hal.
_________________
Gentoo /amd64/2007.0
AMD Athlon64 X2 4200+
ASUS M2N32-SLI Deluxe

[bos_mindwarp]

[Turrican]

Well, my problem was, that the "up" key made a screenshot in KDE.
After I edited the hal config (/etc/hal/fdi/policy/x11-input.fdi) the problem was still there.

For me the solution was to switch to "evdev-managed keyboard" in the KDE control center.
_________________
Windows hates me!

[wizard69]

masking the following packages also helped me

[keenblade]

[slim.one]

[pezed]

i downgraded to hal 0.5.9.1-r3 and it fixed all of my problems. (especially had problems with keyboard under vmware)

I'm still using evdev 1.2. hal 0.5.10 is the problem, not evdev!!

[DesertF0x]

Found something which really helped me:

[Xake]

First some info fo the ones not grasping this:
In xorg-server-1.4 there is hotplug possibilities.
To utilize them you need hal-0.5.10 and evdev-1.2.
It works like this:
X starts and asks HAL for input devices.
HAL tells X what inputdevices it knows of and how they should be configured (what driver to use, what layout to use).
X uses this information, starts the driver and configure it according to how HAL tells it to

What this means for the user:
If you have all the required components and right verions then your devices are hotplugged and the configuration for them resides with HAL (Input sections in xorg.conf is in this case depricated).
If any dependency is not met Xorg uses the old way of managing your devices (input sections in your xorg.conf is used).

So:
No special version of these packages are broken or "are the problem" in any way. If you experience problems this is most likely becouse you have not (re)configured things like you should.

If you do not intend to use hotplugging and do not use evdev, then 'emerge -C xf86-input-evdev' (and remove 'evdev' from your INPUT_DEVICES="" in make.conf).
If you do use evdev but still want to use the configurations from xorg.conf, then do as DesertFox told you and add

[Luda]

Okay, so we don't need the device-sections in our xorg.confs anymore, but how do we tell hal whch keymap to use?

I can tell KDE that I've got a keyboard with de-layout, shure, but what about, for example, KDM?

Maybe something is wrong with my setup:

[Xake]

my /etc/hal/fdi/policy/10-keymap.fdi

[Luda]

Oh, well..

first of all: I mixed up the directories.
second: I had a look at 10-keyboard-policy.fdi and wondered where I could change the layout, because there is no file called 10-keymap.fdi on my system.

I will have a second look at this issue this evening, thanks for now

[mathfeel]

My keyboard and mouse are working except that I don't have the CONTROL key...I am not sure if it is related to the fact that some other devices are also recognized as keyboard:

[superbrain666]

I fixed the issue with adding the correct HAL informations.
And telling KDE to use this evdev-mapped-keyboard.

BUT: My VM in VMWARE is still broken. This means my windows has problems with the cursor keys.
Very ugly because i use windows only for playing games... so games without cursors are not possible

I think it has something to do with VMWAREs build-in GTK interface or with the GTK on my Gentoo, which is not ready for evdev.
Is it possible I tell VMWARE to use the correct keymap? Maybe in a config?

I've tried to clean out my .gnomeXX and .gconf folders with no change.

[mhgentoo]

i did what renrutal decided.
this works fine.
like you mentioned before, hal is the problem!

thanks for this help.

[Luda]

[Xake]

[appofice]

I did have the same problem. I decide to mask the new package but now i decide to install evdev-1.2.0 and configure my xorg.conf.
My new xorg.conf for the input is like this

Section "InputDevice"

Identifier "Keyboard1"
Driver "evdev"
Option "Device" "/dev/input/by-id/usb-Microsoft_Comfort_Curve_Keyboard_2000-event-kbd"
Option "CoreKeyboard"
#Option "AutoRepeat" "500 30"
#Option "XkbRules" "xorg"
Option "XkbModel" "evdev"
#"pc105"
Option "XkbLayout" "ca"
Option "XkbVariant" "fr"
EndSection

Section "InputDevice"
Identifier "Mouse1"
Driver "evdev"
Option "CorePointer"
Option "Name" "Logitech USB-PS/2 Optical Mouse"
#Option "Protocol" "auto" # Mouse Systems (3-button protocol)
Option "Device" "/dev/input/by-id/usb-Logitech_USB-PS.2_Optical_Mouse-event-mouse"
Option "ZAxisMapping" "4 5 6 7"
Option "HWHEELRelativeAxisButtons" "7 6"

EndSection
now or for the moment my keyboard and mouse work well...

ps: i also did what Krampi say about /etc/hal/fdi/policy/x11-input.fdi

<?xml version="1.0" encoding="UTF-8"?>
<deviceinfo version="0.2">
<device>
<match key="info.capabilities" contains="input.keys">
<merge key="input.xkb.layout" type="string">ca</merge>
<merge key="input.xkb.variant" type="string">fr</merge>
</match>
</device>
</deviceinfo>

[Xake]