Sorry, note that this is the same problem that I ended up with at the end of
this bug report: https://bugs.freedesktop.org/show_bug.cgi?id=5807

Since the problem does not pertain to that bug report (which I believe can now
be closed, even though it did introduce another problem), I'm opening this bug
report.

(In reply to comment #0)
> When I use the "kbd" driver in xorg.conf for my keyboard, all of the standard
> keys work as expected, but the multimedia keys do not work (volume, etc).  When
> I change the driver to evdev, the multimedia keys work, but a LOT of my standard
> keys are mapped incorrectly.  For example, PGUP is detected as '/', PGDN is
> detected as a right-click (context menu key), none of the arrow keys work as
> expected, home/end are wrong.  The right control key appears to be detected as
> PGDN.  It's very hard to work with.
> 
> This is using xf86-input-evdev-1.1.2-r1 in gentoo's portage, but the problem has
> existed since 1.0.0.5.  Here are the relevant entries from xorg.conf:
> 

> Section "InputDevice"
>     Identifier	"Keyboard1"
>     Driver	"evdev"
>     Option	"Device"	"/dev/input/event0"
>     Option "AutoRepeat" "500 30"
>     Option "XkbRules"	"xorg"
>     Option "XkbModel"	"evdev"
>     Option "XkbLayout"	"us"
> EndSection

This is not quite right, the Device option is no longer around and you need to
specify some other way to indicate the device, see the manpage.
> 
> Section "InputDevice"
>     Identifier	"Mouse1"
>     Option "Protocol" "auto"
>     Driver	"evdev"
>     Option "Device"      "/dev/input/event1"
>     Option "SendCoreEvents"
>     Option "Resolution" "800"
>     Option "ZAxisMapping" "4 5 6 7"
> EndSection

Same here, and almost none of the options work with evdev, see the manpage for
the right way to specify the mapping.

> (**) Option "XkbRules" "xorg"
> (**) Option "XkbModel" "evdev"
> (**) Option "XkbLayout" "us"

> (II) XINPUT: Adding extended input device "Keyboard1-usb-0000:00:1f.2-2/input0"
> (type: KEYBOARD)
> (II) XINPUT: Adding extended input device "Mouse1-usb-0000:00:1f.2-2/input1"
> (type: KEYBOARD)

The mouse shouldn't be matching the keyboard device, but it is.

>     xkb_keycodes             { include "xfree86+aliases(qwerty)" };

And that's really wrong.
>     xkb_types                { include "complete" };
>     xkb_compatibility        { include "complete" };
>     xkb_symbols              { include "pc/pc(pc105)+pc/us" };
>     xkb_geometry             { include "pc(pc104)" };
> (II) Mouse1-usb-0000:00:1f.2-2/input1: Init
>     xkb_keycodes             { include "xfree86+aliases(qwerty)" };

So is this.

And that's your problem.

Please update to the most recent xkeyboard-config package and fix the
specification stuff, and let me know if that fixes things.

> This is not quite right, the Device option is no longer around and you need to
> specify some other way to indicate the device, see the manpage.

From "man evdev", I see:
       Section "InputDevice"
         Identifier "devname"
         Driver "evdev"
         Option "Device"   "devpath"
         ...
       EndSection
and:
       Option "Device" "string"
              Specifies the device  note  through  which  the  device  can  be
              accessed.     This    will    generally    be    of   the   form
              "/dev/input/eventX", where X is some integer.  The mapping  from
              device node to hardware is system-dependent.
              Please note that use of this option is discouraged.
So, I'm sorry if my man pages may be out of date, but I would assume that
installing the latest package would update any relevant man pages as well (as
virtually all other packages do).  It does say that use of the option is
"discouraged", but that does not by any means indicate that it is "not around"
anymore...  As you can see, Xorg does in fact understand what devices I'm
refering to, so I really don't think the Device line has any effect on the key
mapping problem.  But because it appears to be on the path to deprecation, I
will use the Phys option instead.

> Same here, and almost none of the options work with evdev, see the manpage for
> the right way to specify the mapping.

Thanks, I see the new/correct options for axis mapping in the man page.  I will
fix those as well, although if ZAxisMapping is not recognized, then that means
the current behavior is automatically detected, and it's working great, so I'll
just remove the option until I need to tweak it further.

> The mouse shouldn't be matching the keyboard device, but it is.

Indeed - that was a strange behavior I noticed from the previous bug that I
submitted.  It seems that my mouse is being detected as both a keyboard and a
mouse, as apparently a few of the buttons on the mouse are sent as keyboard
events (I actually have not seen any keyboard events sent by it, although there
is a button on the mouse that matches the glyph on one of the keys on the
keyboard, so perhaps that's the button that is sent as a keyboard event).  Below
is my /proc/bus/input/devices.  You can see that the mouse is detected as both a
keyboard and a mouse.  Why Xorg detects it as ONLY a keyboard, I don't know, but
as I mentioned before, the mouse is actually the part of it that works
perfectly, so again I don't think that has any effect on the problem I'm
experiencing.

I: Bus=0003 Vendor=046d Product=c512 Version=3007
N: Name="Logitech USB Receiver"
P: Phys=usb-0000:00:1f.2-2/input0
S: Sysfs=/class/input/input0
H: Handlers=kbd event0
B: EV=120003
B: KEY=10000 7 ff800000 7ff febeffdf ffefffff ffffffff fffffffe
B: LED=1f

I: Bus=0003 Vendor=046d Product=c512 Version=3007
N: Name="Logitech USB Receiver"
P: Phys=usb-0000:00:1f.2-2/input1
S: Sysfs=/class/input/input1
H: Handlers=kbd mouse0 event1   <---
B: EV=7
B: KEY=7fffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff 0
0 1878 d800d100 1e0000 0 0 0
B: REL=143

Note that input1 is mapped to handlers "kbd" *and* "mouse0".

> >     xkb_keycodes             { include "xfree86+aliases(qwerty)" };
> And that's really wrong.

Okay, but that's not something I specified in the config -- that is coming from
the log file.  So, if it's wrong, how can I fix it?

> Please update to the most recent xkeyboard-config package and fix the
> specification stuff, and let me know if that fixes things.

I'll update xkeyboard-config, and make the changes to the Device sections I
mentioned above, and post back with the results.  Right now, I'm using the "kbd"
driver for the keyboard, and evdev for the mouse, so it seems to be working
pretty well right now with the exception of some of the multimedia keys on the
keyboard not working.  However, all of the standard keys are working properly
with "kbd", so I can live without the multimedia keys until we can get this
behavior figured out.

Thanks for the info - I'll post back after those changes.

Zephaniah:

I updated xkeyboard-config to version 0.8 in portage (uninstalled 'xkbdata',
which blocks xkeyboard-config).  I also removed unnecessary options from the
device sections and replace the Device options with their Phys equivalences.

Everything appears to be the same still.

xorg.conf:
-----
Section "InputDevice"
    Identifier	"Keyboard1"
    Driver	"evdev"
    Option	"Phys" "usb-0000:00:1f.2-2/input0"
    Option "XkbRules"	"xorg"
    Option "XkbModel"	"evdev"
    Option "XkbLayout"	"us"
EndSection

Section "InputDevice"
    Identifier	"Mouse1"
    Option "Protocol" "auto"
    Driver	"evdev"
    Option "Phys" "usb-0000:00:1f.2-2/input1"
    Option "SendCoreEvents"
EndSection


Xorg.0.log:
-----
(II) evdev brain: Rescanning devices (1).
(**) Option "SendCoreEvents"
(**) Mouse1-usb-0000:00:1f.2-2/input1: always reports core events
(**) Option "CorePointer"
(**) Mouse1-usb-0000:00:1f.2-2/input1: Core Pointer
(II) Mouse1-usb-0000:00:1f.2-2/input1: Found 4 relative axes.
(II) Mouse1-usb-0000:00:1f.2-2/input1: Configuring as pointer.
(**) Mouse1-usb-0000:00:1f.2-2/input1: HWHEELRelativeAxisButtons: 6 7.
(**) Mouse1-usb-0000:00:1f.2-2/input1: WHEELRelativeAxisButtons: 4 5.
(II) Mouse1-usb-0000:00:1f.2-2/input1: Found 95 mouse buttons
(II) Mouse1-usb-0000:00:1f.2-2/input1: Configured 99 mouse buttons
(II) evdev brain: Rescanning devices (2).
(**) Option "CoreKeyboard"
(**) Keyboard1-usb-0000:00:1f.2-2/input0: Core Keyboard
(**) Option "XkbRules" "xorg"
(**) Option "XkbModel" "evdev"
(**) Option "XkbLayout" "us"
(II) XINPUT: Adding extended input device "Keyboard1-usb-0000:00:1f.2-2/input0"
(type: KEYBOARD)
(II) XINPUT: Adding extended input device "Mouse1-usb-0000:00:1f.2-2/input1"
(type: KEYBOARD)
(II) XINPUT: Adding extended input device "evdev brain" (type: evdev brain)
(II) XINPUT: Adding extended input device "NVIDIA Event Handler" (type: Other)
(**) Mouse1-usb-0000:00:1f.2-2/input1: 4 valuators.
(**) evdev_btn.c (81): Registering 99 buttons.
    xkb_keycodes             { include "evdev+aliases(qwerty)" };
    xkb_types                { include "complete" };
    xkb_compatibility        { include "complete" };
    xkb_symbols              { include "pc(pc105)+us" };
    xkb_geometry             { include "pc(pc104)" };
(II) Mouse1-usb-0000:00:1f.2-2/input1: Init
    xkb_keycodes             { include "evdev+aliases(qwerty)" };
    xkb_types                { include "complete" };
    xkb_compatibility        { include "complete" };
    xkb_symbols              { include "pc(pc105)+us" };
    xkb_geometry             { include "pc(pc104)" };
(II) Keyboard1-usb-0000:00:1f.2-2/input0: Init
(II) evdev brain: Rescanning devices (3).
(II) Mouse1-usb-0000:00:1f.2-2/input1: On
(II) Keyboard1-usb-0000:00:1f.2-2/input0: On
-----

The mouse is still working great, and the WHEEL and HWHEEL axies are detected
automatically, so I've removed the ZAxisMapping option.  The keyboard is still
showing the same behavior as before.  The log entries that you indicated to be
my problem are still there, but of course I know of no way to change what the
driver is seemingly doing automatically.  If there is a configuration option to
change that behavior, then I would appreciate a point in the right direction to
fix it.  If it's a driver issue, well, that's what I'm posting to find out :) 
Thanks

Sorry for waiting so long to get back to you.

Could you please attach the complete xorg.conf, the complete Xorg.0.log, output
of 'setxkbmap -v 10 -print', and output of 'setxkbmap -print | xkbcomp -a -xkb - -'.

Each one as an attachment to the bug would be best.

Hopefully something in there will give me a hint as to what's going wrong with
this for you.

Zephaniah E. Hull.

Section "InputDevice"
    Identifier     "Keyboard0"
#   Driver         "kbd"
    Driver         "evdev"
#   Option         "Phys dev" "usb-0000:00:10.3-2/input0"
    Option         "CoreKeyboard"
#   Option         "Protocol" "evdev"
    Option         "Device" "/dev/input/event0"
    Option         "XkbRules" "xorg"
#   Option         "XkbModel" "evdev"
#   Option         "XkbModel" "logiultrax"
#   Option         "XkbModel" "logiitc"
    Option         "XkbModel" "pc105"
    Option         "XkbLayout" "it"
    Option         "CustomKeycodes" "on"
EndSection



(In reply to comment #5)
> Sorry for waiting so long to get back to you.
> 
> Could you please attach the complete xorg.conf, the complete Xorg.0.log, output
> of 'setxkbmap -v 10 -print', and output of 'setxkbmap -print | xkbcomp -a -xkb
- -'.
> 
> Each one as an attachment to the bug would be best.
> 
> Hopefully something in there will give me a hint as to what's going wrong with
> this for you.
> 
> Zephaniah E. Hull.

(Ignore the previous comment, please)

I have the same problem here (logitech UltraX Media Desktop Kit).

This is the output of setxkbmap -v 10 -print:

Setting verbose level to 10
locale is C
Couldn't interpret _XKB_RULES_NAMES property
Use defaults: rules - 'xorg' model - 'pc101' layout - 'us'
Applied rules from xorg:
model:      pc101
layout:     us
Trying to build keymap using the following components:
keycodes:   xfree86+aliases(qwerty)
types:      complete
compat:     complete
symbols:    pc/pc(pc101)+pc/us
geometry:   pc(pc101)
xkb_keymap {
        xkb_keycodes  { include "xfree86+aliases(qwerty)"       };
        xkb_types     { include "complete"      };
        xkb_compat    { include "complete"      };
        xkb_symbols   { include "pc/pc(pc101)+pc/us"    };
        xkb_geometry  { include "pc(pc101)"     };
};


My keyboard configuration:

Section "InputDevice"
    Identifier     "Keyboard0"
#   Driver         "kbd"
    Driver         "evdev"
#   Option         "Phys dev" "usb-0000:00:10.3-2/input0"
    Option         "CoreKeyboard"
#   Option         "Protocol" "evdev"
    Option         "Device" "/dev/input/event0"
    Option         "XkbRules" "xorg"
#   Option         "XkbModel" "evdev"
#   Option         "XkbModel" "logiultrax"
#   Option         "XkbModel" "logiitc"
    Option         "XkbModel" "pc105"
    Option         "XkbLayout" "it"
    Option         "CustomKeycodes" "on"
EndSection

Thanks

luigi



(In reply to comment #5)
> Sorry for waiting so long to get back to you.
> 
> Could you please attach the complete xorg.conf, the complete Xorg.0.log, output
> of 'setxkbmap -v 10 -print', and output of 'setxkbmap -print | xkbcomp -a -xkb
- -'.
> 
> Each one as an attachment to the bug would be best.
> 
> Hopefully something in there will give me a hint as to what's going wrong with
> this for you.
> 
> Zephaniah E. Hull.

(In reply to comment #5)
> Sorry for waiting so long to get back to you.
> 
> Could you please attach the complete xorg.conf, the complete Xorg.0.log, output
> of 'setxkbmap -v 10 -print', and output of 'setxkbmap -print | xkbcomp -a -xkb
- -'.
> 
> Each one as an attachment to the bug would be best.
> 
> Hopefully something in there will give me a hint as to what's going wrong with
> this for you.
> 
> Zephaniah E. Hull.

(In reply to comment #7)
> (Ignore the previous comment, please)
> 
> I have the same problem here (logitech UltraX Media Desktop Kit).

Actually, you don't...

> keycodes:   xfree86+aliases(qwerty)

Upgrade your xkeyboard-config.

Let me know if that doesn't fix it.

I have upgraded xkeyboard-config without success.


I also upgraded to Xorg-7.1.

bye.

luigi


(In reply to comment #8)
> (In reply to comment #7)
> > (Ignore the previous comment, please)
> > 
> > I have the same problem here (logitech UltraX Media Desktop Kit).
> 
> Actually, you don't...
> 
> > keycodes:   xfree86+aliases(qwerty)
> 
> Upgrade your xkeyboard-config.
> 
> Let me know if that doesn't fix it.

The problem persists...

I have a keyboard with italian layaout. I report some log about the xorg and
setxkmap executions.

merci

luigi


My configuration:

--- BEGIN xorg.conf ---

Section "InputDevice"
    Identifier     "Keyboard0"
    Driver         "evdev"
    Option         "Phys" "usb-0000:00:10.3-2/input0"
    Option         "CoreKeyboard"
    Option         "Protocol" "evdev"
    Option         "XkbRules" "xorg"
    Option         "XkbModel" "evdev"
    Option         "XkbLayout" "it"
EndSection

Section "InputDevice"
    Identifier     "Mouse0"
    Driver         "evdev"
    Option         "CorePointer"
    Option         "SendCoreEvents"
    Option         "Phys" "usb-0000:00:10.3-2/input1"
    Option         "Protocol" "evdev"
EndSection

--- END xorg.conf ---

Xorg.0.log

-- BEGIN Xorg.0.log ---
(II) evdev brain: Rescanning devices (1).
(**) Option "SendCoreEvents"
(**) Mouse0-usb-0000:00:10.3-2/input1: always reports core events
(**) Option "CorePointer"
(**) Mouse0-usb-0000:00:10.3-2/input1: Core Pointer
(II) Mouse0-usb-0000:00:10.3-2/input1: Found 4 relative axes.
(II) Mouse0-usb-0000:00:10.3-2/input1: Configuring as pointer.
(**) Mouse0-usb-0000:00:10.3-2/input1: HWHEELRelativeAxisButtons: 6 7.
(**) Mouse0-usb-0000:00:10.3-2/input1: WHEELRelativeAxisButtons: 4 5.
(II) Mouse0-usb-0000:00:10.3-2/input1: Found 95 mouse buttons
(II) Mouse0-usb-0000:00:10.3-2/input1: Configured 99 mouse buttons
(II) evdev brain: Rescanning devices (2).
(**) Option "CoreKeyboard"
(**) Keyboard0-usb-0000:00:10.3-2/input0: Core Keyboard
(**) Option "XkbRules" "xorg"
(**) Option "XkbModel" "evdev"
(**) Option "XkbLayout" "it"
(II) XINPUT: Adding extended input device "Keyboard0-usb-0000:00:10.3-2/input0"
(type: KEYBOARD)
(II) XINPUT: Adding extended input device "Mouse0-usb-0000:00:10.3-2/input1"
(type: KEYBOARD)
(II) XINPUT: Adding extended input device "evdev brain" (type: evdev brain)
(**) Mouse0-usb-0000:00:10.3-2/input1: 4 valuators.
(**) evdev_btn.c (81): Registering 99 buttons.
    xkb_keycodes             { include "evdev+aliases(qwerty)" };
    xkb_types                { include "complete" };
    xkb_compatibility        { include "complete" };
    xkb_symbols              { include "pc(pc105)+us" };
    xkb_geometry             { include "pc(pc104)" };
(II) Mouse0-usb-0000:00:10.3-2/input1: Init
    xkb_keycodes             { include "evdev+aliases(qwerty)" };
    xkb_types                { include "complete" };
    xkb_compatibility        { include "complete" };
    xkb_symbols              { include "pc(pc105)+it" };
    xkb_geometry             { include "pc(pc104)" };
(II) Keyboard0-usb-0000:00:10.3-2/input0: Init
(II) evdev brain: Rescanning devices (3).
(II) Mouse0-usb-0000:00:10.3-2/input1: On
(II) Keyboard0-usb-0000:00:10.3-2/input0: On
    xkb_keycodes             { include "xfree86+aliases(qwerty)" };
    xkb_types                { include "complete" };
    xkb_compatibility        { include "complete" };
    xkb_symbols              { include "pc(pc105)+it+inet(logicdit)" };
    xkb_geometry             { include "pc(pc104)" };
(EE) Error loading keymap /usr/share/X11/xkb/compiled/server-0.xkm
--- END Xorg.0.log ---

setxkmap -v 10 -print

--- BEGIN setxkmap -v 10 -print ---
setxkbmap -v 10 -print
Setting verbose level to 10
locale is C
Applied rules from xorg:
model:      evdev
layout:     it
Trying to build keymap using the following components:
keycodes:   evdev+aliases(qwerty)
types:      complete
compat:     complete
symbols:    pc(pc105)+it
geometry:   pc(pc104)
xkb_keymap {
        xkb_keycodes  { include "evdev+aliases(qwerty)" };
        xkb_types     { include "complete"      };
        xkb_compat    { include "complete"      };
        xkb_symbols   { include "pc(pc105)+it"  };
        xkb_geometry  { include "pc(pc104)"     };
};

--- END setxkmap -v 10 -print --

--- BEGIN setxkbmap -layout it -v 10 ---
setxkbmap -layout it -v 10
Setting verbose level to 10
locale is C
Warning! Multiple definitions of keyboard layout
         Using command line, ignoring X server
Applied rules from xorg:
model:      evdev
layout:     it
Trying to build keymap using the following components:
keycodes:   evdev+aliases(qwerty)
types:      complete
compat:     complete
symbols:    pc(pc105)+it
geometry:   pc(pc104)
Error loading new keyboard description

--- END setxkbmap -layout it -v 10 ---

Created attachment 5814 [details]
xorg.conf with evdev enabled

Created attachment 5815 [details]
Xorg log file with evdev

Created attachment 5816 [details]
Output of 'setxkbmap' commands

Created attachment 5817 [details]
Resulting xkb file from 'xkbcomp' command

Comment on attachment 5817 [details]
Resulting xkb file from 'xkbcomp' command

FYI, xkbcomp did not accept the '--' argument to take STDIN as the input file. 
I had to use a temporary file.

The above 4 files contain all of the information you requested.  Let me know if
you find something incorrect.  Thanks!

*** Bug 5559 has been marked as a duplicate of this bug. ***

*** Bug 5903 has been marked as a duplicate of this bug. ***

I think this is connected to #8469.
I experience the same problems as below and using xev to look at the events I
indeed got (as in the other bug) "button" instead of "keycode" in its output.

Currently, the problem is fixed in gentoo-portage. I'm using the following versions:

xf86-input-evdev-1.1.5-r1
xorg-server-1.1.1-r1

I use Option "XkbModel" "evdev" in xorg.conf, and everything works swell.

xorg-x11-drv-evdev-1.1.2-3.fc7.x86_64
xorg-x11-server-Xorg-1.3.0.0-7.fc7.x86_64

Problem does not look like fixed, at least for fedora 7. cursors, home, scroll lock and friends are busted.

I believe the problem with this, at least for me, was the model settings, as for example, when I selected "Logitech Cordless Desktop Pro" keyboard model, the keys work properly, but selecting the standard pc104 keyboard model, the key strangeness I described crops up.  So even though most people choose model "evdev", and it is apparently the "correct" way to do it, it results in incorrect key mappings.  Try choosing your appropriate keyboard model, to see if it corrects the problem.  I don't use this keyboard any longer though, so I'm just going from memory with this.

(In reply to comment #21)
> I believe the problem with this, at least for me, was the model settings, as
> for example, when I selected "Logitech Cordless Desktop Pro" keyboard model,
> the keys work properly.

What are you using to select the keyboard model?

Just an additional note, Debian bug #442316 (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=442316) also shows this problem.

I believe the primary culprit here are the various programs used to change the xkbmap. Before switching to version 1.4.x I used kxkbmap to add the Hebrew layout, and by the way, switched the keyboard model to pc104. This caused various wrong key mappings.
Just found how to correct it, by changing the model there to evdev it's fixed.
This thing should be documented upon switching to the newer X.

mass reassignment. Zephaniah isn't the maintainer anymore.

From Comment #1:
"The right control key appears to be detected as PGDN."

Typical problem when the xkb model is set to the wrong value. This has been fixed with xkeyboard-config 1.4.