Description of problem:The KDE control Module, Touchpad shows tapping enabled but it is not working HP G60 synaptics touchpad. Version-Release number of selected component (if applicable): How reproducible: open touchpad KDE control module and try to set tapping Steps to Reproduce: 1. select tapping enabled 2. click apply Actual results: tapping touchpad does nothing Expected results: tapping touchpad produces a click (according to touchpad settings a left click should be available from tapping the right bottom corner) Additional info: running synclient shows TapButton1 is set to 0 after setting it. Running synclient TapButton1 = 1 switches on tapping (tap anywhere on touchpad is interpreted as a left click). Open touchpad KDE control module and untick Tapping enabled and tapping no longer works (expected) but reticking it does not enable it (not expected). Disable tapping in KDE control. Enable it with synclient, open up KDE control and still shown as not enabled (and not working) (but running synclient shows TapButton set to 1). If you now set tapping in KDE control and click apply then synclient now shows TapButton is set to 0! So changes here do something but not what is expected. NOW if you run synclinet TapButton1 = 1 and check with synclient it really is set to 1 and tapping works. SO tapping only works if first set in KDE control and then set using synclient TapButton1=1. However the left/right click settings as shown in KDE control are not implemented, just a generic tap anywhere for left click. (KDE control does set scrolling on/off on the pad, both horizontal and/or vertical)
Are you sure you tried explicitly enabling single tap = left button? The default is to do nothing. See also bug #688956.
Well, I clicked the enable tapping tick box - fairly explicitly 'enabled tapping' as far as I can see. At the bottom of the dialogue box is this Right-Top Corner means None Right-Bottom corner means Left Button Left-Top Corner means Middle Button Left-Bottom Corner means Right Button One Finger Two Fingers Three Fingers I would not interpret the above as the default is to do nothing. I would say the default is to do what it says it does. Of course it could mean that the corners are defined as to which button they emulate but that the one, two and three finger taps are not defined to take any action. What is the point in that? Basically if you select 'enable tapping' it won't work as the fingers that define the tap are not set. If that is what you mean by the default is to do nothing then that is rather silly as there is no apparent way to change this on the dialogue as these items are not editable. So, how would you suggest, from this dialogue explicitly enabling single tap = left button (or any other tap meaning anything)? See also bug #688956. - Yes I agree, this looks like the same thing but my search did not turn this up for some reason. Sorry
> Well, I clicked the enable tapping tick box - fairly explicitly 'enabled > tapping' as far as I can see. Unfortunately, that's not sufficient, you also need to set an actual tapping action. > At the bottom of the dialogue box is this > Right-Top Corner means None > Right-Bottom corner means Left Button > Left-Top Corner means Middle Button > Left-Bottom Corner means Right Button > One Finger > Two Fingers > Three Fingers > > I would not interpret the above as the default is to do nothing. I would say > the default is to do what it says it does. > Of course it could mean that the corners are defined as to which button they > emulate but that the one, two and three finger taps are not defined to take any > action. That's exactly what it means. So this is the longstanding bug #688956. (Not strictly speaking a bug, just a bad user interface.) > What is the point in that? Basically if you select 'enable tapping' it won't > work as the fingers that define the tap are not set. If that is what you mean > by the default is to do nothing then that is rather silly as there is no > apparent way to change this on the dialogue as these items are not editable. Uh, they are (or at least should be) editable once you check the box to enable tapping. > See also bug #688956. - Yes I agree, this looks like the same thing but my > search did not turn this up for some reason. Sorry Probably because you used the wrong component. kde-settings is the package with the default settings we ship in Fedora, it does NOT contain any software. System Settings is in kde-workspace, but this particular System Settings module is in kcm_touchpad. *** This bug has been marked as a duplicate of bug 688956 ***
(In reply to comment #3) > > Well, I clicked the enable tapping tick box - fairly explicitly 'enabled > > tapping' as far as I can see. > > Unfortunately, that's not sufficient, you also need to set an actual tapping > action. > > > At the bottom of the dialogue box is this > > Right-Top Corner means None > > Right-Bottom corner means Left Button > > Left-Top Corner means Middle Button > > Left-Bottom Corner means Right Button > > One Finger > > Two Fingers > > Three Fingers > > > > I would not interpret the above as the default is to do nothing. I would say > > the default is to do what it says it does. > > Of course it could mean that the corners are defined as to which button they > > emulate but that the one, two and three finger taps are not defined to take any > > action. > > That's exactly what it means. > > So this is the longstanding bug #688956. (Not strictly speaking a bug, just > a bad user interface.) a bad UI? No, a nonsensical UI - does not say to need to change anything, other than the tick box, and does not give you any idea what options you are allowed to enter or the means to enter them. Left click, right click, double click, select and enter - nothing I have tried lets me edit these settings > > > What is the point in that? Basically if you select 'enable tapping' it won't > > work as the fingers that define the tap are not set. If that is what you mean > > by the default is to do nothing then that is rather silly as there is no > > apparent way to change this on the dialogue as these items are not editable. > > Uh, they are (or at least should be) editable once you check the box to > enable tapping. > Nope, impossible to edit them > > See also bug #688956. - Yes I agree, this looks like the same thing but my > > search did not turn this up for some reason. Sorry > > Probably because you used the wrong component. kde-settings is the package > with the default settings we ship in Fedora, it does NOT contain any > software. System Settings is in kde-workspace, but this particular System > Settings module is in kcm_touchpad. Ah so the obvious route to the settings of selecting 'System Settings' from the nice little 'f' button in the bottom left of the desktop and then selecting the obvious 'Input Devices' icon followed by touchpad and then tapping is the wrong way to do this. Silly me, I should have realised So how am I supposed to change this setting and edit the options of one finger two finger etc to get them to do anything? > > *** This bug has been marked as a duplicate of bug 688956 ***
> Nope, impossible to edit them Then either there's another bug or you're doing something wrong. I guess we really need to look into this bug ASAP, I've been wanting to take a look, but never got around to it. (The bug is not personally important to me because I hate tapping. ;-) ) > Ah so the obvious route to the settings of selecting 'System Settings' from the > nice little 'f' button in the bottom left of the desktop and then selecting the > obvious 'Input Devices' icon followed by touchpad and then tapping is the wrong > way to do this. Silly me, I should have realised No, actually, that's the right way to get to it. All the KCMs are embedded in System Settings. But bugs need to be filed against the component which actually implements the KCM, which is kcm_touchpad in this case. And if you're unsure, you should file the bug against kde-workspace, not kde-settings.
So, I just tested this, the stuff is perfectly editable, you just didn't understand the UI. All the actions default to nothing. You have to select "One Finger" from the left list, then "Left Button" from the right list, to assign the action "Left Button" to the event "One Finger". Selecting the event on the left will select the currently assigned action in the list box on the right, select another action on the right and choose Apply to change it.
And to be clear: > Right-Top Corner means None > Right-Bottom corner means Left Button > Left-Top Corner means Middle Button > Left-Bottom Corner means Right Button > One Finger > Two Fingers > Three Fingers You completely misunderstood this. This is not a mapping. You only see the mapped action when you select an event on the left, which automatically selects the currently selected actions. (By default, this is always "None", which is what I meant by "the default is to do nothing".)
Yes, I finally figured this out late last night! Two columns, side by side, one labelled tapping and one labelled means would rather lead one to assume that the side by side items are related to one another, in some direct manner. So, in part, not a bug but a strangely designed UI with no guidance on it and no help available (well at least the default install has no help installed). Now I have figured out how to use the UI it only partly works, but this could be that my touch pad only supports some of the options or some are broken. Not yet sure which. I can set a one finger tap to left click but setting a two finger tap to right button does not do anything. None of the corner settings seem to do anything, with or without the 1,2 or 3 finger settings. Another odd but sort of related thing I found out, while trying to find out how this worked yesterday, is that several screen shots I found showed the option (on the general tab) to stop the touch pad working while typing but my setup does not have this so having to use syndaemon to set this. Seems an odd thing to leave off the UI. Thanks for your patience in helping sort this. This has only become an issue in the last few days as not sitting at a desk with an external mouse and KB. Interestingly, until recently(ish) I was using Kubuntu and tapping was working by default so I never had to play with these settings, but I do remember having to do something to prevent the touch pad working while typing (though I can't remember if this was syndaemon or something else) thanks again
> Another odd but sort of related thing I found out, while trying to find out how > this worked yesterday, is that several screen shots I found showed the option > (on the general tab) to stop the touch pad working while typing but my setup > does not have this so having to use syndaemon to set this. Seems an odd thing > to leave off the UI. That option was removed from the kcm_touchpad UI because it was never actually implemented. (It requires a daemon and kcm_touchpad doesn't ship one.)