Multitouch support not available for Synaptics touchpads v7.2
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
HP tm2 packages |
Fix Released
|
Medium
|
|||
Linux |
Fix Released
|
Medium
|
|||
Open Input Framework |
Fix Released
|
High
|
Henrik Rydberg | ||
Baltix |
Fix Committed
|
Medium
|
Mantas Kriaučiūnas | ||
xf86-input-multitouch (Ubuntu) |
Fix Released
|
Wishlist
|
Daniel Joo Sung Yi | ||
Bug Description
I've tried to enable the multi-touch feature on my Samsung NC10 touchpad enabled (Synaptics) but I did't find a way for correctly do it working.
I've started from this how-to http://
I've tried to run this:
synclient -m 100
but it seems that recognize only a single finger.
This touchpad has multi-touch feature since i correctly make it running under windows xp, but I like to be able to use it under Linux too.
I'm running last updated Intrepid Ubuntu.
Also affecting last updated Karmic (k)ubuntu.
[Possible Fix]
Install this ppa - ppa:utouch-
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Davide P. (scaltro) wrote : | #1 |
Changed in xserver-xorg-input-synaptics: | |
status: | New → Confirmed |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Paweł (paff) wrote : | #2 |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
crashsystems (crashsystems) wrote : | #3 |
Per charlie-tca's recommendation on #ubuntu+1, I'm commenting on this bug early and often. After following the instructions on https:/
#laptop:
bios-version:A02
system-
system-
system-version:Not Specified
#uname-a:
Linux crashsystems 2.6.28-11-generic #35-Ubuntu SMP Wed Mar 18 21:55:34 UTC 2009 x86_64 GNU/Linux
#version_signature
Ubuntu 2.6.28-
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
crashsystems (crashsystems) wrote : | #4 |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Charlie Kravetz (cjkgeek) wrote : | #5 |
Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. Thanks for taking the time to make Ubuntu better!
Changed in xserver-xorg-input-synaptics: | |
importance: | Undecided → Medium |
status: | Confirmed → Triaged |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Viale Fabrice (viale-fabrice) wrote : | #6 |
I have found this tweak. However I have not personally tested it.
http://
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
spi (spi-gmxpro) wrote : | #7 |
This tweak is only a workaround as it uses the option EmulateTwoFinge
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#8 |
If the user touches the touchpad in two locations, then raises the first finger that touched the pad, the mouse jumps to the location of the second finger as if a full move occurred. This happens on Synaptics touchpads.
To reproduce:
Touch the pad in the upper right and hold
Touch with another finger lower left and hold
Release the finger in the upper right
Mouse jumps to lower left edge of the screen, sometimes selecting text along the way
I have noticed a few symptoms related to the problem. They can be tracked down in ComputeDeltas() in synaptics.c:
1) Sometimes deltas are so big that they couldn't possibly happen in so little time (e.g. in less than 20 milliseconds).
2) A comparison between the timestamp in priv->move_hist and hw->millis shows that something went wrong and that an event was skipped, hence the deltas are wrong (or at least bigger than they should be).
3) Usually when 2) takes place, the next few deltas happen to be inaccurate too.
I have written a patch which is more of a workaround for the touchpads that I own and I believe that, at least 2) could be fixed in a better way. Consider the patch as an additional description.
Let me know if there is something I can do to help or where you would like to see this problem fixed.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#9 |
I might be worth checking the finger value too, i.e. if the fingers down go
from 2 to 1, then a jump to another position should possibly be ignored.
Please attach the patch to this bugreport, I'd be interested to see it.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#10 |
Created an attachment (id=25641)
Jumpy cursor patch
Sorry, something went wrong when I tried to attach the patch.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#11 |
The finger value was the 1st thing I checked but it didn't seem to solve the problems that I was experiencing.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#12 |
I just tried this patch and it makes the touchpad quite unpredictable. Moving fast towards a point on the screen (a common thing if you want to close a window) makes the touchpad quite edgy with some movements swallowed, etc.
We can't merge this patch as it is. Can you take the finger value into account in the calculations? i.e. if the previous finger value was 2 and is now 1 and there was a huge movement then smoothen it out?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#13 |
(In reply to comment #4)
> I just tried this patch and it makes the touchpad quite unpredictable. Moving
> fast towards a point on the screen (a common thing if you want to close a
> window) makes the touchpad quite edgy with some movements swallowed, etc.
>
> We can't merge this patch as it is. Can you take the finger value into account
> in the calculations? i.e. if the previous finger value was 2 and is now 1 and
> there was a huge movement then smoothen it out?
>
Sure, I can do that again but it wouldn't work if an event was skipped and we would end up smoothening out the wrong movements.
I'll see what I can do.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#14 |
As this is currently only happening on the touchpads of the newer Minis, would it be acceptable to just detect the model of such touchpads and apply this as a quirk for them?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#15 |
I have a T61 and it's happening for me too, so this doesn't just affect the Dell minis.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#16 |
(In reply to comment #7)
> I have a T61 and it's happening for me too, so this doesn't just affect the
> Dell minis.
>
Right, but the reason why the cursor jumps and the solution to the problem may vary according to models.
For example, let's consider the solution which involves smoothening movements when the previous finger value was 2 and is then 1:
1) The Synaptics touchpad in the Dell Mini 10V doesn't detect multiple fingers and two-fingers emulation doesn't work well. If I want that touchpad to detect 2 fingers (through emulation) I can set the relevant properties manually but then my thumb (or using my index with a slightly bigger pressure) is treated as if it were two fingers. And I can't use this solution because there's no clear way to distinguish between 2 fingers and 1 finger.
2) The Synaptics touchpad in my Fujitsu-Siemens detects multiple fingers (natively) and this solution reduces the issue.
3) The Elantech in my Eee 901 Go doesn't report finger pressure but emulation works well and so on.
Furthermore different values assigned to the "threshold" variable (in my patch) can improve or worsen the situation according to the model.
For this reason I was wondering if quirks could be added for different touchpads (when no general solution can be found).
What do you think?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#17 |
(In reply to comment #8)
> (In reply to comment #7)
> > I have a T61 and it's happening for me too, so this doesn't just affect the
> > Dell minis.
> >
>
[...]
> For this reason I was wondering if quirks could be added for different
> touchpads (when no general solution can be found).
>
> What do you think?
>
I recognize this problem from some time ago. Have you tried applying the ubuntu patches to see if the problem goes away? (apt-get source xserver-
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#18 |
Created an attachment (id=27760)
Quirk - First draft
I was thinking of something like the attached patch.
NOTE: this quirk is just for Synaptics touchpads and therefore it's applied only if priv->model == MODEL_SYNAPTICS.
If the touchpad can detect multi-finger events then, as Peter suggested, we smoothen out movements after the user raises the second finger from the touchpad. This works well with the Synaptics touchpad in my Fujitsu laptop.
If the touchpad can't detect multi-finger events (e.g. the Dell Mini 10v, the HP Mini, etc.) we smoothen movement events which are (usually) too big take place in so little time. I know that this is not perfect but, as reported by our customers, it's still a big improvement. Furthermore I'm not sure how accurate we can be with this kind of touchpads. Better ideas are always welcome though.
What do you think?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#19 |
(In reply to comment #10)
> Created an attachment (id=27760) [details]
> Quirk - First draft
>
> I was thinking of something like the attached patch.
>
> NOTE: this quirk is just for Synaptics touchpads and therefore it's applied
> only if priv->model == MODEL_SYNAPTICS.
fwiw, my synaptics doesn't do multi-finger, so MODEL_SYNAPTICS is not a good quirk selector. priv->has_double and priv->has_triple are set if the touchpad has multi-finger capabilities. This is regardless of the model.
I find the patch quite hard to review, indentation has a certain randomized component to it. the second half (the non-multifinger part) is the one I tested on my non-multifinger pad and it basically made the touchpad unusable for any larger movements. So this part definitely needs fine-tuning.
why is threshold a double? threshold could be based on the pad dimensions too since a movement of 90 on an ALPS is significantly more than on a synaptics pad.
rather than the wasTimeSkipped approach it'd be better to just dump the old values back into the history so dx/dy is automatically 0 on the next run.
(for a final version of that patch, the xf86Msg must disappear too, it'd spam the logs)
> If the touchpad can detect multi-finger events then, as Peter suggested, we
> smoothen out movements after the user raises the second finger from the
> touchpad. This works well with the Synaptics touchpad in my Fujitsu laptop.
I cannot test this. Henrik, any comments?
> If the touchpad can't detect multi-finger events (e.g. the Dell Mini 10v, the
> HP Mini, etc.) we smoothen movement events which are (usually) too big take
> place in so little time. I know that this is not perfect but, as reported by
> our customers, it's still a big improvement. Furthermore I'm not sure how
> accurate we can be with this kind of touchpads. Better ideas are always welcome
> though.
is it possible to make conditional on two-finger emulation in this case. i.e. only smooth if two-finger emu was triggered?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#20 |
(In reply to comment #11)
> fwiw, my synaptics doesn't do multi-finger, so MODEL_SYNAPTICS is not a good
> quirk selector. priv->has_double and priv->has_triple are set if the touchpad
> has multi-finger capabilities. This is regardless of the model.
>
This is why I did "if (priv->
> I find the patch quite hard to review, indentation has a certain randomized
> component to it. the second half (the non-multifinger part) is the one I tested
Yes, I've just noticed that and I'll fix it.
> why is threshold a double? threshold could be based on the pad dimensions too
> since a movement of 90 on an ALPS is significantly more than on a synaptics
> pad.
Good point. Do you refer to priv->minx (etc.) or is there some variable with the physical dimension of the pad?
>
> rather than the wasTimeSkipped approach it'd be better to just dump the old
> values back into the history so dx/dy is automatically 0 on the next run.
>
Ok.
> (for a final version of that patch, the xf86Msg must disappear too, it'd spam
> the logs)
>
Yes, of course. I forgot to remove that.
> is it possible to make conditional on two-finger emulation in this case. i.e.
> only smooth if two-finger emu was triggered?
>
Yes but two-finger emulation doesn't really work well on the Dell Mini 10v therefore it never gets triggered.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#21 |
(In reply to comment #9)
> I recognize this problem from some time ago. Have you tried applying the ubuntu
> patches to see if the problem goes away? (apt-get source
> xserver-
> additional patches available at ubuntuforums for this. I am particularly
> thinking of the patches that disable movement when more than one finger is or
> recently was in contact with the touchpad.
>
I wrote the patches in Ubuntu (I'm a Canonical employee) but if you have links to additional patches I would be glad to have a look at them.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#22 |
Created an attachment (id=27846)
Quirk - Second draft
This patch has the following changes:
1) threshold is an int;
2) the driver now appends skipped events to priv->move_hist;
3) I added priv->model_version so that we can affect as few touchpads as possible. Now the driver tests priv->model, priv->has_double and priv->model_version before the quirk is applied.
NOTE: this patch should be tested with kernel 2.6.29 or higher, otherwise priv->has_double is always reported = 1 instead of its real value.
Any comments?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Frank Aurich (1100101-gmail) wrote : Re: Multi fingers touch doesn't be correctly recognized | #23 |
The Asus EeePC 1005HA-M is affected by this as well. Multitouch works fine in Windows 7, but synclient only recognizes 1 finger.
Same version of Ubuntu as mentioned above.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#24 |
Created an attachment (id=27915)
Quirk - Third draft
As regards appending skipped events to priv->move_hist, it makes the cursor jump even when only 1 finger is on the touchpad which is not ideal.
I went back to the was_time_skipped approach. The rest of the patch is the same as before.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#25 |
I just compared the first version of the patch "Jumpy cursor patch" with the current third version. I tested the first version a while ago on my touchpad which does _NOT_ have multifinger capabilities. I tested this one too.
My comments were that this makes the touchpad unusable as it is quite easy to trigger the threshold when moving fast. Your solution was to special case it for some models and ignore the problem for all others. This is _not_ a solution.
IIRC, dell have alps touchpads with dimensions of 1024. So calculate the threshold based on that and then we can try if the same calculation is valid for synaptics touchpads.
Also, can you remind me again why we need to fix a behaviour for a functionality that the hardware doesn't support? i.e. why we need to behave properly for multi-finger touches if the touchpad is a single-finger pad? I think we discussed that on IRC once but I forgot.
Having just trawled the launchpad reports I see the following picture:
- you filed a bugreport in launchpad about the behaviour described here.
- you applied a patch in ubuntu
- this caused a regression with other touchpads
https:/
which, incidentally is the same issue I described in comment 4.
- you fixed this regression by making special-casing your touchpad so that those users that reported the regression don't see the effect of the patch anymore.
Can you please point to a user (other than you) who has been affected by this behaviour and who confirms that the patch fixes it?
Because, quite frankly, right now I'm not particularly inclined to add special-cases and half-broken patches to the driver to fix something that doesn't seem to affect a lot of users just so we can not support something that isn't supported by the hardware anyway...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#26 |
(In reply to comment #16)
> IIRC, dell have alps touchpads with dimensions of 1024.
don't know why I thought that, they have synaptics pads.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#27 |
<email address hidden> wrote:
> http://
>
>
>
>
>
> --- Comment #16 from Peter Hutterer <email address hidden> 2009-08-19 17:38:25 PST ---
> I just compared the first version of the patch "Jumpy cursor patch" with the
> current third version. I tested the first version a while ago on my touchpad
> which does _NOT_ have multifinger capabilities. I tested this one too.
>
> My comments were that this makes the touchpad unusable as it is quite easy to
> trigger the threshold when moving fast. Your solution was to special case it
> for some models and ignore the problem for all others. This is _not_ a
> solution.
>
> IIRC, dell have alps touchpads with dimensions of 1024. So calculate the
> threshold based on that and then we can try if the same calculation is valid
> for synaptics touchpads.
>
> Also, can you remind me again why we need to fix a behaviour for a
> functionality that the hardware doesn't support? i.e. why we need to behave
> properly for multi-finger touches if the touchpad is a single-finger pad? I
> think we discussed that on IRC once but I forgot.
>
> Having just trawled the launchpad reports I see the following picture:
> - you filed a bugreport in launchpad about the behaviour described here.
> - you applied a patch in ubuntu
> - this caused a regression with other touchpads
>
> https:/
> which, incidentally is the same issue I described in comment 4.
> - you fixed this regression by making special-casing your touchpad so that
> those users that reported the regression don't see the effect of the patch
> anymore.
>
> Can you please point to a user (other than you) who has been affected by this
> behaviour and who confirms that the patch fixes it?
>
> Because, quite frankly, right now I'm not particularly inclined to add
> special-cases and half-broken patches to the driver to fix something that
> doesn't seem to affect a lot of users just so we can not support something that
> isn't supported by the hardware anyway...
>
>
I concur. Temporarily moving from a multi-touch device to a single-touch
device one is bound to notice that they don't behave the same. Using one
finger to point and click is the only supported gesture on single-touch
devices.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#28 |
(In reply to comment #16)
> I just compared the first version of the patch "Jumpy cursor patch" with the
> current third version. I tested the first version a while ago on my touchpad
> which does _NOT_ have multifinger capabilities. I tested this one too.
>
> My comments were that this makes the touchpad unusable as it is quite easy to
> trigger the threshold when moving fast. Your solution was to special case it
> for some models and ignore the problem for all others. This is _not_ a
> solution.
Right, it's a workaround (after all it's a hardware problem). And it has to be very specific to the touchpad model (i.e. to its real dimensions and resolution).
>
> IIRC, dell have alps touchpads with dimensions of 1024. So calculate the
> threshold based on that and then we can try if the same calculation is valid
> for synaptics touchpads.
I have a few netbooks whose touchpads report the same dimensions but have different sizes in real life. This is why, in my opinion, we cannot rely on the reported dimensions and different thresholds have to be set.
>
> Also, can you remind me again why we need to fix a behaviour for a
> functionality that the hardware doesn't support? i.e. why we need to behave
> properly for multi-finger touches if the touchpad is a single-finger pad? I
> think we discussed that on IRC once but I forgot.
I'm not saying that we should support multi-finger touches but if users (and in my case, customers) complain about the cursor being horribly jumpy (and this is not only a problem of the Dell Mini10v) when they accidentally put more than one finger on their touchpad, I think it's worth doing something to make the problem at least less annoying.
>
> Having just trawled the launchpad reports I see the following picture:
> - you filed a bugreport in launchpad about the behaviour described here.
> - you applied a patch in ubuntu
> - this caused a regression with other touchpads
>
> https:/
> which, incidentally is the same issue I described in comment 4.
> - you fixed this regression by making special-casing your touchpad so that
> those users that reported the regression don't see the effect of the patch
> anymore.
>
> Can you please point to a user (other than you) who has been affected by this
> behaviour and who confirms that the patch fixes it?
Sure:
https:/
and:
https:/
In the second case the one who reported the bug (a colleague of mine) is using my patch (even though he didn't reply in the bug report).
Not to mention the feedback that I received from Dell and other customers, which is why I wanted to fix this upstream.
>
> Because, quite frankly, right now I'm not particularly inclined to add
> special-cases and half-broken patches to the driver to fix something that
> doesn't seem to affect a lot of users just so we can not support something that
> isn't supported by the hardware anyway...
>
I think a final solution (or workaround) would be, as discussed on IRC, a property which allows users to set the threshold...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#29 |
(In reply to comment #19)
> This would be necessary because the kernel doesn't expose enough information
> (and no, ID_VENDOR, ID_PRODUCT and ID_VERSION are not specific enough) to
> identify a specific touchpad model therefore we have to rely on the laptop
> model instead.
the kernel (2.6.31) exports the resolution as well. Are you able to calculate the threshold based on that? That said, as soon as we have that threshold anywhere we kinda need to expose it as an option anyway. but a correct auto-calculation is needed nonetheless.
> https:/
> https:/
both bugs describe the issue where the users clicks a button while using a finger. this is what the Synaptics Area property is already for, if this area doesn't work in this use-case then that's the bit that needs fixing.
can you please test this with the area property set to the correct values, the second finger should not have any effect whatsoever if the area is active.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#30 |
(In reply to comment #20)
> the kernel (2.6.31) exports the resolution as well. Are you able to calculate
> the threshold based on that? That said, as soon as we have that threshold
> anywhere we kinda need to expose it as an option anyway. but a correct
> auto-calculation is needed nonetheless.
>
I'm using kernel 2.6.31 but the resolution is still incorrectly reported as 1x1. I'll look into this problem and see if the resolution can help with this bug.
> > https:/
> > https:/
>
> both bugs describe the issue where the users clicks a button while using a
> finger. this is what the Synaptics Area property is already for, if this area
> doesn't work in this use-case then that's the bit that needs fixing.
> can you please test this with the area property set to the correct values, the
> second finger should not have any effect whatsoever if the area is active.
>
In those cases the Synaptics Area was not set but the property works well when used.
I have noticed that the reports which are more specific to the problem we're dealing with are private reports from our customers. Only members of Canonical's OEM team have access to these reports. I can give you the description of their problems (stripped of private information) if you think it can help.
For example the first two paragraphs of the description that I put in this bug report on freedesktop.org were taken from one of our private reports.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#31 |
(In reply to comment #21)
> (In reply to comment #20)
> I'm using kernel 2.6.31 but the resolution is still incorrectly reported as
> 1x1. I'll look into this problem and see if the resolution can help with this
> bug.
in the driver or in xinput? there's about 5 levels where this can be a bug, so please make sure the driver has the right information.
> I have noticed that the reports which are more specific to the problem we're
> dealing with are private reports from our customers. Only members of
> Canonical's OEM team have access to these reports. I can give you the
> description of their problems (stripped of private information) if you think it
> can help.
>
> For example the first two paragraphs of the description that I put in this bug
> report on freedesktop.org were taken from one of our private reports.
I can understand why two fingers would be used with the special button area. Why else would you use two fingers on a single-touch touchpad?
Looking at the values my touchpad produces here, the ranges that I can trigger with by using two fingers and lifting one are about the same of those when moving fast from one point on the screen to another one.
From an UI point of view, this is quite important: touching the touchpad with two fingers and having the cursor jump is a predictable response that can be avoided by using a single finger only. Having a threshold that cuts off certain movements can interfere with normal usage of the touchpad in a non-deterministic manner.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#32 |
(In reply to comment #22)
> I can understand why two fingers would be used with the special button area.
> Why else would you use two fingers on a single-touch touchpad?
> Looking at the values my touchpad produces here, the ranges that I can trigger
> with by using two fingers and lifting one are about the same of those when
> moving fast from one point on the screen to another one.
>
> From an UI point of view, this is quite important: touching the touchpad with
> two fingers and having the cursor jump is a predictable response that can be
> avoided by using a single finger only. Having a threshold that cuts off certain
> movements can interfere with normal usage of the touchpad in a
> non-deterministic manner.
>
Users can (and do) accidentally put more than one finger on the touchpad, not only in the use case of the Synaptics Area. For example, if you use your index to move the cursor, it can happen that the middle finger (or another finger) accidentally touches the touchpad surface. On the Dell Mini10v and on some other netbooks when this happens the cursor jumps to the other side of the screen which is really not what I would call "predictable behaviour".
Of course on other models this problem is much less noticeable as in your case or on some other netbooks that I own. For this reason I think that we should adopt a case by case approach and apply the threshold only when the problem is unbearable.
I agree with you that cutting off movements is not ideal but in some cases it can really make a difference, which is why I'm more inclined to develop this as a quirk in the fdi file.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#33 |
Created an attachment (id=29076)
Quirk - Fourth draft
I have played a bit with touchpad resolutions and I'm still convinced that touchpads with the same resolution and different physical size should act differently, therefore I don't think we should really relay on the resolution.
I have rewritten the patch so that the threshold is a property which we can set through xinput. Customised thresholds for different laptops can now be added to the fdi file. For example I put different values for HP Mini 1000 and Dell Mini10v.
Thanks to this patch users will be able to experiment with different values for the threshold (when the cursor jumps too much), find the one which solves the problem (or which makes it more bearable), get the output of "lshal | grep system.
Feedback on the patch is welcome.
tags: | added: intrepid |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Jose Bernardo (bernardo-bandos) wrote : Re: Multi fingers touch doesn't be correctly recognized | #34 |
Karmic and jaunty (both lpia) on a asus 1101HA, and I have also this problem. Multi-touch works well in windows XP, not at all in ubuntu . "synclient -m 100" shows only one finger is detected.
tags: | added: jaunty karmic |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Alberto Milone (albertomilone) wrote : | #35 |
I need more information about the problem.
1) If you're using Jaunty, can you install the kernel in the "-proposed" repository, reboot and follow step 3
2) If you're using Karmic, please follow step 3
3) Type:
xinput list --short
and find the name of your touchpad.
then type:
xinput list-props $YOUR_TOUCHPAD
(replace $YOUR_TOUCHPAD with the name of your touchpad in quotation marks)
and attach the output of the command
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Roshan Shariff (roshan.shariff) wrote : | #36 |
- xinput-synaptics.txt Edit (1.6 KiB, text/plain)
I have an Asus 1005HA-P with the same problem (and very likely the same touchpad as Frank Aurich's 1005HA-M above). I'm running karmic, and xinput's output is attached.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Davide P. (scaltro) wrote : | #37 |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Jose Bernardo (bernardo-bandos) wrote : | #38 |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Alberto Milone (albertomilone) wrote : | #39 |
@Jose
The "Synaptics Capabilities" (1, 1, 1, 0, 0) property shows that your touchpad doesn't support multi-touch. You can still use emulation mode but it's not guaranteed to work.
@scaltro
Please follow point 1) first, otherwise I won't be able to help you.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Jose Bernardo (bernardo-bandos) wrote : | #40 |
Strange, as multi-touch works well under wxp. I didn't know that XP had multi touch emulation. I'll try to do a few more tests.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Davide P. (scaltro) wrote : | #41 |
- 2.6.28-15 jaunty proposed Edit (1.3 KiB, text/plain)
The first one was a 2.6.28-15 very well customized by Voria (https:/
Anyway I've attached now the output on 2.6.28-15 from proposed repository.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ritz (jonas-ritz) wrote : | #42 |
EEE PC 1000H running Karmic
My touchpad is a ETPS/2 Elantech Touchpad id=10 XExtensionpointer
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ritz (jonas-ritz) wrote : | #43 |
Forgot to attach the output so here it is:
Device 'ETPS/2 Elantech Touchpad':
Device Enabled (95): 1
Synaptics Edges (242): 53, 1099, 48, 720
Synaptics Finger (243): 25, 30, 256
Synaptics Tap Time (244): 180
Synaptics Tap Move (245): 59
Synaptics Tap Durations (246): 180, 180, 100
Synaptics Tap FastTap (247): 0
Synaptics Middle Button Timeout (248): 75
Synaptics Two-Finger Pressure (249): 257
Synaptics Two-Finger Width (250): 7
Synaptics Scrolling Distance (251): 27, 27
Synaptics Edge Scrolling (252): 1, 1, 0
Synaptics Two-Finger Scrolling (253): 0, 0
Synaptics Move Speed (254): 0.400000, 0.700000, 0.036711, 40.000000
Synaptics Edge Motion Pressure (255): 30, 160
Synaptics Edge Motion Speed (256): 1, 108
Synaptics Edge Motion Always (257): 0
Synaptics Button Scrolling (258): 1, 1
Synaptics Button Scrolling Repeat (259): 1, 1
Synaptics Button Scrolling Time (260): 100
Synaptics Off (261): 0
Synaptics Guestmouse Off (262): 0
Synaptics Locked Drags (263): 0
Synaptics Locked Drags Timeout (264): 5000
Synaptics Tap Action (265): 0, 3, 0, 0, 1, 3, 2
Synaptics Click Action (266): 1, 1, 1
Synaptics Circular Scrolling (267): 0
Synaptics Circular Scrolling Distance (268): 0.100000
Synaptics Circular Scrolling Trigger (269): 0
Synaptics Circular Pad (270): 0
Synaptics Palm Detection (271): 0
Synaptics Palm Dimensions (272): 10, 200
Synaptics Coasting Speed (273): 0.000000
Synaptics Pressure Motion (274): 30, 160
Synaptics Pressure Motion Factor (275): 1.000000, 1.000000
Synaptics Grab Event Device (276): 1
Synaptics Area (277): 0, 0, 0, 0
Synaptics Capabilities (278): 1, 1, 1, 1, 1
Synaptics Jumpy Cursor Threshold (279): 0
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
opus440 (opus440) wrote : | #44 |
Here's mine from an new Acer Aspire 1410 running Karmic beta:
Device 'SynPS/2 Synaptics TouchPad':
Device Enabled (115): 1
Synaptics Edges (260): 1752, 5192, 1620, 4236
Synaptics Finger (261): 24, 29, 255
Synaptics Tap Time (262): 180
Synaptics Tap Move (263): 221
Synaptics Tap Durations (264): 180, 180, 100
Synaptics Tap FastTap (265): 0
Synaptics Middle Button Timeout (266): 75
Synaptics Two-Finger Pressure (267): 280
Synaptics Two-Finger Width (268): 7
Synaptics Scrolling Distance (269): 100, 100
Synaptics Edge Scrolling (270): 1, 1, 0
Synaptics Two-Finger Scrolling (271): 0, 0
Synaptics Move Speed (272): 0.400000, 0.700000, 0.009952, 40.000000
Synaptics Edge Motion Pressure (273): 29, 159
Synaptics Edge Motion Speed (274): 1, 401
Synaptics Edge Motion Always (275): 0
Synaptics Button Scrolling (276): 1, 1
Synaptics Button Scrolling Repeat (277): 1, 1
Synaptics Button Scrolling Time (278): 100
Synaptics Off (279): 0
Synaptics Guestmouse Off (280): 0
Synaptics Locked Drags (281): 0
Synaptics Locked Drags Timeout (282): 5000
Synaptics Tap Action (283): 0, 3, 0, 0, 1, 3, 2
Synaptics Click Action (284): 1, 1, 1
Synaptics Circular Scrolling (285): 0
Synaptics Circular Scrolling Distance (286): 0.100000
Synaptics Circular Scrolling Trigger (287): 0
Synaptics Circular Pad (288): 0
Synaptics Palm Detection (289): 0
Synaptics Palm Dimensions (290): 10, 199
Synaptics Coasting Speed (291): 0.000000
Synaptics Pressure Motion (292): 29, 159
Synaptics Pressure Motion Factor (293): 1.000000, 1.000000
Synaptics Grab Event Device (294): 1
Synaptics Area (295): 0, 0, 0, 0
Synaptics Capabilities (296): 1, 1, 1, 0, 0
Synaptics Jumpy Cursor Threshold (297): 0
I'm not getting any multi-touch though I know that it worked in Windows Vista.
bg@blade:
Parameter settings:
LeftEdge = 1752
RightEdge = 5192
TopEdge = 1620
BottomEdge = 4236
FingerLow = 24
FingerHigh = 29
FingerPress = 255
MaxTapTime = 180
MaxTapMove = 221
MaxDoubleTa
SingleTapTi
ClickTime = 100
FastTaps = 0
EmulateMidB
EmulateTwoF
EmulateTwoF
VertScrollDelta = 100
HorizScroll
VertEdgeScroll = 1
HorizEdgeScroll = 1
CornerCoasting = 0
VertTwoFing
HorizTwoFin
MinSpeed = 0.4
MaxSpeed = 0.7
AccelFactor = 0.00995223
TrackstickSpeed = 40
EdgeMotionMinZ = 29
EdgeMotionMaxZ = 159
EdgeMotionM
EdgeMotionM
EdgeMotionU
UpDownScrolling = 1
LeftRightSc
UpDownScrol
LeftRightSc
ScrollButto
TouchpadOff = 0
GuestMouseOff = 0
LockedDrags = 0
LockedD...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Alberto Milone (albertomilone) wrote : | #45 |
@opus440
The "Synaptics Capabilities" (1, 1, 1, 0, 0) property shows that your touchpad doesn't support multi-touch. You can still use emulation mode but it's not guaranteed to work.
you can try setting the following properties to different values with synclient and see if emulation works:
EmulateTwoFinge
EmulateTwoFinge
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Brad Greco (grecobrad) wrote : | #46 |
I'm also getting the line
Synaptics Capabilities (276): 1, 1, 1, 0, 0
in my output on a eeepc 1005ha. I'm still able to get 2-finger scrolling in Windows using two-finger-scroll (http://
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Jim Braux-Zin (j-brauxzin) wrote : | #47 |
- xinput-synaptics.txt Edit (1.6 KiB, text/plain)
Same problem with an Asus 1005HA-m on an up to date Karmic. I have also the 1, 1, 1, 0, 0 line. I am pretty sure the touchpad can do multi-touch because it's working on windows. However, on Windows it can actually do true multi- touch (opposed to multi-tap) for example to zoom like on the iPhone, so maybe the way for the device to report multi touch has changed.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ritz (jonas-ritz) wrote : | #48 |
The synaptics driver is not working at all with .32-rc3
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Michael Mulqueen (michael.mulqueen) wrote : | #49 |
This bug may be related. It is not necessarily a duplicate.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Robert Casties (r0bcas7) wrote : | #50 |
doing
synclient EmulateTwoFinge
works fine for me with Karmic (fresh install of final release) on a EEEPC 1005HA. I had to fiddle with the different EmulateTwoFingerXXX settings in earlier releases but since Karmic-final the defaults are ok for me apart from the MinZ setting.
What is the proposed way of saving that setting in the system? Is /etc/hal/fdi/policy the right place as HAL is supposedly no longer there?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Michael Mulqueen (michael.mulqueen) wrote : Re: [Bug 308191] Re: Multi fingers touch doesn't be correctly recognized | #51 |
I have just tried that workaround (the synclient ...MinZ=10 one) but
it doesn't work for me. The command executes fine, it just has no
effect, even if I fiddle with gnome-mouse-
settings are almost entirely the defaults if not entirely the
defaults. Perhaps this bug affects different touchpads in different
ways (my touchpad is an ALPS Glidepoint one), what is yours? Post a
copy of this command if possible:
xinput list | grep -i pointer
Regarding making a permanent change to the touchpad configuration: I'm
not sure in all honesty. I think you can specify it in xorg.conf
(although, by default X doesn't use a configuration file any more, but
it will read one if it exists). HAL is being depreciated, but to my
understanding, it is still in progress (with input devices still being
handled with HAL rather than udev) but by no means finished. This wiki
page provides some details:
https:/
Out of interest, has anyone tried this with a different distribution?
(non-Debian derived or otherwise)
This bug doesn't seem to be getting that much developer attention, we
should consider raising this upstream (if it's not Debian/Ubuntu
specific).
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Robert Casties (r0bcas7) wrote : Re: Multi fingers touch doesn't be correctly recognized | #52 |
On my eeepc 1005HA (where two finger scrolling works with minz=10) I get:
xinput list | grep -i pointer
"Virtual core pointer" id=0 [XPointer]
"Macintosh mouse button emulation" id=9 [XExtensionPointer]
"SynPS/2 Synaptics TouchPad" id=10 [XExtensionPointer]
and in dmesg:
Synaptics Touchpad, model: 1, fw: 7.2, id: 0x1a0b1, caps: 0xd04731/0xa40000
the complete set from synclient -l:
LeftEdge = 1752
RightEdge = 5192
TopEdge = 1620
BottomEdge = 4236
FingerLow = 24
FingerHigh = 29
FingerPress = 255
MaxTapTime = 180
MaxTapMove = 221
MaxDoubleTa
SingleTapTi
ClickTime = 100
FastTaps = 0
EmulateMidB
EmulateTwoF
EmulateTwoF
VertScrollDelta = 100
HorizScroll
VertEdgeScroll = 0
HorizEdgeScroll = 0
CornerCoasting = 0
VertTwoFing
HorizTwoFin
MinSpeed = 0.4
MaxSpeed = 0.7
AccelFactor = 0.00995223
TrackstickSpeed = 40
EdgeMotionMinZ = 29
EdgeMotionMaxZ = 159
EdgeMotionM
EdgeMotionM
EdgeMotionU
UpDownScrolling = 1
LeftRightSc
UpDownScrol
LeftRightSc
ScrollButto
TouchpadOff = 0
GuestMouseOff = 0
LockedDrags = 0
LockedDragT
RTCornerButton = 0
RBCornerButton = 3
LTCornerButton = 0
LBCornerButton = 0
TapButton1 = 1
TapButton2 = 3
TapButton3 = 2
ClickFinger1 = 1
ClickFinger2 = 1
ClickFinger3 = 1
CircularScr
CircScrollDelta = 0.1
CircScrollT
CircularPad = 0
PalmDetect = 0
PalmMinWidth = 10
PalmMinZ = 199
CoastingSpeed = 0
PressureMot
PressureMot
PressureMot
PressureMot
GrabEventDevice = 1
AreaLeftEdge = 0
AreaRightEdge = 0
AreaTopEdge = 0
AreaBottomEdge = 0
JumpyCursor
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Chrisitan (the-doctor) wrote : | #53 |
Can confirm this on my EeePC 1005PE.
Seems to affect several types of netbooks.
I solved it by setting EmulateTwoFinge
Try using:
#synclient EmulateTwoFinge
with shmconfig enabled and set this in your fdi/xorg.conf file.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Erik Andrén (erik-andren) wrote : | #54 |
dawn2k, that is only a workaround but doesn't address the real issue. I currently suspect that the specs on Synaptics site is outdated and that there is another way of detecting multitouch which isn't specified.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
dan (dumbledore3) wrote : | #55 |
i can confirm the same problem on a brand new acer aspire 1810t. same output from xinput, the 1, 1, 1, 0, 0. strange since the touchpad even comes with a sticker on it which says it supports multitouch, with all sorts of pinching pictures...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Dana Goyette (danagoyette) wrote : | #56 |
- SynDiag2010-01-25_16-16-08.log Edit (398.7 KiB, text/plain)
I just reported a bug: https:/
Handy hint for in Windows: go to the mouse control panel and press "alt-shift-i", and it will give you a debug dialog. I have attached the saved diagnostics details here.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
vitalic (kyliewilson) wrote : | #57 |
ive managed to get multi touch working, but its terrible. i cant believe how bad this is considering it worked flawlessly on windows. its taken me about 10 hours of tweaking to get it to a semi-satisfactory level when it took 1 minute to set up on xp.
there are jerky mouse movements when you leave one finger down after scrolling, sometimes it keeps scrolling after you stop moving your fingers, the two/three finger touch emulation doesnt work half of the time, sometimes you try and middle click and it thinks you are scrolling and moves half way down the page, sometimes you have to tap 3 or 4 times before it recognises it.
how hard can it be to get right? dont tell me "your netbook doesnt support multi touch", it DOES because when i first bought the thing i immediately tried to set up multitouch on xp and it worked perfectly (scrolling, middle clicking, right clicking) and as soon as i installed netbook remix it didnt work at all.
for the people still trying to get it working to some degree, this post will help: http://
the HAL stuff doesnt work any more so just run the script towards the end. personally i had to tweaks the values to get it working, my values were
xinput set-int-prop "SynPS/2 Synaptics TouchPad" "Synaptics Two-Finger Pressure" 32 11
xinput set-int-prop "SynPS/2 Synaptics TouchPad" "Synaptics Two-Finger Width" 32 5
xinput set-int-prop "SynPS/2 Synaptics TouchPad" "Synaptics Jumpy Cursor Threshold" 32 0
you can make this script run after login by adding it to /etc/gdm/
for people trying to set up two touch middle click, wow thats another thing that doesnt work out of the box and there is no way to change it because of a bug. what i did was make a script which executes "synclient TapButton2=2 TapButton3=3" and create an entry in startup applications so it runs after login, this makes three finger touch = right click and two finger touch = middle click the way it *should* be by default but the shitty developers of this mess decided otherwise
please sort this out because you are ruining my netbook experience
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Dana Goyette (danagoyette) wrote : | #58 |
I've attached a video of my touchpad spazzing out as I try moving around with two or three fingers. Unfortunately, gtk-recordmydesktop can't keep up with the desktop drawing under compiz, and I need compiz to get the "showmouse" flame-ring. Observe how it leaves trails from movements way too fast to be reasonable.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Dana Goyette (danagoyette) wrote : | #59 |
- dana_nocrash.profile Edit (8.5 KiB, text/plain)
An attempt at making the spazzing more visible: "Annotate" plugin.
I would imagine fixing the multi-finger detection should fix this spazzing cursor issue.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Dana Goyette (danagoyette) wrote : | #60 |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Tournier Mathieu (mathieutournier) wrote : | #61 |
Same problem here on a dell xps 16 (1640)
The multitouch works on windows but is not recognize by hal.
xinput list-props "SynPS/2 Synaptics TouchPad"
Device 'SynPS/2 Synaptics TouchPad':
Device Enabled (116): 1
Synaptics Edges (263): 1752, 5192, 1620, 4236
Synaptics Finger (264): 24, 29, 255
Synaptics Tap Time (265): 180
Synaptics Tap Move (266): 221
Synaptics Tap Durations (267): 180, 180, 100
Synaptics Tap FastTap (268): 0
Synaptics Middle Button Timeout (269): 75
Synaptics Two-Finger Pressure (270): 280
Synaptics Two-Finger Width (271): 7
Synaptics Scrolling Distance (272): 100, 100
Synaptics Edge Scrolling (273): 1, 1, 1
Synaptics Two-Finger Scrolling (274): 0, 0
Synaptics Move Speed (275): 0.400000, 0.700000, 0.009952, 40.000000
Synaptics Edge Motion Pressure (276): 29, 159
Synaptics Edge Motion Speed (277): 1, 401
Synaptics Edge Motion Always (278): 0
Synaptics Button Scrolling (279): 1, 1
Synaptics Button Scrolling Repeat (280): 1, 1
Synaptics Button Scrolling Time (281): 100
Synaptics Off (282): 1
Synaptics Guestmouse Off (283): 0
Synaptics Locked Drags (284): 0
Synaptics Locked Drags Timeout (285): 5000
Synaptics Tap Action (286): 0, 0, 0, 0, 1, 0, 0
Synaptics Click Action (287): 1, 1, 1
Synaptics Circular Scrolling (288): 0
Synaptics Circular Scrolling Distance (289): 0.100000
Synaptics Circular Scrolling Trigger (290): 0
Synaptics Circular Pad (291): 0
Synaptics Palm Detection (292): 0
Synaptics Palm Dimensions (293): 10, 199
Synaptics Coasting Speed (294): 3.000000
Synaptics Pressure Motion (295): 29, 159
Synaptics Pressure Motion Factor (296): 1.000000, 1.000000
Synaptics Grab Event Device (297): 1
Synaptics Area (298): 0, 0, 0, 0
Synaptics Capabilities (299): 1, 1, 1, 0, 0
Synaptics Jumpy Cursor Threshold (300): 0
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
wankel786 (mahatama) wrote : | #62 |
Tournier Mathieu, have you been able to solve this issue? I also have an XPS 1640 that does not recognize multi finger in touching in linux.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
lenios (lenios) wrote : | #63 |
i had the same issue with karmic and now lucid, and a working workaround (at least on eeepc 901) is to execute the two following commands:
$ synclient TapButton3=3
$ synclient TapButton2=2
this will activate right click with two fingers click, and middle (wheel) click with 3 fingers.
I hope it helps.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Neatchee (neatchee) wrote : | #64 |
Confirmed not working on my Acer Aspire 5740 w/ synaptics touchpad.
synclient -m 100 reports single-touch only.
Here is my xinput list-props output:
Device '"SynPS/2 Synaptics TouchPad"':
Device Enabled (125): 1
Device Accel Profile (242): 0
Device Accel Constant Deceleration (243): 1.000000
Device Accel Adaptive Deceleration (245): 1.000000
Device Accel Velocity Scaling (246): 10.000000
Synaptics Edges (247): 1752, 5192, 1620, 4236
Synaptics Finger (248): 24, 29, 255
Synaptics Tap Time (249): 180
Synaptics Tap Move (250): 221
Synaptics Tap Durations (251): 180, 180, 100
Synaptics Tap FastTap (252): 0
Synaptics Middle Button Timeout (253): 75
Synaptics Two-Finger Pressure (254): 280
Synaptics Two-Finger Width (255): 7
Synaptics Scrolling Distance (256): 100, 100
Synaptics Edge Scrolling (257): 1, 0, 0
Synaptics Two-Finger Scrolling (258): 0, 0
Synaptics Move Speed (259): 0.400000, 0.700000, 0.009952, 40.000000
Synaptics Edge Motion Pressure (260): 29, 159
Synaptics Edge Motion Speed (261): 1, 401
Synaptics Edge Motion Always (262): 0
Synaptics Button Scrolling (263): 1, 1
Synaptics Button Scrolling Repeat (264): 1, 1
Synaptics Button Scrolling Time (265): 100
Synaptics Off (266): 1
Synaptics Guestmouse Off (267): 0
Synaptics Locked Drags (268): 0
Synaptics Locked Drags Timeout (269): 5000
Synaptics Tap Action (270): 2, 3, 0, 0, 1, 3, 2
Synaptics Click Action (271): 1, 1, 1
Synaptics Circular Scrolling (272): 0
Synaptics Circular Scrolling Distance (273): 0.100000
Synaptics Circular Scrolling Trigger (274): 0
Synaptics Circular Pad (275): 0
Synaptics Palm Detection (276): 0
Synaptics Palm Dimensions (277): 10, 199
Synaptics Coasting Speed (278): 0.000000
Synaptics Pressure Motion (279): 29, 159
Synaptics Pressure Motion Factor (280): 1.000000, 1.000000
Synaptics Grab Event Device (281): 1
Synaptics Gestures (282): 1
Synaptics Capabilities (283): 1, 1, 1, 0, 0
Synaptics Pad Resolution (284): 103, 57
Synaptics Area (285): 0, 0, 0, 0
Synaptics Jumpy Cursor Threshold (286): 0
I can see that Capabilities is reporting no multitouch support, but the "spazz" behavior that other users have reported seems to indicate a hardware understanding of multitouch that isn't being properly recognized by xinput. Can we force xinput to see the touchpad as having multitouch capabilities to see if it perhaps it's just a device recognition error?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Neatchee (neatchee) wrote : | #65 |
Attaching dmesg, Xorg.0.log, and /proc/bus/
tags: | added: lucid |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Neatchee (neatchee) wrote : | #66 |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Neatchee (neatchee) wrote : | #67 |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Dana Goyette (danagoyette) wrote : | #68 |
I've discovered something new (on another laptop):
By installing these drivers on my non-multi-
http://
I had initially thought it had upgraded my touchpad firmware... but when I booted Linux again, it went right back to single-finger-only.
It seems the Windows drivers must be doing some runtime-only patching of the device firmware.
Now, we just need to figure out how to do the same thing in Linux.
Anyway, this means that the Windows drivers showing real multi-finger do not necessarily mean the touchpad firmware originally supports multi-finger detection.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Michael Mulqueen (michael.mulqueen) wrote : Re: [Bug 308191] Re: Multi fingers touch doesn't be correctly recognized | #69 |
Just confirming that this is still a problem for me on Lucid (no
multi-touch whatever I do). At least now though,
gnome-mouse-
up gsynaptics, it had "Enable Touchpad" unchecked and checking it and
closing gsynaptics had no observable effects.
@Dana Goyette
I believe the synaptics driver has software emulation of multi touch
(for single touch devices), for some reason it isn't working on
certain pads. This is probably not because they were never supported,
because it seems that some people had it working on earlier versions
of Ubuntu.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Neatchee (neatchee) wrote : Re: Multi fingers touch doesn't be correctly recognized | #70 |
@Dana Goyette
There's an easy way to determine in Windows if your trackpad is emulating multitouch or providing real hardware multitouch on newer laptops (running newer trackpad firmware): Open up your Mouse control panel, then press shift+alt+i. This will open a debug window. From there, go to the device0 tab, and look near the bottom for - and i might have the name wrong here - Finger Sensing (#). This value will show you how many fingers the driver is reporting. Now, watch this number while you apply contact to the pad in several different ways. First, touch the pad with two fingers spaced a little bit apart. Next, touch the pad with 3 or 4 fingers spaced with as little space between them as possible. Next, try pressing the entire side of your finger to the pad at once. Does it show more than 1 contact point when you try the second two methods? If so, then the firmware is taking any wide-area contact to the trackpad and assuming that the two edges of the contact area are your two separate fingers, meaning that it is emulating multitouch
I would also note that, strangely, with the updates from a few nights ago, the "spazz" behavior I was previously seeing when I would multi-touch my trackpad has stopped. Touching the trackpad with two fingers now produces normal single-touch mousing behavior.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Dana Goyette (danagoyette) wrote : | #71 |
I can confirm... using the side of one finger, or three fingers immediately adjacent, does give me just one contact area.
Also, I do still have the "spazzing" issue on the netbook.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Jose Bernardo (bernardo-bandos) wrote : | #72 |
On my 1101HA, finger sensing correctly shows 1, 2 or 3 fingers in windows, using the method outlined by Neatchee. It also detects a finger side as 1 finger only. Still, in karmic "synclient -m 100" only detects one finger.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#73 |
We are seeing a similar problem in Lucid. It appears on multi-touch pads when they aren't reporting as multi-touch. Same symptoms. Jumpy cursor.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Jim Rorie (jfrorie) wrote : Re: Multi fingers touch doesn't be correctly recognized | #74 |
I think this is related to the upstream bug:
https:/
It is for a single touch pad, but I'm thinking that our multi-touches are being reported as singles, so it's the same problem.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Jim Rorie (jfrorie) wrote : | #75 |
Ugh, Sorry. The above bug is for the symptom of this problem, jumpy cursor behavior.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Neatchee (neatchee) wrote : | #76 |
@Jim That's actually an unrelated bug. That bug refers to placing two fingers on the touchpad, lifting one, and having the cursor jump from the location of the first touch to the location of the remaining finger, without passing the points in between. This is more of an "incorrect behavior" than a bug, so to speak. This is not related to the "spazz" behavior that users are reporting here.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Neatchee (neatchee) wrote : | #77 |
Errrr, cancel that "without passing the points in between." Either way, unrelated issue.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Martin Maier (ener22gizer) wrote : | #78 |
Can confirmit, exactly the same behaviour as described... fw:7.2, capabilities 1,1,1,0,0
Multiutouch working on Windows
Changed in xserver-xorg-input-synaptics (Ubuntu): | |
status: | Triaged → In Progress |
status: | In Progress → Confirmed |
description: | updated |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Neatchee (neatchee) wrote : | #79 |
Martin: Why was this bug changed from Triaged to Confirmed? This bug had already been confirmed and triaged, but no dev had been assigned.
Otherwise, can I get people to check which version of the firmware they are running if they are experiencing these issues? 6.5 firmware seems to report multitouch capabilities just fine, while it looks like 7.2 firmware is where the problems lie. Does anyone using 7.2 firmware have multitouch working properly?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Martin Maier (ener22gizer) wrote : | #80 |
Sorry, that was my fault. i just registered and played around and wasnt realizing i actually am able to change the status.... i couldnt put it back to triaged, so I changed it back to confirmed.
Sorry for that.
@Neatchee:
As far as I can see every pad wth 7.2 Firmware gets recognised as Touchpad-
Maybe its working on Windows because of some sort of runtime-
Like these (very) old 3-Button-Mouses you had to press the middle Button on startup, otherwise they told the Mainboard theyre only 2-Buton Mouses?
description: | updated |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
wankel786 (mahatama) wrote : | #81 |
Has anyone tried the new synaptics driver that was released a few days ago?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Martin Maier (ener22gizer) wrote : | #82 |
Yep, doesn't change anyting..
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Jim Rorie (jfrorie) wrote : | #83 |
Has anyone looked at this project? It appears someone is rewriting the driver for obvious reasons.
http://
I've tried to load it, but to no avail. Perhaps someone with a little more expertise might chime in.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Bryce Harrington (bryce) wrote : Re: Multitouch support not available for -synaptics | #84 |
Thanks for the reference to the ubuntuforums post. Of course our preference would be to see this included in -synaptics (or -evdev would be even better) so we don't end up with a multitude of different drivers.
summary: |
- Multi fingers touch doesn't be correctly recognized + Multitouch support not available for -synaptics |
Changed in xserver-xorg-input-synaptics (Ubuntu): | |
importance: | Medium → Wishlist |
status: | Confirmed → Triaged |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Bryce Harrington (bryce) wrote : | #85 |
[While this is definitely a legitimate issue, the proposed solution is outside the scope of what can be accomplished with an SRU.]
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Matteo Rossi (teo-red90) wrote : | #86 |
I confirm the bug on a Sony VPCCW2C5E with Synaptics touchpad V7.2.
Windows driver reports up to three fingers with Shift+Alt+i. Under Lucid, synclient -m only one finger. Sometimes I experience some spazzy pointer behavior.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Florian Kriener (florian-kriener) wrote : | #87 |
I too can confirm this bug on a Lenovo Thinkpad t400s with Synaptics Touchpad V7.2 (using Debian though).
However, I want to add, that this does not affect xserver-
python -c 'print 0xd047b1 & (1<<1)'
prints 0 and not 2.
The question is why does it work with windows?
Changed in xorg-driver-synaptics: | |
importance: | Unknown → Undecided |
status: | Unknown → New |
status: | New → Invalid |
Changed in xserver-xorg-input-synaptics (Ubuntu): | |
status: | Triaged → Invalid |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#88 |
For instance please note that this bug also affects Ubuntu Lucid Lync 10.04 and is reported in launchpad under https:/
Files that included are xev output, xorg.0.log file. Another closely related issue reported is the cursor going crazy(instead of being jumpy when reboot from windows) while when booting directly into ubuntu the cursor shows jumpy behaviour as described in this bug report.inspite
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Vish (vish) wrote : Re: Multitouch support not available for -synaptics | #89 |
Re-setting the status back to triaged. Seems to have been an accidental change by RussianNeuroMancer
Changed in xorg-driver-synaptics: | |
importance: | Undecided → Unknown |
status: | Invalid → Unknown |
Changed in xserver-xorg-input-synaptics (Ubuntu): | |
status: | Invalid → Triaged |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
RussianNeuroMancer (russianneuromancer) wrote : | #90 |
Thanks!
Sorry, my mistake.
summary: |
- Multitouch support not available for -synaptics + Multitouch support not available for Synaptics touchpads |
summary: |
- Multitouch support not available for Synaptics touchpads + Multitouch support not available for Synaptics touchpads v7.2 |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Jessica Leigh (blackwednesday) wrote : | #91 |
Hey, someone asked awhile back if any non-Debian users can confirm that this isn't a Debian-specific issue... I'm using Gentoo. I've read that it's a Synaptics firmware issue (looks like between versions 6.2 and 6.3 multi-finger detection got turned off). Don't know if that's true or not, but I've got 7.0, and my capabilities line is 1,0,1,0,0
EmulateTwoFinge
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Gursimran singh (simar) wrote : | #92 |
Jessica, I think you are also affected by the bug because, your synaptics capabilities show 0,0 in the last, which implies that your touchpad lacks multitouch support. What you are using is software emulation of the two finger scroll using EmulateTwoFinge
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#93 |
As of this git commit, there is code to work around cursor jump on multi-touch transitions for majority cases:
This works for both hardware that can report number of fingers and also for cases where it must be emulated from finger width.
As of this next git commit, the default behavior is to enable 2-finger emulation. So effectively, the above patch is working by default for all users.
Based on that, I think the intent of this bug report is addressed and you can consider closing it.
Outstanding issue: On my hardware, I must rely on emulation. If I touch opposite extremes of touchpads with two fingers then hardware gets confused and never reports a finger width big enough to trigger 2-finger logic to debounce cursor jumps. But this is an extreme corner case (I don't see it with typical usage) and may be unique to emulation-based hardware only. I've not be able to reproduce jump as long as 1 finger is fully on touchpad.
For this corner case, it may still be useful to add a check in code to see when current X/Y value is at extreme edge of touchpad and if so do some additional checks to try to guess when its because of a corner case (for example when previous X/Y were on opposite extreme of touchpad).
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
tob (tobynbertram) wrote : | #94 |
I have found the multitouch initialization sequence for the Synaptics V7.4 Clickpad touchpad in my HP dv7t Select. The touchpad uses a new 12 byte protocol for multitouch events after it has been properly initialized. I have not completely figured out the new multitouch protocol. I would imagine that the initialization sequence and multitouch protocol for the Synaptics V7.2 touchpads is similar if not the same as the V7.4 touchpads. More info can be found at https:/
Changed in xorg-driver-synaptics: | |
importance: | Unknown → Medium |
status: | Unknown → Confirmed |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Dana Goyette (danagoyette) wrote : | #95 |
Cool.... now we just need to do that with THIS driver, and we'll get multi-finger on ALL Synaptics touchpads:
http://
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Matteo Rossi (teo-red90) wrote : | #96 |
Well not exactly Dana. Here we're talking about MT support on Synaptics v7.2 which actually has native multitouch support, but it is not recognized by xorg driver. We're not talking about emulation, which by the way I think is already supported in linux.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Dana Goyette (danagoyette) wrote : | #97 |
This other driver is not emulation -- it adds native multitouch to ANY touchpad, even ones that didn't originally do multitouch even in Windows! We just need to sniff out the initialization sequence -- it seems to be patching the firmware on the fly.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Davide P. (scaltro) wrote : | #98 |
Same problem with last Synaptic driver (v7.4) from Maverick.
Do you need other command's log ?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
RussianNeuroMancer (russianneuromancer) wrote : | #99 |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Matt (mattredmond1) wrote : | #100 |
This looks promising...can anybody help me out applying these patches? I can't seem to find a download link. Or will they be part of a future synaptic upgrade?
TIA
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Matteo Rossi (teo-red90) wrote : | #101 |
Guys I found this page which contains three patches by the author reported on phoronix.com (Takashi Iwai):
https:/
I don't know how to compile the driver so if someone wants to try them or tell me the steps to follow I'll be glad to help!
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
hokasch (hokasch) wrote : | #102 |
@ Matt and Matteo
There is a PKGBUILD for Arch Linux here:
http://
The patch files are there, and if you have a look at the PKGBUILD you can see how it is build (these are just bash scripts, you can do the same routine manually and adapt the last "install" part to your distribution/
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Gursimran singh (simar) wrote : | #103 |
Hi there
I don't know what's the current status of the bug. However there's a bug #50626 which got some idea of hacking the windows driver using virtual box
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
tob (tobynbertram) wrote : | #104 |
@Gursimran
I think you posted the wrong bug #. Nevertheless, I have already used VirtualBox to determine the initialization sequence and multitouch protocol; see post #94. Furthermore, Takashi Iwai from Open Suse has released patches to enable experimental multitouch support to the Xorg-devel mailing list. There was a lot of talk a while ago regarding this issue, but it looks like it has quieted down lately.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Dana Goyette (danagoyette) wrote : | #105 |
Would you mind doing the same sniffing for that special driver I linked to? That driver really does enable multi-finger detection on touchpads that have never supported it before, even in Windows!
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Gursimran singh (simar) wrote : | #106 |
@ Tob
Thanks Tob for letting know that and also about your work. Rest all I will read in the bug report when I get time.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Gursimran singh (simar) wrote : | #108 |
@ Dana
You should not any tweaking for enabling multitouch or rather multitouch emulation for synaptics touchpad that does not support multitouch natively. Just do some tweaking with the original synaptics driver(emulation already present) in linux and get the emulation of it working.
See
$man synaptics
Also there's a bug report, that gives a well defined workaround for it. See the bugs in my lp page and search for similar bugs like this one.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
tob (tobynbertram) wrote : | #109 |
@Dana
I don't think that the driver that you linked to is actually using true multitouch. They would have provided pinch-zoom and rotate functionality if they had a true multitouch driver. Some older Synaptics touchpads can report the number of fingers touching the touchpad or the driver can use the width property to determine the number of fingers touching the touchpad. This is what is referred to as emulation.
@Gursimran
You can find more info in Bug #633225
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Dana Goyette (danagoyette) wrote : | #110 |
No, I am quite absolutely sure that that IS enabling real multi-finger detection.... read the comments! It seems to be patching the firmware of the touchpad, somehow.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Dana Goyette (danagoyette) wrote : | #112 |
Anyway, that's not the main issue being discussed on this bug... it's just that the technique you used would be useful for that, too:
https:/
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
hokasch (hokasch) wrote : | #113 |
From all I've seen it is either enabling functions in the windows drivers (not the firmware!), or is simply using emulation (which has turned on by default on linux in recent versions). Check their "advanced features enabled" info here, no multitouch:
http://
Multitouch != Multi-Finger-
If you are so sure about it, please provide some evidence in a new bug and stop spamming this one. Thanks.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Dana Goyette (danagoyette) wrote : | #114 |
"new bug"... there's this one I just linked to above!
https:/
And with that, I am done with this thread here.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Henrik Rydberg (rydberg) wrote : | #115 |
For maverick users: the attached dkms package should provide multitouch support for a family of synaptics touchpads. Install and reboot. Please report both success and failure here. Thanks!
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Henrik Rydberg (rydberg) wrote : | #116 |
Changed in utouch: | |
status: | New → In Progress |
assignee: | nobody → Henrik Rydberg (rydberg) |
importance: | Undecided → High |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Brad Greco (grecobrad) wrote : | #117 |
I just tried in on a Asus EEE 1005HA, using Maverick x86 (2.6.35-
Two-finger scrolling (both horizontal and vertical) works wonderfully, as does tapping with two fingers. It doesn't seem to detect a 3-finger tap, though. Then again, I don't know if my touchpad has the hardware capabilities of detecting a 3-finger tap.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Gursimran singh (simar) wrote : Re: [Bug 308191] Re: Multitouch support not available for Synaptics touchpads v7.2 | #118 |
@Henrick
Thats a WOW!! thing
I will try it as soon as I get my laptop back from repair..
On Tue, Nov 16, 2010 at 8:25 PM, Brad Greco <email address hidden> wrote:
> I just tried in on a Asus EEE 1005HA, using Maverick x86
> (2.6.35-
>
> Two-finger scrolling (both horizontal and vertical) works wonderfully,
> as does tapping with two fingers. It doesn't seem to detect a 3-finger
> tap, though. Then again, I don't know if my touchpad has the hardware
> capabilities of detecting a 3-finger tap.
>
> --
> Multitouch support not available for Synaptics touchpads v7.2
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in The Linux Kernel: Unknown
> Status in uTouch: In Progress
> Status in XOrg-Driver-
> Status in “xserver-
>
> Bug description:
> I've tried to enable the multi-touch feature on my Samsung NC10 touchpad
> enabled (Synaptics) but I did't find a way for correctly do it working.
> I've started from this how-to
> http://
>
> I've tried to run this:
> synclient -m 100
>
> but it seems that recognize only a single finger.
>
> This touchpad has multi-touch feature since i correctly make it running
> under windows xp, but I like to be able to use it under Linux too.
>
> I'm running last updated Intrepid Ubuntu.
>
> Also affecting last updated Karmic (k)ubuntu.
>
>
>
> To unsubscribe from this bug, go to:
> https:/
>
--
Warm Regards,
Gursimran singh Mohar
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Jim Rorie (jfrorie) wrote : | #119 |
@Henrick
Works like a champ on a Sony VPCS111FM.
You sir, are a god among men. Revel in your awesomeness. :)
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Henrik Rydberg (rydberg) wrote : | #120 |
Glad it works. :-)
Credit for finding out the hardware protocol goes to Takashi Iwai. Chase Douglas put the pieces together and sent the first batch upstream. Chris Bagwell did further improvements and cleanup.
I have uploaded the package to the ppa:utouch-
Thanks!
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Landon Cheek (lcheek) wrote : | #121 |
@Henrik
Works beautifully on my ThinkPad T510. Horizontal/Vertical two-finger scrolling and two-finger tapping all work, and better than the driver on Windows 7 I might add.
Thanks.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
John Baptist (jepst79) wrote : | #122 |
Are there any plans to release this fix as part of a mainline release of Ubuntu, either a future version, or as an update to Lucid or Maverick? Or will I always have to manually use the PPA?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Mariano Draghi (chaghi) wrote : | #123 |
@Henrik
Works perfect on a Dell Studio 1458 (aka Dell Studio 14). Thank you!
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
tob (tobynbertram) wrote : | #124 |
@Henrik
Your dkms package moves the Clickpad button detection to xorg-input. I know that Takashi released a number of patches for xorg-input-
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Henrik Rydberg (rydberg) wrote : | #125 |
@baptist: The process of adding this functionality to future releases of ubuntu and mainline is ongoing, and has been for some time. The utouch package is based on the upcoming mainline solution.
@tob: The kernel will provide MT data, and Clickpads and Macbook integrated trackpads will be served in user space. For an existing X driver that handles MT data to achieve this, see xf86-input-
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Øsse (oystwa) wrote : | #126 |
Thanks so much for this package! This is huge! My report:
Prior to all this I haven't done anything deviating from a default 10.10 installation with anything related to the touchpad. I installed the synaptic-dkms package for the utouch PPA about 14 hours ago.
After reboot I was able to select two-finger scrolling from System -> Preferences -> Mouse -> Touchpad. Brilliant!! As you all probably know this is usually greyed out. Without me doing anything, a two-finger tap translates to a right click. Excellent!
Running "xinput list-props" on my touchpad gives me "Synaptics Capabilities (320): 1, 0, 1, 1, 1" indicating three-finger tap support. This was previously "1, 0, 1, 0, 0" indicating no multi-finger support. As "xev" indicates, a three-finger tap is not recognized. I have also tried changing the action with the "Synaptics Tap Action (307)" property with no effect.
It seems to me the synaptics driver has (in principle) three-finger tap support, since it lists that as a possible capability. By the same token, it seems to me the synaptics driver does not have three-finger swipe/scroll support. Am I correct in this?
Again, thanks!
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Henrik Rydberg (rydberg) wrote : | #127 |
What is missing from all synaptics drivers is support for three individual fingers, i.e., real multitouch support. However, most firmwares are capable of detecting three objects on the pad, so there is still hope that this information can be enabled.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Jose Bernardo (bernardo-bandos) wrote : | #128 |
Thanks! Now when I check my touchpad capabilities with xinput, I get "Synaptics Capabilities (305): 1, 0, 1, 1, 1", and two finger scrolling works.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Joe Barnett (thejoe) wrote : | #129 |
@Henrik;
on an HP Envy15, works in terms of allowing two finger scroll & two-finger-
-right and middle mouse "button" areas of click pad register as left click (same as #582809)
-can't click, hold button down, and drag w/ 2nd finger, as 2nd finger gets treated as two-finger-
can't seem to install both your synaptics-dkms package as well as pauls' "psmouse" dkms package at the same time and get both fixes, but looks like they're actually both providing the same driver, so that seems expected.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Daniel Holm (danielholm) wrote : | #130 |
@Henrik, why do I get this when trying to install?
ERROR: binary package for synaptics: 1.0.0 not found
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
dominic (d-bestler) wrote : | #131 |
successfully installed the package on
Dell Adamo
Ubuntu 32bit
Kernel 2.6.35-22-generic
Many thanks to Henrik!
@Henrik: Is it possible to change the scroll behavior to "roll" instead being "very exact"? The scrolling depends then on the speed of the fingers and does not abruptly stop when removing the fingers from the touchpad - instead its slowly decreases the scroll speed and finally stops (like on every mac or android device).
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Anmar Oueja (anmar) wrote : | #132 |
I can report that it installed and functioning successfully on Lenovo ThinkPad X201 - i5.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Clark (cserolf) wrote : | #133 |
@ Henrik :
Thanks , Installed and functioning on Samsung NC10
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Leo Iannacone (l3on) wrote : | #134 |
Mmm... Package could not be installed in Natty:
$ sudo dpkg -i synaptics-
(Reading database ... 187713 files and directories currently installed.)
Preparing to replace synaptics-dkms 1.0.0 (using synaptics-
Unpacking replacement synaptics-dkms ...
Removing old module source...
Setting up synaptics-dkms (1.0.0) ...
Loading new synaptics-1.0.0 DKMS files...
Loading tarball for module: synaptics / version: 1.0.0
Loading /usr/src/
Creating /var/lib/
DKMS: ldtarball Completed.
Installing prebuilt kernel module binaries (if any)
Building module...
Kernel preparation unnecessary for this kernel. Skipping...
Building module:
cleaning build area....
make KERNELRELEASE=
Error! Bad return status for module build on kernel: 2.6.37-5-generic (i686)
Consult the make.log in the build directory
/var/lib/
0
0
ERROR: binary package for synaptics: 1.0.0 not found
dpkg: error processing synaptics-dkms (--install):
subprocess installed post-installation script returned error exit status 10
Errors were encountered while processing:
synaptics-dkms
#######
And this is the make.log:
DKMS make.log for synaptics-1.0.0 for kernel 2.6.37-5-generic (i686)
Tue Nov 23 13:17:43 CET 2010
make: Entering directory `/usr/src/
CC [M] /var/lib/
In file included from /var/lib/
/var/lib/
include/
/var/lib/
/var/lib/
/var/lib/
/var/lib/
/var/lib/
/var/lib/
/var/lib/
/var/lib/
/var/lib/
make[1]: *** [/var/lib/
make: *** [_module_
make: Leaving directory `/usr/src/
#######
Some info:
lsb_release -cd
Description: Ubuntu natty (development branch)
Codename: natty
uname -a
Linux laptop 2.6.37-5-generic #14-...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Daniel Holm (danielholm) wrote : | #135 |
Could it be because of the 2.6.37-kernel? I got RC2 installed in Maverick and I can't install the package either..
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Øsse (oystwa) wrote : | #136 |
Henrik: I'd really like to be able to use the bleeding edge version of this development. Will the PPA you provided above be regularly updated, or was that a one-off thing and newer version are found elsewhere?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Stephen Sandlin (sandlst) wrote : | #137 |
@Henrik: Success on Dell Studio 1747, thanks much!
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ben (ben-bdlow) wrote : | #138 |
Thinkpad Edge 13 0196CTO w/ Ubuntu 10.10; 'sudo dpkg -i synaptics-
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ricco (eric-escolano) wrote : | #139 |
@Henrik : works on my Dell Studio 1747, thanks !
However ,the two fingers need to be somewhat apart for it to work, while they could be joined when using two-finger emulation. I could get used to it but it feels quite annoying. Anyone else noticed this ?
tags: | added: maverick natty |
description: | updated |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
carmaxx (carmaxx) wrote : | #140 |
It works on my Lenovo U450p on 10.10, thanks a million!
However, the scrolling is somewhat inaccurate while it wasn't so with the latest touchpad driver on Windows or with the script under Ubuntu 10.10 that I used so far. The scrolling sometimes seems to 'jump' back in the opposite direction.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
fiacobelli (francisco-iacobelli) wrote : | #141 |
I have an HP dm1z with an ALPS trackpad that supports multitouch. Running Maverick Meerkat 64bits.
I tried the synaptics-dkms package from post #116, but nothing happened.
xinput -list produces "PS/2 Generic Mouse" for the mouse.
synclient -l produces: "Couldn't find synaptics properties. No synaptics driver loaded?"
Any other solutions?
thanks!
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ricco (eric-escolano) wrote : | #142 |
@fiacobelli : well, you are telling us your touchpad is made by ALPS, this is designed for Synaptics touchpads so it won't work on your ALPS.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ricco (eric-escolano) wrote : | #143 |
I have reverted back to using two-finger emulation, because I just can't get used to two-finger scrolling with the fingers apart, that is really unconvenient (same thing as with Windows and official Synaptics driver).
synclient -m 100 reads as follows :
two fingers apart : 2 fingers registered, width 5
two fingers joining : 1 finger registered, width 15
So I understand why two-finger scrolling won't work with the fingers joining : they register as one finger only.
I just don't feel comfortable with the fingers apart, so I am going back to my emulation script.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
pablomme (pablomme) wrote : | #144 |
@Ricco, carmaxx: you may want to file separate bug reports against the synaptics-dkms package since your issues seem hardware-dependent. In my case (Asus Eee PC 1201N), the dkms driver works better than emulation (no need to keep the fingers apart), and there is no jumpiness when scrolling.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Jim Rorie (jfrorie) wrote : | #145 |
Actually, carmaxx's bug is already reported in the thread. If you look at comment #8, you will see the symptoms described. What he is experiencing is the same bug, except now mutlitouch is working and the jumping is affecting his scrolling. I don't know if these bugs are directly related, but they were reported under this thread...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
pablomme (pablomme) wrote : | #146 |
Reporting bugs in comments is not how the system works. Different bugs must be reported separately.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Jim Rorie (jfrorie) wrote : | #147 |
@pablomme
Comment #8 is describes freedesktop-bugs #21614, which is attached as
THIS bug. (See Affects and assigned to)
That's what I'm saying. Per the launchpad specs, it is THIS bug until
someone changes that.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
pablomme (pablomme) wrote : | #148 |
Sorry, I thought you implied that another bug shouldn't be opened since this one already exists. The freedesktop bug should probably not be linked from this bug (nor should it link back to this bug) since they are not the exact same thing: this one is for multitouch support, the freedesktop one is about an issue with multitouch emulation (which wouldn't be needed if proper multitouch was available, and the bug would thus be fixed by implementing multitouch as requested by this bug, but is still a different issue and should be kept separate).
However note that carmixx's problem is not that in the freedesktop bug; he refers to scroll jumpiness, not cursor jumpiness.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
carmaxx (carmaxx) wrote : | #149 |
@Jim Rorie
Thank you for the hint with post #8. I was able to reproduce the cursor jumpiness both with the script and the newly installed package (when two-finger scrolling is turned off). It turned out that the jumpiness is more extreme with the package, the cursor really makes a huge leap and continues to move even further when I already took my fingers off the touchpad. I really think this might be related to the scrolling jumpiness.
When I activate two-finger scrolling when the package is installed and perform the steps described in post #8, the window would scroll up or down.
I hope this information helps to fix this issue. Please let me know if you need further information.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Gursimran singh (simar) wrote : | #150 |
I installed the patch, but unfortunately the synaptics capabilities are still reported as
Synaptics Capabilities (272): 1, 0, 1, 0, 0
Its for Sony vaio VPCCW16FG laptop with a synaptics touchpad supporting true multitouch in windows.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Aldo (aldojay) wrote : | #151 |
installed on my asus eeepc 1215n 10.10 and it works nicely.
i'm sorry for the three-finger-tap issue, it would be very useful...
thank you
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#224 |
Created attachment 40902
Add JumpyCursorThre
For those touchpads that don't support multi-finger or sending correct finger width, the jumpy cursor problem is still there. One notable example is the ClickPad found on Lenovo S10-3t whose ClickPad suffers from this jumpy cursor problem very severely, because its buttons also have sensible surface thus every time you click a button without lifting another finger from the pad, such as when trying to drag a window or select text, the cursor jumps, and renders the whole touchpad nigh unusable.
(if you are wondering why Synaptics driver doesn't enable ClickPad mode and limit the touch area thus ignore ABS sent from button area, it's because those ClickPads send out BTN_LEFT and BTN_RIGHT just as normal touchpads so they don't trigger the ClickPad mode, which is designed for ClickPads that never send BTN_RIGHT)
Therefore Alberto Milone's JumpyCursorThre
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Andrzej Kłapeć (solidslash) wrote : | #152 |
Still doesn't work in Natty, same output as in #134 comment.
Using 2.6.37-8-generic kernel.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Victor (elektro-style) wrote : | #153 |
Installed on my HP Pavillion dv5. Two-finger taps work, but two-finger scrolling is still grayed-out in mouse preferences.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
gelie (gelie) wrote : | #154 |
Works like a charm on Acer Travelmate 5320 running Maverick, 2.6.35-23-generic kernel (64-bit). Like the 'new' multitouch features. Thanks guys for all the hard work !!
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Anton (avelo) wrote : | #155 |
deb package builds ok with 2.6.35-24 kernel.
Package performs very well on two finger scrolling, with only some problems when the two fingers are very close (Same problem but worse in a Win7 install that I did only for test win. synaptic driver).
Main problem is that it lacks detection of click zone of clickpads, so click+move or right click are impossible.
Also, doesn't build with 2.6.36 or 2.6.37 kernels
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Henrik Rydberg (rydberg) wrote : | #156 |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Henrik Rydberg (rydberg) wrote : | #157 |
Here is a second version, still for maverick (2.6.35), but with both three-finger support and MT support. This package is very close to the final upstream version. Release in natty will follow on positive test results. Enjoy!
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Øsse (oystwa) wrote : | #158 |
Three-finger tap works for me! If I knew what "MT" is I would have testet that as well :P
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Nathan Crawford (njcrawford) wrote : | #159 |
@Henrik: Version 1.1.0 works perfectly on my System76 Lemur2! Thanks much!
One question, is there a way to configure the two and three finger tap actions? I'd like to have two finger tap be middle click and three finger tap be right click.
Again, thanks for your work, this is excellent!
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
pablomme (pablomme) wrote : | #160 |
@Nathan: you can do
xinput set-int-prop "Synaptics Tap Action" 8 "0 0 0 0 1 2 3"
See 'man synaptics' for more info. If you run this from Startup Applications the settings will get overridden by Gnome's (which doesn't appear to have a way to configure this) as it sets itself up. What I have is a script to keep re-applying the settings for 2 minutes:
#!/bin/bash
itry=0 ; while ((itry<24)) ; do itry=$((itry+1))
xinput set-int-prop "Synaptics Tap Action" 8 "0 0 0 0 1 2 3"
sleep 5
done
Still I get some config resets at seemingly random times, so I have the xinput command at hand to re-apply them when needed..
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
hokasch (hokasch) wrote : | #161 |
You should be able to stop Gnome overwriting your settings if you disable its mouse plugin by navigating to "apps/gnome_
@Henrik:
Could you point me to the patches/source combo to compile this on other distros/without dkms?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Anton (avelo) wrote : | #163 |
I don't know if I should report this here or in the clickpad buttons bug
https:/
I've tested the 1.1.0 package, and it compiles Ok and works of for two finger scroll and three finger paste.
But with clickpads, you cannot click+drag, because as they heve a full sensitive surface with no physical separated buttons,
when you press the touchpad with a second finger to make the click, the driver detects two fingers and so, stops the cursor and start scrolling. Same happens if you made a click, and with the finger pressing the surface (in button area) you put another finger to drag the thing below the cursor.
Testing Win7 synaptic driver behaviour, it seems that it takes into account the delay or time between one finger and two finger touchs. i.e.,
If you put two fingers in the touchpad more or less simultaneously, it behaves as two finger detected and start scrolling, but
if you put first one finger, and then the second finger with some delay (~0.5s or more), cursor moves as if only one finger was detected, and so, you can click and then touch and drag. Same if you are moving one finger on the touchpad (moving the cursor) and then touch with other finger to do a click for example, the driver behaves as if only the initial finger was over the touchpad, allowing you to click with the other.
In fact, it seems that Win7 syn. dirver doesn't use the area marked as left buttton for anything, you can click+drag or move+click or scroll with two finger simultaneously in any place. The only diference is when you make the click in right-bottom area designated as right button, that it then behaves as right click.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Gursimran singh (simar) wrote : | #164 |
After I updated my computer, it started working on SONY VAIO VPCCW16FG, two finger scroll as well as two finger right click. Option in the Gnome touchpad tab "Two finger scroll" is not greyed now..
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Bryan Cain (plombo) wrote : | #165 |
I suffered from the issue with the ridiculous cursor jumping on Maverick, and it was fixed with an update to the latest version. However, after restarting a second time (the first time being immediately after the update), the cursor jumping is back.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Henrik Rydberg (rydberg) wrote : | #166 |
@anton: the click pad issue is a separate problem, which is also being worked on.
The attached package is for maverick only, and is similar to the final final upstream version. Should appear in natty in the beginning of the new year. Thanks to everyone reporting!
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Henrik Rydberg (rydberg) wrote : | #167 |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
carmaxx (carmaxx) wrote : | #168 |
The jumpiness is gone for me in the 1.1.1 release, thanks so much!
The only remaining problem is that if the fingers are too close together, instead of scrolling the cursor would move.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Alexemena (alexemena) wrote : | #169 |
Still have the greyed out option for 2 finger scrolling with the 1.1.1 release Lenovo t61p on 10.10 x64 dont really have any idea why.
some hopefully useful information:
xinput list
Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ SynPS/2 Synaptics TouchPad id=10 [slave pointer (2)]
⎜ ↳ TPPS/2 IBM TrackPoint id=12 [slave pointer (2)]
dmesg after installing 1.1.1
input: SynPS/2 Synaptics TouchPad as /devices/
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
mat (sabourin-mathieu) wrote : | #170 |
Success on a asus eeepc 1001px.
Thanks !
mathieu
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
RussianNeuroMancer (russianneuromancer) wrote : | #171 |
With version 1.1.1 on Acer Aspire 8943G now detected three-finger tap. Before with version 1.1.0 it's not wotking.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
D. Wegener (dpwegener) wrote : | #172 |
Multi-finger now detected on Asus 1005PE with the latest patch.
Synaptics Capabilities (292): 1, 0, 1, 1, 1
synclient -m reporting multiple fingers
7.001 3396 3521 84 2 5 0 0 0 0 0 00000000 0 0 0 0 0
8.002 3393 3503 84 2 5 0 0 0 0 0 00000000 0 0 0 0 0
9.002 3404 3565 84 2 5 0 0 0 0 0 00000000 0 0 0 0 0
10.002 3407 2412 87 3 5 0 0 0 0 0 00000000 0 0 0 0 0
11.002 3405 2463 96 3 5 0 0 0 0 0 00000000 0 0 0 0 0
12.002 3404 2489 97 3 5 0 0 0 0 0 00000000 0 0 0 0 0
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Richard Merren (richard-merren) wrote : | #173 |
With the 1.1.1 version installed on my HP Pavilion dv7, the two fingered scroll is now available and works like a charm! The right-button patch from bug #582809 doesn't appear to be compatible, but I haven't tried installing the right button patch first and then this package. I do not have a working right button. Jumpiness appears to be gone as well, though if both palms rub the touchpad while typing it does scroll. The sensitivity seems to be better as well.
I need to play with the settings (xinput list-props 'SynPS/2 Synaptics TouchPad') to see if there is some improvement to be had, but generally this works great.
One other item: I do not have click and drag. I can double-tap (e.g. on a window title bar) and drag it around, but I cannot click the left button with one finger and drag around with the other. I am sure I will find a combo of settings that works well, though.
The missing items are worth it to be able to type without the cursor jumping around! (Though with current settings it still picks up a palm as a click and moves the cursor occasionally.)
To others reading: if you try this it is helpful to post your results, including your laptop model info, so that fellow trackpad sufferers googling for an answer can find this bug.
Great work...thanks, Henrik!
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Richard Merren (richard-merren) wrote : | #174 |
I should add that (without changing any settings) I am getting right click functionality if I double-tap with two fingers.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Richard Merren (richard-merren) wrote : | #175 |
One final note on right-button functionality and then I stop bugging you: The strip across the bottom area of my trackpad is a button. Clicking anywhere on that button (right or left) with one finger is a left-click and clicking anywhere with two fingers is a right click. Theoretically, clicking with three fingers is a middle click, but I haven't tested this.
The upshot is that this patch enabling multitouch has given me full functionality on the trackpad. I will raise a glass to Henrik at my next opportunity.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Henrik Rydberg (rydberg) wrote : | #176 |
Glad it works, and thanks for all the reports! There is a path for clickpads now, although it may be a while before it materializes. It should be a different bug, anyways, as this bug should soon be marked fixed. Happy new year!
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Dana Goyette (danagoyette) wrote : | #177 |
I'd appreciate it if somebody would figure out the initialization
sequence for that "magic" driver mentioned in bug 546697 ... there's
absolutely zero activity there.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
carmaxx (carmaxx) wrote : | #178 |
Sorry to repeat this, but there still seems to be a problem with the two finger scrolling recognition if the fingers are too close together, as reported in posts #155 (https:/
Happy new year everyone!
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
pauljohn32 (pauljohn32) wrote : | #179 |
I have wrestled with this lots, and the problem is that no two people describe it as the same problem.
For some people, the mouse/touchpad driver or module is just wrong. I believe they are the minority.
The majority are people who have working devices, but can't figure how to configure them and the point-and-click tools that keep getting thrown about just make it worse.
If you can make settings work in the terminal with synclient, I wrote down how you can make those fixes permanent.
https:/
For Gnome users, the magic bullet is to stop using the mouse configure menu, turn off gnome-settings-
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Andrzej Kłapeć (solidslash) wrote : | #180 |
Works amazingly well on Maverick! One question though: when is it going to be available on Natty?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Bryce Harrington (bryce) wrote : | #181 |
Looks like Henrik's deb can be considered a solution to this bug. I gather it's a kernel patch so reassigning this bug to the kernel.
Henrik, it'd be great if you could post a link to the sources of the deb, or outline your plan of attack for getting this incorporated into natty. Thanks!
affects: | xserver-xorg-input-synaptics (Ubuntu) → linux (Ubuntu) |
Changed in linux (Ubuntu): | |
status: | Triaged → In Progress |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Henrik Rydberg (rydberg) wrote : | #182 |
The patches are now in 2.6.38 mainline, and will appear in natty when -rc1 has been merged.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Øsse (oystwa) wrote : | #183 |
Any progress on three-finger swipe? :)
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
wankel786 (mahatama) wrote : | #184 |
Can anyone package the new synaptics driver for archlinux? It would be greatly appreciated :)
Changed in linux: | |
status: | Unknown → Confirmed |
Changed in xorg-driver-synaptics: | |
importance: | Medium → Unknown |
status: | Confirmed → In Progress |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Andrzej Kłapeć (solidslash) wrote : | #185 |
I can confirm that two-fingers scroll works out-of-the-box on Natty @ 2.6.38rc2 kernel and xserver-
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
blusa (corsiandr) wrote : | #186 |
As SolidSlash said, two-fingers scroll and tap works on Natty, but we still miss three-fingers support and a better calibration of parameters.
Hope will arrive soon!
Changed in linux: | |
importance: | Unknown → Medium |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ricardo Caldeira (rikycaldeira) wrote : | #187 |
Im using version 1.1.1 on a HP dv3 and so far everything's working pretty good =)
Just one thing bugging me though, when I turn on an external monitor and extend the desktop the pointer speed in one of the axis increases. For example, if I put the 2 monitors side-by-side, horizontal speed will be increased. If the monitors are one in top of the other the vertical speed increases. Really annoying..
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Vincent Ladeuil (vila) wrote : | #188 |
@Ricardo: This bug now has 187 comments, your description is pretty precise and would get more attention as a new bug report (but check duplicates).
Changed in xorg-driver-synaptics: | |
importance: | Unknown → Medium |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Duncan McGreggor (oubiwann) wrote : | #189 |
On Feb 3, 2011, at 11:53 AM, Ricardo Caldeira wrote:
> Im using version 1.1.1 on a HP dv3 and so far everything's working
> pretty good =)
> Just one thing bugging me though, when I turn on an external monitor
> and extend the desktop the pointer speed in one of the axis
> increases. For example, if I put the 2 monitors side-by-side,
> horizontal speed will be increased. If the monitors are one in top
> of the other the vertical speed increases. Really annoying..
*chuckles*
Yeah, we debated this quite a bit (not heatedly... more
philosophically. And physically.)
It's a tricky problem to solve generally, but I'm with you Ricardo...
I believe that this behaviour will be anti-intuitive for most folks.
d
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Andrzej Kłapeć (solidslash) wrote : | #190 |
I do realize that this might not be the best place to ask this but - by default, the top-right corner of a touchpad emulates the middle click. Is there any way to change it to the bottom-left corner?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
hrvooje (hrvooje-gmail) wrote : | #191 |
after
sudo sh -c "echo options psmouse proto=exps > /etc/modprobe.
I have no touchpad tab under system-
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ryan (ryansully) wrote : | #192 |
I can confirm that three-finger clicking (middle click) works for me, using 1.1.1 on HP Envy 14.
Didn't test three-finger swiping however (not sure what function that provides, and don't know what software supports that function).
Changed in linux (Ubuntu): | |
assignee: | nobody → Anudeep Gautamt (jatingautam08) |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Stuart Donald (stuart-donald-family) wrote : | #193 |
Doesn't enable multitouch for Lenovo S12. Ideapad-S12 2.6.37-
Two finger scrolling remains greyed out.
Synaptics Capabilities (282): 1, 0, 1, 0, 0
xinput list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ SynPS/2 Synaptics TouchPad id=12 [slave pointer (2)]
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
kaervos (eudoxus) wrote : | #194 |
@Henrik - Just wanted to note that the 1.1.1 DKMS deb worked great for me on an ASUS g73jh-b1. Thanks!
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Martin Spacek (mspacek) wrote : | #195 |
@ Ricardo and Duncan:
I've opened up a new bug for the non-constant per axis multimonitor pointer speed issue:
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Markus Berndt (markus-berndt) wrote : | #196 |
I just installed the 1.1.1 DKMS deb on my HP DM4 1160us and it works well.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
.aionys. (eyeonus) wrote : | #197 |
Is there a way to configure a zone other than RTCornerButton, RBCornerButton, LTCornerButton, and LBCornerButton?
As in, can I set it up like so:
-------
| button 4 | | button 5 | LTCornerButton = button 4
|------
| |
| |
| |
| |
|------
| button1 | button 3 | button 2 | Rb CornerButton = button 2 (Right Mouse)
-------
If not, I would like to request this feature.
Also, how do I make the CornerButton areas larger? Is that the LeftEdge, etc. values?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
id_ima (id-ima) wrote : | #198 |
Seems to me that synaptics-
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
id_ima (id-ima) wrote : | #199 |
Seems to me that synaptics-
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ofir Klinger (klinger-ofir) wrote : | #200 |
Just installed it. It seems that multi-touch works (as two finger scrolling now works).
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Michael Moore (stuporglue) wrote : | #201 |
I installed it and it works on Ubuntu 10.10 64 bit, on an HP Pavilion dv7.
It doesn't play well with suspend/resume though. When I run it in a terminal, I get the following output when the computer wakes up:
Enable
Disable
X Error of failed request: XI_BadDevice (invalid Device parameter)
Major opcode of failed request: 146 (XInputExtension)
Minor opcode of failed request: 37 (X_ChangeDevice
Device id in failed request: 0x17
Serial number of failed request: 49376
Current serial number in output stream: 49377
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Henrik Rydberg (rydberg) wrote : | #202 |
This bug, as stated in the title, has been fixed upstream (2.6.38), and has been released in natty. There is also a package linked in this bug, confirmed by a large number of users, to work on maverick. Therefore, I am marking this bug as fixed.
Please people, if you still experience problems related to this problem, file a new bug. A bug with 250 comments is bound to include more than one problem report. Thanks.
Changed in utouch: | |
status: | In Progress → Fix Committed |
status: | Fix Committed → Fix Released |
Changed in linux (Ubuntu): | |
status: | In Progress → Fix Released |
affects: | xorg-driver-synaptics → hp-tm2 |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Richard Elkins (texadactyl) wrote : | #203 |
The Synaptics-dkms package improved my touchpad experience on an HP dv3-1075us immensely. Thank you very much.
For extra credit: I'd like to see hardware detection offer this as a suggested "Additional Drivers" in the future.
Changed in linux: | |
status: | Confirmed → Fix Released |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Marco Chiappetta (mardurhack) wrote : | #204 |
I'm sorry to wake this thread up but I'm not able to install the package on my Ubuntu 10.04.2 (just installed). This is the error log of dpkg trying to install synaptics-
And this is the content of the file /var/lib/
My machine is an Eee 1201N (Atom 330, 3GB DDR3, 320GB HD, Nvidia ION).
Multitouch scroll correctly works on Ubuntu 11.04 Natty. Thanks in advance for your help! I would like to keep using a LTS for production purposes and I miss this feature.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Jesús Martínez (pakitochus-gmail) wrote : | #205 |
Same problem as #204, Same error log too.
My machine: Asus K53SV (Core i7, nvidia geforce gt640M, 4GB DDR, 640 GB HD, Synaptics touchpad.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
zhanxw (zhanxw) wrote : | #206 |
Different error message to 204/205, my make.log is:
DKMS make.log for synaptics-1.1.1 for kernel 2.6.38-8-generic (x86_64)
Mon May 30 01:54:09 EDT 2011
make: Entering directory `/usr/src/
CC [M] /var/lib/
/var/lib/
/var/lib/
/var/lib/
/var/lib/
/var/lib/
/var/lib/
make[1]: *** [/var/lib/
make: *** [_module_
make: Leaving directory `/usr/src/
I am using ubuntu 11.04 64-bit, kernel 2.6.38-8.
Hopefully, we will have a newer deb package...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
belltown (sea-av80r) wrote : | #207 |
@Jesús Martínez
@zhanxw
I'm also using Ubuntu 11.04 64-bit, kernel 2.6.38-8 with a Synaptics touchpad.
I was able to get everything working with the released Xorg driver plus patches from Bug #582809 (Comments #144 and #190).
The multi-touch functions, tap-to-drag, and right-click seem to work correctly with the patch from Comment #144. Comment #190 includes instructions for how to install this patch plus a patch for LED tap-to-disable.
I have built a deb file for the Comment #144 patches for Ubuntu 11.04 64-bit. You can download it from http://
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
carlosv (cvedovatti) wrote : | #208 |
belltown you file almost fixed everything for me.
I have a clickpad HP tm2 Ubuntu 11.04 64bit. I installed your file and works everything fine (right button, two finger tap, etc.) except when I do two-finger-scroll. When I scroll slow is ok, but when I scroll fast it changes direction, it scroll up instead of down.
Any ideas for that?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
belltown (sea-av80r) wrote : | #209 |
@carlosv.
I'm not sure why it would do that . The two-finger vertical scroll works for me, although it's a little jumpier and less smooth than when I'm running the same touchpad under Windows 7. How do you have it configured, i.e. what is the output from synclient -l
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
carlosv (cvedovatti) wrote : | #210 |
Hi, the dkms-synaptics worked really well in Ubuntu 10.10, but not in 11.04. And I just upgraded to 11.04, I dont know it affects (I uninstalled dksm-synaptics..). I got this:
LeftEdge = 1751
RightEdge = 5187
TopEdge = 1626
BottomEdge = 4306
FingerLow = 24
FingerHigh = 29
FingerPress = 255
MaxTapTime = 180
MaxTapMove = 222
MaxDoubleTa
SingleTapTi
ClickTime = 100
FastTaps = 0
EmulateMidB
EmulateTwoF
EmulateTwoF
VertScrollDelta = 101
HorizScroll
VertEdgeScroll = 0
HorizEdgeScroll = 0
CornerCoasting = 0
VertTwoFing
HorizTwoFin
MinSpeed = 1
MaxSpeed = 1.75
AccelFactor = 0.0394867
TrackstickSpeed = 40
EdgeMotionMinZ = 29
EdgeMotionMaxZ = 159
EdgeMotionM
EdgeMotionM
EdgeMotionU
TouchpadOff = 1
LockedDrags = 0
LockedDragT
RTCornerButton = 2
RBCornerButton = 3
LTCornerButton = 0
LBCornerButton = 0
TapButton1 = 1
TapButton2 = 3
TapButton3 = 2
ClickFinger1 = 1
ClickFinger2 = 1
ClickFinger3 = 1
CircularScr
CircScrollDelta = 0.1
CircScrollT
CircularPad = 0
PalmDetect = 0
PalmMinWidth = 9
PalmMinZ = 199
CoastingSpeed = 20
CoastingFri
PressureMot
PressureMot
PressureMot
PressureMot
GrabEventDevice = 1
TapAndDragG
AreaLeftEdge = 0
AreaRightEdge = 0
AreaTopEdge = 0
AreaBottomEdge = 0
TouchButtonArea = 20
TouchButton
LEDStatus = 0
LEDDoubleTap = 1
JumpyCursor
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Jesús Martínez (pakitochus-gmail) wrote : | #211 |
@belltown
Hi! I installed the packages you provided, but it didn't worked for me. Moreover, I followed the instructions on Bug #582809 (patched xserver-
I think the problem is that the touchpad isn't recognized by the kernel. When I type: synclient -l, I get:
Couldn't find synaptics properties. No synaptics driver loaded?
Any ideas?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
belltown (sea-av80r) wrote : | #212 |
@Jesús Martínez
Can you post the contents of your /var/log/Xorg.0.log file.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Jesús Martínez (pakitochus-gmail) wrote : | #213 |
@belltown
Thanks for your answer. This is the content of my /var/log/Xorg.0.log file. I guess my touchpad is recognized as a PS/2 Optical Mouse at [ 21.899]
[ 21.103]
X.Org X Server 1.10.1
Release Date: 2011-04-15
[ 21.103] X Protocol Version 11, Revision 0
[ 21.103] Build Operating System: Linux 2.6.24-29-server x86_64 Ubuntu
[ 21.103] Current Operating System: Linux pakitochus-K53SV 2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11 03:31:24 UTC 2011 x86_64
[ 21.103] Kernel command line: BOOT_IMAGE=
[ 21.103] Build Date: 21 May 2011 11:48:41AM
[ 21.103] xorg-server 2:1.10.1-1ubuntu1.1 (For technical support please see http://
[ 21.103] Current version of pixman: 0.20.2
[ 21.103] Before reporting problems, check http://
to make sure that you have the latest version.
[ 21.103] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 21.104] (==) Log file: "/var/log/
[ 21.128] (==) Using system config directory "/usr/share/
[ 21.128] (==) No Layout section. Using the first Screen section.
[ 21.128] (==) No screen section available. Using defaults.
[ 21.128] (**) |-->Screen "Default Screen Section" (0)
[ 21.128] (**) | |-->Monitor "<default monitor>"
[ 21.128] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 21.128] (==) Automatically adding devices
[ 21.128] (==) Automatically enabling devices
[ 21.128] (WW) The directory "/usr/share/
[ 21.128] Entry deleted from font path.
[ 21.128] (WW) The directory "/usr/share/
[ 21.128] Entry deleted from font path.
[ 21.128] (WW) The directory "/usr/share/
[ 21.128] Entry deleted from font path.
[ 21.128] (WW) The directory "/usr/share/
[ 21.128] Entry deleted from font path.
[ 21.128] (WW) The directory "/usr/share/
[ 21.128] Entry deleted from font path.
[ 21.128] (==) FontPath set to:
/usr/share/
/usr/share/
/var/lib/
built-ins
[ 21.128] (==) ModulePath set to "/usr/lib/
[ 21.128] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 21.128] (II) Loader magic: 0x7e0280
[ 21.128] (II) Module ABI versions:
[ 21.128] X.Org ANSI C Emulation: 0.4
[ 21.128] X.Org Video Driver: 10.0
[ 21.128] X.Org XInput driver : 12.3
[ 21.128] X.Org Server Extension : 5.0
[ 21.129] (--) PCI:*(0:0:2:0) 8086:0116:1043:15f2 rev 9, Mem @ 0xdd400000/4194304, 0xb0000000/
[ 21.129] (--) PCI: (0:1:0:0) 10de:0df4:
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
belltown (sea-av80r) wrote : | #214 |
@Jesús Martínez
That would be the problem. You either do not have a Synaptics touchpad, or if you do the kernel is not recognizing it as such. cat /proc/bus/
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Jesús Martínez (pakitochus-gmail) wrote : | #215 |
@belltown
Thank you for the answer. I can't find any information (for a while) about the touchpad present in Asus K35SV. I will start from this point, and try fortune.
Thanks again.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Mahesh Takate (mahesh-takate) wrote : | #216 |
I have Sony Laptop with E Series VPCEB34EN model and my touch pad does not work.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Jonas (jonas-f-henriksen) wrote : | #217 |
Hi,
on ubuntu 11.04 on a dell latitude e6420 i get the following error when trying to install the deb-package:
ERROR: binary package for synaptics: 1.1.1 not found
Any suggestions/
Jonas
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
hrvooje (hrvooje-gmail) wrote : | #218 |
I must say I installed openSUSE 11.4 on my hp 4520s and now synaptics clickpad works perfect. circular scrolling, side scrolling, taping, LED, taping LED ... maybe this info could help ubuntu developers.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ben Hearsum (bhearsum) wrote : | #219 |
Not sure if this is the right place to report this issue or not, but I've noticed that two finger vertical scrolling doesn't work when going slightly or greatly diagonal. Instead of scrolling up or down, it bounces quickly between up and down.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
alberto (alberto-sanchez-upr) wrote : | #220 |
i tried to install the driver but i can't theres this message
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 250374 files and directories currently installed.)
Preparing to replace synaptics-dkms 1.1.1 (using .../synaptics-
-------
Deleting module version: 1.1.1
completely from the DKMS tree.
-------
Done.
Unpacking replacement synaptics-dkms ...
Removing old module source...
Setting up synaptics-dkms (1.1.1) ...
Loading new synaptics-1.1.1 DKMS files...
Loading tarball for module: synaptics / version: 1.1.1
Loading /usr/src/
Creating /var/lib/
DKMS: ldtarball Completed.
Installing prebuilt kernel module binaries (if any)
Building module...
Kernel preparation unnecessary for this kernel. Skipping...
Building module:
cleaning build area....
make KERNELRELEASE=
Error! Bad return status for module build on kernel: 3.0-3-generic (x86_64)
Consult the make.log in the build directory
/var/lib/
0
0
ERROR: binary package for synaptics: 1.1.1 not found
dpkg: error processing synaptics-dkms (--install):
subprocess installed post-installation script returned error exit status 10
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Wizek (123-wizek) wrote : | #221 |
I have the exact same problem as @Alberto and @Jonas on Natty (ASUS K43SV if that matters). What could be the problem?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Alex P (alexander-e-popov) wrote : | #222 |
I get the following error when trying to install the https:/
Error! Bad return status for module build on kernel: 2.6.38-10-generic (x86_64)
Consult the make.log in the build directory
/var/lib/
0
0
ERROR: binary package for synaptics: 1.1.1 not found
dpkg: error processing synaptics-dkms (--install):
subprocess installed post-installation script returned error exit status 10
Errors were encountered while processing:
synaptics-dkms
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
carlosv (cvedovatti) wrote : | #223 |
@outlogic
The synaptics-dkms just works on Ubuntu 10.10. For Ubuntu 11.04 try the solution on the: https:/
Changed in linux (Ubuntu): | |
assignee: | Anudeep Gautamt (jatingautam08) → Jorge Barocio (barocio-05) |
affects: | linux (Ubuntu) → xf86-input-multitouch (Ubuntu) |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#225 |
Still without final solution? I.e. a year of doing nothing in this concern?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#226 |
Thomas, according to two comments up, it looks like only a small corner case is left.
Also, Yan, you should bring up your patch for discussion on xorg-devel.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
sergiomb (sergio-sergiomb) wrote : | #227 |
from
https:/
you got a new patch that alreay queued in main stream kernel :
http://
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Nathan Palmer (dsblue) wrote : | #228 |
Right click and 2-finger-scroll is not working for me on Oneiric. I couldn't get synaptics-
http://
Is this supposed to be working out of the box on Ubuntu 11.10?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
carlosv (cvedovatti) wrote : | #229 |
@Nathan Palmer
Check comment #208 that may help you.
Changed in xf86-input-multitouch (Ubuntu): | |
assignee: | Jorge Barocio (barocio-05) → nobody |
Changed in xf86-input-multitouch (Ubuntu): | |
assignee: | nobody → prannoy (prannoy13in) |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Lord_bow (lordbow) wrote : | #230 |
@Henrik Rydberg
I have the same problem. I can use vertical edge scrolling but not horizontal edge scrolling on my touchpad. The Ubuntu Forum points to your comment on this page for a debian package that'll fix this bug. It explicitly points to your comments #115 and #116. You mention the debian package is attached but there's nothign there and comment #116 is missing (which I'm guessing had the attached files to install).
Can you help me out and repots the bug fixer or can you direct me to where I can get this bug fixed? Thanks.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
|
#231 |
I believe this patch finally fixed this issue:
commit c546779b32d8be2
Author: Chase Douglas <email address hidden>
Date: Thu Feb 9 16:56:29 2012 -0800
Ignore motion during touch count changes on semi-mt devices
Changed in hp-tm2: | |
status: | In Progress → Fix Released |
Changed in baltix: | |
status: | New → Fix Released |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
dindongpas Yu (pkpd168) wrote : | #232 |
Great fixes! It works perfectly wiht my Acer Aspire v3 471G.
Changed in baltix: | |
importance: | Undecided → Medium |
assignee: | nobody → Mantas Kriaučiūnas (mantas) |
status: | Fix Released → Fix Committed |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Stephen Phillips (stephen-kent-phillips) wrote : | #233 |
I just installed Ubuntu 12.10, and I still had trouble with my touchpad. Is this the right place to comment?
I finally found the solution on Ask Ubuntu: http://
That works for me, but is it possible to get that built into the driver. Is this part of the same issue, or should I open a new bug request, or is this the wrong place?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Junior Rimac (junior-rimac) wrote : | #234 |
Solution posted on comments #115 and #116 worked like charm!!!
Linux Distribution: Ubuntu 12.04
Laptop HP ProBook 6460b
Thank you so much.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Timothy Magee (timothy-d-magee) wrote : | #235 |
I have this issue in 12.04 with an HP Pavilion dv6 laptop and SynPS/2 Synaptics touchpad. Judging by the posts above, the synaptics-dkms fix is specific to 10.10. Is that correct? If I try to install it, I get the error described in comments 130, 134, 152, 204, 205, ... I suspect we were all trying to use a fix that isn't compatible with the distro we are using. Is there any solution available for newer releases? It looks like two others have the same problem in 12.04 here:
http://
Changed in xf86-input-multitouch (Ubuntu): | |
assignee: | prannoy (prannoy13in) → monomoy (zhaomozm) |
Changed in xf86-input-multitouch (Ubuntu): | |
assignee: | monomoy (zhaomozm) → Marc Ros (marclouieros) |
Changed in xf86-input-multitouch (Ubuntu): | |
assignee: | Marc Ros (marclouieros) → Daniel Joo Sung Yi (jskorea9997) |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Josh Ventura (joshv10) wrote : | #236 |
Three-finger clicking is very much broken for me (behaves as behaves as either one-finger or two-finger click, depending on how far apart my fingers are), on my System76 Bonobo laptop.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
penalvch (penalvch) wrote : | #237 |
Josh Ventura, thank you for your comment. As this bug report is marked Fix Released, it is not covering your problem. If you want your bug fixed in Ubuntu, please feel free to file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux
For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https:/
Ubuntu Kernel Team: https:/
Ubuntu Community: https:/
When opening up the new report, please feel free to subscribe me to it.
Thank you for your understanding.
Helpful bug reporting tips:
https:/
I also ask you to solve this problem.
I'm using Jaunty (2.6.28-10-generic) and the synaptics driver detects only a single finger. Tried with:
# synclient -m 100