KDE mouse control fails to set touchpad for left-handed operation

Bug #46854 reported by Courtney Rosenthal
22
Affects Status Importance Assigned to Milestone
kdebase (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: kcontrol

Environment is:
* Dell Inspiron 600m
* AlpsPS/2 Glidepoint touchpad
* Ubuntu Dapper
* KDE desktop
* kcontrol 3.5.2-0ubuntu26

Perform: System Settings -> Mouse -> Left handed -> apply

This does not have any effect on the touchpad button order (i.e. button 1 remains the left button).

The Gnome control panel works correctly, the touchpad buttons can be remapped.

Also ... in previous versions of Ubuntu, the Alps Glidepoint appeared as a 12-button mouse to X, and I could remap the touchpad for left-handed use by saying:

xmodmap -e 'pointer = 3 2 1 4 5 6 7 8 9 10 11 12'

Now when I try that I get an error:

xmodmap: commandline:1: bad number of buttons, must have 9 instead of 12
xmodmap: 1 error encountered, aborting.

I have a guess at what is causing the xmodmap behavior ... in previous releases I set touchpad as my CorePointer and did not configure any other pointing devices.

In the default Dapper installation the PS/2 port (currently empty) is set as the CorePointer, and I suspect xmodmap may be trying to reconfigure that. Maybe kcontrol is doing the same???

Here are relevant sections from my configuration:

Section "ServerLayout"
        Identifier "Default Layout"
        Screen "Default Screen"
        InputDevice "Generic Keyboard"
        InputDevice "Configured Mouse"
        InputDevice "stylus" "SendCoreEvents"
        InputDevice "cursor" "SendCoreEvents"
        InputDevice "eraser" "SendCoreEvents"
        InputDevice "Synaptics Touchpad"
EndSection

Section "InputDevice"
        Identifier "Configured Mouse"
        Driver "mouse"
        Option "CorePointer"
        Option "Device" "/dev/input/mice"
        Option "Protocol" "ExplorerPS/2"
        Option "ZAxisMapping" "4 5"
        Option "Emulate3Buttons" "true"
EndSection

Section "InputDevice"
        Identifier "Synaptics Touchpad"
        Driver "synaptics"
        Option "SendCoreEvents" "true"
        Option "Device" "/dev/psaux"
        Option "Protocol" "auto-dev"
        Option "HorizScrollDelta" "0"
        # local additions below
        Option "SHMConfig" "on"
        Option "TapButton1" "3"
        Option "TapButton3" "1"
EndSection

Revision history for this message
Courtney Rosenthal (courtneyr) wrote :

Correction, in the paragraph:

    This does not have any effect on the touchpad button order (i.e. button 1 remains the right button).

Please s/right/left/

description: updated
Revision history for this message
Yuriy Kozlov (yuriy-kozlov) wrote :

I can confirm this on Kubuntu Feisty on an Asus V6J laptop. The setting affects a usb mouse, but not the touchpad.

Changed in kdebase:
status: Unconfirmed → Confirmed
Revision history for this message
Yuriy Kozlov (yuriy-kozlov) wrote :
Revision history for this message
Markus Kienast (elias1884) wrote :

This is the same for gnome-mouse-settings! If I set mouse speed and acceleration this should affect my touchpad as well, but it does not. In fact, even the touchpad settings, in case gsynaptics is installed, do not actually affect the touchpad speed.

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Seems to work ok in Intrepid.

Changed in kdebase:
status: Confirmed → Fix Released
Revision history for this message
Courtney Rosenthal (courtneyr) wrote :

The problem is NOT FIXED. The status was changed without checking with the bug submitter.

Changed in kdebase:
status: Fix Released → Confirmed
Revision history for this message
Courtney Rosenthal (courtneyr) wrote :

Yikes! I'm very sorry. I confirm this problem is fixed. I got this confused with another KDE bug I have outstanding. Sorry.

Changed in kdebase:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.