Created attachment 693011 [details] current output of "synclient" Description of problem: On a Samsung NP300X4D, with an Elantech clickpad, two finger scoll (in any direction) is activated by any type of 2nd touch. Further, the 2nd touch seems to disable palm detection for the first touch. The 2nd touch may have any size or movement in any direction. Only the first touch controls scroll direction. It could very well be related the hardware, or an unimplemented gesture. Either way, the end result feels incorrect. Sometimes I get scrolling in text windows while typing, especially when coming back to the home row from above. Version-Release number of selected component (if applicable): 1.6.2-2.fc17 How reproducible: always Steps to Reproduce: 1. execute: synclient VertTwoFingerScroll=1 HorizTwoFingerScroll=1 PalmDetect=1 2. Touch touchpad with one fingertip and remain in contact. 3. With other hand, lay palm on touch pad. 4. Move first finger up down/left right to scroll. Actual results: Scrolling. Expected results: No scrolling. Additional info: dmesg|grep -i elan [ 1.951331] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x361f00) [ 1.974245] psmouse serio1: elantech: Synaptics capabilities query result 0x41, 0x15, 0x0f. [ 2.052463] input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input4
According to synclient -m: when a 2nd finger is detected, the Z and W values become fixed at the value of the 1st finger at the time of 2nd finger detection. If I add a 3rd finger, then remove the 1st, z and w are reset to follow the 2nd finger, and are again fixed until only a single finger is detected. synaptics.c has: 1872: if (hw->numFingers > 1 || /* more than one finger -> not a palm */ If hardware does not report dimensions for each touch, then this makes sense, and there may not be a fix. However if new hardware reports dimensions for multiple touches, then might be the place to update the code. synclient does not appear able to report sizes for more than one touch, so I guess the next step is looking at the code for synclient and the elantech kernel module.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.