Created attachment 379388 [details] lshal after boot Description of problem: I can't disable tap using hal policy, but i can disable it when i use 'synclient TapButton1=0' Version-Release number of selected component (if applicable): xorg-x11-drv-synaptics-1.2.0-2.fc12.i686 How reproducible: always Steps to Reproduce: 1. cp /usr/share/hal/fdi/policy/20thirdparty/10-synaptics.fdi /etc/hal/fdi/policy/ 2. edit that file, remove comment section, add "<merge key="input.x11_options.TapButton1" type="string">0</merge>" 3. reboot Actual results: Single finger tap is enable Expected results: Single finger tap is disable Additional info: i think hal policy is loaded, but i dont know why xorg didnt respect that
Created attachment 379389 [details] hal policy
Created attachment 379390 [details] xorg log
system-preferences-mouse, touchpad tab, is it enabled there? If not, the session applies your user settings after logging in and overwrites the system settings set in HAL.
Yes it is enable This is my touchpad tab on mouse preferences: General Disable touchpad while typing [uncheck, when activate this option, nothing happen i think it is another bug] Enable mouse clicks with touchpad [checked, text and option are grey, i cann't change this option] Scrolling Two-finger scrolling Enable horizontal scrolling [checked]
(In reply to comment #4) > Yes it is enable right, this is the reason why tapping is enabled in the session then, g-s-d overwrites the setting in hal. > Enable mouse clicks with touchpad [checked, text and option are grey, i cann't > change this option] if it is greyed out, this means the touchpad didn't detect a physical button on your machine. In this case the tool won't let you disable tapping as this would mean you would lose the ability to enable it again (since you couldn't click it without plugging in an extra mouse). out of interest - why do you want to disable tapping?
(In reply to comment #5) > right, this is the reason why tapping is enabled in the session then, g-s-d > overwrites the setting in hal. > > if it is greyed out, this means the touchpad didn't detect a physical button on > your machine. In this case the tool won't let you disable tapping as this would > mean you would lose the ability to enable it again (since you couldn't click it > without plugging in an extra mouse). > so this is another bug ? my machine is macbookpro 4.1 (it has 1 physical button) > out of interest - why do you want to disable tapping? i don't want to disable tapping, but i want to disable "single finger tap" instead. single finger tap is very annoying, i choose to using physical button for left click, but still activate dual finger tap for right click. single finger tap annoying: when i writing some text, accidently my tumb touching the touchpad and i screw my work (as i said before, i can't disable toucpad while typing via mouse preference, bug ?)
(In reply to comment #6) > (In reply to comment #5) > > so this is another bug ? my machine is macbookpro 4.1 (it has 1 physical > button) hmm, that shouldn't happen then. can you attach the section from /proc/bus/input/devices for this device? > > out of interest - why do you want to disable tapping? > > i don't want to disable tapping, but i want to disable "single finger tap" > instead. > single finger tap is very annoying, i choose to using physical button for left > click, but still activate dual finger tap for right click. > > single finger tap annoying: when i writing some text, accidently my tumb > touching the touchpad and i screw my work (as i said before, i can't disable > toucpad while typing via mouse preference, bug ?) with the current interface, you can't disable a special tap. that's in the works but not there yet (https://bugzilla.gnome.org/show_bug.cgi?id=598820). if you check the disable while typing checkbox, do you see syndaemon spawning? that's what syndaemon is for, so I'd rather we fix this issue for you than have you change the configuration to work around another issue.
Created attachment 383234 [details] my mbp4.1 /proc/bus/input/devices
yes, syndaemon is spawning when i check the disable while typing checkbox. actually they spawn this: "syndaemon -i 0.5 -k" (so, ok .. this is not a bug, thx for pointing to this info) how to change default syndaemon parameter ?
this timeout is hardcoded but you could just untick this box and run sydaemon yourself. the -i flag specifies the number of seconds to disable the touchpad after typing has been detected. In regards to your issue, the check in the control-center applet is wrong, it checks for the presence of LMR buttons and if any is missing, this checkbox is ticked and disabled. The better check would be to check only whether the left mouse button is present. Upstream bug for this issue is: https://bugzilla.gnome.org/show_bug.cgi?id=606793
Please test the scratch build from here: http://koji.fedoraproject.org/koji/taskinfo?taskID=1917728 It includes the patch sent to the upstream bug report. Let me know if that works for you.
Thanks peter, thats work. after upgrade to control-center-filesystem-2.28.1-14.fc12.i686, i can disable finger tap.
sorry, i mean control-center-2.28.1-14.fc12.i686
gnome-settings-daemon-2.28.1-12.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/gnome-settings-daemon-2.28.1-12.fc12
control-center-2.28.1-16.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/control-center-2.28.1-16.fc12
control-center-2.28.1-16.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update control-center'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2010-0769
control-center-2.28.1-16.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.
gnome-settings-daemon-2.28.1-12.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.