evdev keyboard problem in xorg 1.5.2 and evdev 2.0.99+

Scott Serr serrjunk at theserrs.net
Wed Dec 31 13:19:51 PST 2008


Timo Aaltonen wrote:
> On Tue, 30 Dec 2008, Scott Serr wrote:
>
>   
>> I'm using Ubuntu 8.10 / Intrepid.  I'm working on a multiseat project,
>> but this is not a multiseat issue.
>>
>> I disable HAL, to let X handle the input devices:
>>
>> Section "ServerFlags"
>>       Option "AutoAddDevices" "false"
>> EndSection
>>
>> Then specify my keyboard:
>>
>> Section "InputDevice"
>>   Identifier   "Keyboard0"
>>   Driver       "evdev"
>>   Option       "Device"      "/dev/input/event1"
>>   Option       "CoreKeyboard"
>>   Option       "XkbRules"    "xorg"
>>   Option       "XkbModel"    "evdev"
>>   Option       "XkbLayout"   "us"
>> EndSection
>>
>> This works correctly, I'm able to type with my first keyboard and the
>> second one is not listened to.  This is good.  The problem is keys are
>> mapped weird.  "up arrow" launches the ScreenShot tool in Gnome.  Gnome
>> keyboard is set to evdev managed.  It seems I can't give it any Xkb
>> options to resolve this.
>>     
>
> XkbRules needs to be evdev, not model.
>
> t
>
>   

Timo, it almost works.

I installed a fresh Ubuntu 8.10 with xkb-data package
xkb-data_1.3-2ubuntu4.4_all.deb.  All updates to date.  Indeed there is
an evdev config file in the xkb-data.

This is very weird... The only way it works is if I switch Preferences->
Appearance-> VisualEffects back and forth between None and
Normal/Extra.  It doesn't matter if it is set one way or the other...
The "up arrow" causing a "PrtScn" happens every time before this is
toggled.   And after a toggle, "up arrow" works correctly.  I also
tested on a new user, same behavior.  Need to fiddle with the
VisualEffects radio button.

The toggle of course turns on and off the "double X" graphics (compiz)
stuff that I know nothing about.  But I wonder if it initializes
something in the process giving me what I really asked for?

I start up TWM with xinit and things work.

This doesn't necessarily seem like an X problem now.  Any guidance?

Thanks,
Scott




More information about the xorg mailing list