Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 498249 - Can't switch mapping for physical buttons, but not tap
Summary: Can't switch mapping for physical buttons, but not tap
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-settings-daemon
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Peter Hutterer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: fedora-x-target
TreeView+ depends on / blocked
 
Reported: 2009-04-29 15:39 UTC by Bastien Nocera
Modified: 2009-10-27 01:25 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-10-27 01:25:07 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 599623 0 None None None Never

Description Bastien Nocera 2009-04-29 15:39:49 UTC 
Either through lack of documentation, or because it's really not supported, there's no way to switch button mapping without reassigning the tap behaviour as well.

It should be possible to swap the left/right physical buttons on the touchpad, but let the "tap" be button 1.

Currently, gnome-settings-daemon will ignore all the touchpads. Once it's possible to swap only the physical buttons, we can remove that behaviour in gnome-settings-daemon.
Comment 1 Peter Hutterer 2009-04-29 22:07:13 UTC 
This is awkward but: the button mapping is handled in the server, tapping in the driver.

So if you switch tapping to 3-2-1 and the device button mapping to 3-2-1, tap 1 comes through as button 1 while phys. button 1 comes through as button 3.

I'll add this to the man page.
Comment 2 Bastien Nocera 2009-04-29 22:54:47 UTC 
How would we do this programmatically?
Comment 3 Peter Hutterer 2009-04-30 00:28:24 UTC 
The button mapping through XSetDeviceButtonMapping as usual, the TapButton by changing the property on the synaptics driver. 

http://cvs.fedoraproject.org/viewvc/rpms/gnome-settings-daemon/F-11/gnome-settings-daemon-2.26.0-support-touchpads.patch?revision=1.1&view=markup

set_tap_to_click (gboolean state) does it for the normal 1/3/2 mapping, you'd just need to set it to 3/1/2.
Comment 4 Adam Williamson 2009-07-17 18:10:06 UTC 
Discussed at today's critical bug review meeting. Jesse opined that it's an annoyance, not truly an issue that should block release. I didn't have a strong opinion. So we're dropping it to F12Target on that basis.

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers
Comment 5 Peter Hutterer 2009-10-26 06:30:14 UTC 
Filed as GNOME bug 599623 (https://bugzilla.gnome.org/show_bug.cgi?id=599623)

Fixed in build: http://koji.fedoraproject.org/koji/taskinfo?taskID=1768089
Requested for F12 final.
Comment 6 Adam Williamson 2009-10-27 01:25:07 UTC 
tag request was accepted, closing.

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers
Note You need to log in before you can comment on or make changes to this bug.