Bug 169528

Summary: Swapping mouse buttons doesn't work with "AlwaysCore" devices
Product: Red Hat Enterprise Linux 3 Reporter: Bastien Nocera <bnocera>
Component: XFree86Assignee: X/OpenGL Maintenance List <xgl-maint>
Status: CLOSED WONTFIX QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.0CC: benl, tao
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-05-02 10:20:21 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 170417    

Description Bastien Nocera 2005-09-29 12:49:07 UTC
1) check the mapping with 'xmodmap -pp' (it should be Button=Code)
2) change the mapping with 'xmodmap -e "pointer = 3 2 1 4 5" '
3) check the mapping again ('xmodmap -pp') it should have buttons 3 and 1 swapped
4) the mouse should then behave as known-broken (left and right behaving like
the right mouse button)

In /etc/X11/XF86Config (or /etc/X11/xorg.conf) the 'ServerLayout' section looks
like:
Section "ServerLayout"
       Identifier     "Default Layout"
       Screen      0  "Screen0" 0 0
       InputDevice    "Keyboard0" "CoreKeyboard"
       InputDevice    "DevInputMice" "AlwaysCore"
EndSection

If changed to look like the following, the button swap will work:
Section "ServerLayout"
       Identifier     "Default Layout"
       Screen      0  "Screen0" 0 0
       InputDevice    "Keyboard0" "CoreKeyboard"
       InputDevice    "DevInputMice" "CorePointer"
EndSection

This problem happens on a bare X (failsafe with only twm and xterm). Note that
the problem also occurs on RHEL4, and FC4's x.org.

Comment 1 Mike A. Harris 2005-10-03 06:39:39 UTC
I believe we looked into this before, and it wasn't a bug, but a limitation
in xmodmap et al.  We'll need to re-investigate this during the RHEL4U3
cycle, but it probably falls under the lines of "feature enhancement request".