Bug 232630 - Tap feature of touchpad not fully implemented [NEEDINFO]
Tap feature of touchpad not fully implemented
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: synaptics (Show other bugs)
5.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Peter Hutterer
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-03-16 10:05 EDT by Charles A. Landemaine
Modified: 2014-06-02 09:19 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2014-06-02 09:19:10 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
pm-rhel: needinfo? (landemaine)


Attachments (Terms of Use)
The original xorg.conf file (566 bytes, text/plain)
2007-03-21 09:46 EDT, Charles A. Landemaine
no flags Details
The Xorg log file (35.03 KB, text/plain)
2007-03-21 09:47 EDT, Charles A. Landemaine
no flags Details
The Xorg log file after removing xorg.conf and rebooting (43.37 KB, text/plain)
2007-03-21 10:01 EDT, Charles A. Landemaine
no flags Details
xorg-log (28.99 KB, text/plain)
2008-05-15 12:18 EDT, Jonas Nyman
no flags Details
xorg.log (21.47 KB, text/plain)
2008-05-15 12:19 EDT, Michael A G Lacintra
no flags Details

  None (edit)
Description Charles A. Landemaine 2007-03-16 10:05:35 EDT
I have an AlpsGlide Synaptics touchpad. The drag and drop feature doesn't work 
with my touchpad if I use it together with the tap feature. In other words, if 
I hit twice the touchpad without releasing it, over a file, and if I try 
dragging this file to a different directory, moving my finger over the 
touchpad, the file doesn't move to the other directory.
Comment 1 David Zeuthen 2007-03-16 13:07:40 EDT
Not sure why you filed this against nautilus-media; reassinging to Nautilus.
Btw, sounds like an X11 bug to me, not sure though, so I'll let Alex decide.
Comment 2 David Zeuthen 2007-03-16 13:14:42 EDT
Wrong CC
Comment 3 Alexander Larsson 2007-03-19 06:00:48 EDT
I have no idea what tap is supposed to do, but its nothing nautilus ever cares
explicitly about. Its likely an X issue or driver issue.
Comment 4 Charles A. Landemaine 2007-03-19 07:47:57 EDT
Please refer to the original message for explanations on what tap is supposed 
to do.
Comment 5 Matěj Cepl 2007-03-20 17:11:00 EDT
Thanks for the bug report.  We have reviewed the information you have provided
above, and there is some additional information we require that will be helpful
in our diagnosis of this issue.

Please attach your X server config file (/etc/X11/xorg.conf) and X server log
file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file
attachments using the bugzilla file attachment link below.

Could you please also try to run without any /etc/X11/xorg.conf whatsoever and
let X11 autodetect your display and video card? Attach to this bug
/var/log/Xorg.0.log from this attempt as well, please.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.
Comment 6 Charles A. Landemaine 2007-03-21 09:46:34 EDT
Created attachment 150572 [details]
The original xorg.conf file
Comment 7 Charles A. Landemaine 2007-03-21 09:47:36 EDT
Created attachment 150573 [details]
The Xorg log file
Comment 8 Charles A. Landemaine 2007-03-21 10:01:13 EDT
Created attachment 150575 [details]
The Xorg log file after removing xorg.conf and rebooting

After removing xorg.conf and rebooting, the tap feature of my touchpad still
doesn`t work.
Comment 9 Matěj Cepl 2007-03-21 16:31:24 EDT
It might be something so simple as improper configuration of your touchpad --
which doesn't make it less bug, because auto-detection should work -- but it
could be possible to overcome this bug by configuring it yourself.

Could you try to edit /etc/X11/xorg.conf (you have to be root to do it; and
don't forget to make a backup copy of the file) and add this new section to it?

Section "InputDevice"
	Identifier  "Touchpad"
	Driver      "synaptics"
	Option	    "Protocol" "auto"
	Option	    "Device" "/dev/input/mice"
	Option	    "ZAxisMapping" "4 5 6 7"
EndSection

(your settings may differ, more details could be find in synaptics(5) manpage)
and then change the section "ServerLayout" (should be on the top of the file) so
that it refers to your new InputDevice. Like this (the only change should be the
one regarding your touchpad, left the rest as it is even if it differs from this
example):

Section "ServerLayout"
	Identifier     "single head configuration"
	Screen      0  "Screen0" 0 0
	InputDevice    "Touchpad" "CorePointer"
	InputDevice    "Keyboard0" "CoreKeyboard"
EndSection

Restart X and try it again. Does it help?
Comment 10 Charles A. Landemaine 2007-03-21 17:11:03 EDT
No, it still doesn't work. I didn't find any solution in the man page either.
The following line caused the touchpad to be very slow also:

InputDevice    "Touchpad" "CorePointer"
Comment 11 Hendrik Borghorst 2008-04-12 17:31:47 EDT
I can confirm it on Asus EEE-PC. Tapping is not working
Comment 12 Jonas Nyman 2008-05-15 12:18:22 EDT
Created attachment 305504 [details]
xorg-log
Comment 13 Michael A G Lacintra 2008-05-15 12:19:15 EDT
Created attachment 305505 [details]
xorg.log
Comment 14 RHEL Product and Program Management 2014-03-07 08:44:50 EST
This bug/component is not included in scope for RHEL-5.11.0 which is the last RHEL5 minor release. This Bugzilla will soon be CLOSED as WONTFIX (at the end of RHEL5.11 development phase (Apr 22, 2014)). Please contact your account manager or support representative in case you need to escalate this bug.
Comment 15 RHEL Product and Program Management 2014-06-02 09:19:10 EDT
Thank you for submitting this request for inclusion in Red Hat Enterprise Linux 5. We've carefully evaluated the request, but are unable to include it in RHEL5 stream. If the issue is critical for your business, please provide additional business justification through the appropriate support channels (https://access.redhat.com/site/support).

Note You need to log in before you can comment on or make changes to this bug.