I have a Logitech NX80 mouse and a custom mapping in my xorg.conf:

Code: Select all

Section "InputDevice"
    ### Logitech NX80 (laser)
    Identifier   "Mouse"
    Driver   "evdev"
    #Option   "Name"         "Logitech USB Receiver"
    Option   "Device"      "/dev/input/event4"
    Option   "Resolution"      "1000"   ### The right resolution of this mouse
    Option   "ReopenAttempts"   "300"   ### So that X finds the mouse again when un- and re-plugged
    Option    "ButtonMapping"      "1 0 3 4 5 6 7 8 2"   ### For "middle" button to work on the button 9
 EndSection
 
 Section "InputDevice"
    Identifier   "Synaptics"
    Driver      "synaptics"
    Option   "Device"      "/dev/input/event6"
    Option   "Protocol"      "auto-dev"
    Option   "LeftEdge"      "1700"
    Option   "RightEdge"      "5300"
    Option   "TopEdge"      "1700"
    Option   "BottomEdge"      "4200"
    Option   "FingerLow"      "25"
    Option   "FingerHigh"      "30"
    Option   "MaxTapTime"      "180"
    Option   "MaxTapMove"      "220"
    Option   "VertScrollDelta"   "100"
    Option   "MinSpeed"      "0.09"
    Option   "MaxSpeed"      "0.18"
    Option   "AccelFactor"      "0.0015"
    Option   "SHMConfig"      "true"
    Option   "Repeater"      "/dev/ps2mouse"
    ### KSynaptics says I need UseShm
    Option   "UseShm"      "true"
 EndSection


As you can see the mapping is mainly there to solve the (physically) missing button 2.

This setting works normally under:

• KDM
• Fluxbox
• (probably elsewhere, but I haven't tried it)

The problem is that it doesn't work in KDE itself — that is when I log into my KDE session, my custom X mouse binding is overridden by what I suspect is the KControl mouse module (where you can select your scrolling speed, if you're right- or left-handed etc.).

If anyone knows how I can make KDE not meddle with the mouse settings, I'd be more then happy to know. It's odd that the 'kxkb' keyboard layout module is optional in KControl, but the mouse settings aren't and the user can't seem to turn them off.

What I currently do to work around this problem is run

Code: Select all

xmodmap -e "pointer = 1 9 3 4 5 6 7 8 2"

after I log into KDE. This works, but it annoys me greatly to have to manually force a setting over an automatically forced wrong setting over a completely workable and correct setting in 'xorg.conf'.

P.S. I'm using KDE 3.5.9 and evdev 2.1_rc3 (needed for ButtonMapping in evdev)
P.P.S. Bug 68372 seems to be connected to this problem.

Oddly, when I switched to Evdev and HAL to handle my input devices and removed those settings from xorg.conf, it started working.

For all others who would want to migrate from xorg.conf to HAL handling their devices (and getting RandR to work their dual-head), I've written a HOWTO on my webpage.

After switching to HAL and Evdev whenever the mouse gives me trouble (i.e. when X/KDE (re)starts), I just plug it out and in again.

This triggers HAL to reconsider it and apply the settings set in the .fdi file(s), which overrides any defaults that X or KDE (or any other DE for that matter) try to assume.