Description of problem:
If I use an xorg.conf file that disables the evdev stuff with
Option "AutoAddDevices" "false"
then the keycodes (not merely keysyms) on my keyboard magically
change. Up arrow becomes keycode 98 (katakana) instead of 111 (Up),
right arrow turns to enter, etc. I can't even begin to imagine
how or why this happens or what component I ought to file this
bug against :-).
Version-Release number of selected component (if applicable):
Every time I boot with the xorg.conf in place.
Steps to Reproduce:
keycodes stay the same
Created attachment 361796 [details]
the xorg.conf file I try to use
Created attachment 361797 [details]
the xorg log when using xorg.conf (and getting bad keycodes)
Created attachment 361798 [details]
the xorg log when not using xorg.conf (and I get good keycodes)
Ah-HA! Apparently the "kbd" driver default layout has silently changed
(and no longer matches the man page). If I add this explicit definition
to my xorg.conf, I get my keyboard back to normal:
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
In fedora 11 with same hardware, I don't have to explicitly set pc105, in fact,
I don't have to define a keyboard input device at all.
Could the mysterious default behavior change be related to the KEYBOARD=pc
kernel boot parameter I see anaconda setup when I installed fedora 12?
I didn't get one of those in earlier fedoras (or a bunch of other funny
looking kernel parameters for language stuff either).
The foundational question which I am curious about: why do you need to set AutoAddDevices to false?
Because I have a trackball, and I can't use a trackball without being able
to define a drag lock button, and bug 524428 is preventing me from
defining a drag lock button the "right way".
Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their packages (at least F12Beta, but even better if the very latest versions).
Please, if you experience this problem on the up-to-date system, let us now in the comment for this bug, or whether the upgraded system works for you.
If you won't be able to reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
[This is a bulk message for all open Fedora Rawhide Xorg-related bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.
More information and reason for this action is here:
Could you please reply to the previous question? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
[Note please, that this is machine generated comment for large amount of bugs; due to some technical issues, it is possible we've missed some of the responses -- it is happens, please, just a make a comment about that; that we will see. Thank you]
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.
Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.
Closing as INSUFFICIENT_DATA.
Fedora Bugzappers volunteer triage team