scrolling issues using touchpad

[hnrkg]

Binary package hint: xserver-xorg-input-synaptics

1. When I move my finger from the left to right side and (accidentally) touching the scrolling area (on the right side) on the touchpad, the cursor jumps to the far right of the screen. This only happens when I'm moving my finger into the scrolling area, a single (or double) tap in the scrolling area doesn't do anything.

2. This concerns 'continuous scrolling' (I think it's called). First: in 9.10 I hadn't continuous scrolling activated (by default?), in 10.04 it is. But this isn't the issue. To do a continuous scrolling you do a long stroke up or down, and it continuous to scroll up or down. The problem is that it seems to continue to scroll until a tap/click is made. This often results in a in or out zooming of webpages in chrome, e.g.

First I scroll down a page, then I scroll up. And everything is fine. But when I am about to enter a different web address, using CTRL+L, the page zooms in (CTRL+scroll) continuously.

or

in Compiz desktop zoom: I've just scrolled up a page in Chrome and I'm going use the Scale function (Super+Tab). As soon as I'm pressing the Super button, Compiz zooms in.

Now, 1 and 2 are on one hand two different issues but since they both occurred after I upgraded to 10.04 and that I can't figure out how to change these behaviours, I'm filing them as one bug. Maybe there is a way of fixing this with udev rules or something, but I don't know how to do that.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: xserver-xorg-input-synaptics 1.2.2-1ubuntu4
ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
Architecture: i386
Date: Wed Jun 9 11:18:58 2010
DkmsStatus:
 vboxdrv, 3.2.4, 2.6.32-22-generic, i686: installed
 vboxnetflt, 3.2.4, 2.6.32-22-generic, i686: installed
 vboxnetadp, 3.2.4, 2.6.32-22-generic, i686: installed
Lsusb:
 Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LG Electronics F1-22PTV
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: root=UUID=e0f735bb-287d-4413-bfca-9800b20f3a8e ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=en_GB.utf8
 SHELL=/bin/bash
SourcePackage: xserver-xorg-input-synaptics
dmi.bios.date: 09/01/2006
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: A1034IL1 V1.20 09/01/06
dmi.board.name: MS-1034
dmi.board.vendor: MICRO-STAR INT'L CO.,LTD.
dmi.board.version: N/A
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: MICRO-STAR INT'L CO.,LTD.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA1034IL1V1.2009/01/06:bd09/01/2006:svnLGElectronics:pnF1-22PTV:pvrLG-1034:rvnMICRO-STARINT'LCO.,LTD.:rnMS-1034:rvrN/A:cvnMICRO-STARINT'LCO.,LTD.:ct10:cvrN/A:
dmi.product.name: F1-22PTV
dmi.product.version: LG-1034
dmi.sys.vendor: LG Electronics
system:
 distro: Ubuntu
 codename: lucid
 architecture: i686
 kernel: 2.6.32-22-generic

[Kamil (kneczaj-gmail)]

I can confirm that it's regression from 1.1.2. Just installed 1.1.2 and the bug doesn't occur any more.

[Peter Hutterer (peter-hutterer)]

Henrik, Christoph - do you have time to look at this? I'm a bit busy right now.

[Kamil (kneczaj-gmail)]

Instantly isn't appropriate word to describe the problem, so I changed it to suddenly in summary line :P

[Peter Hutterer (peter-hutterer)]

what's the output of synclient -l?
is the output different between 1.1.2 and 1.1.3?

[Kamil (kneczaj-gmail)]

Output is the same for both versions:

Parameter settings:
    LeftEdge = 1700
    RightEdge = 5300
    TopEdge = 1700
    BottomEdge = 4200
    FingerLow = 25
    FingerHigh = 30
    FingerPress = 255
    MaxTapTime = 180
    MaxTapMove = 221
    MaxDoubleTapTime = 180
    SingleTapTimeout = 180
    ClickTime = 100
    FastTaps = 0
    EmulateMidButtonTime = 75
    EmulateTwoFingerMinZ = 280
    EmulateTwoFingerMinW = 7
    VertScrollDelta = 100
    HorizScrollDelta = 100
    VertEdgeScroll = 1
    HorizEdgeScroll = 1
    CornerCoasting = 1
    VertTwoFingerScroll = 1
    HorizTwoFingerScroll = 1
    MinSpeed = 0.3
    MaxSpeed = 1
    AccelFactor = 0.006
    TrackstickSpeed = 40
    EdgeMotionMinZ = 29
    EdgeMotionMaxZ = 159
    EdgeMotionMinSpeed = 1
    EdgeMotionMaxSpeed = 401
    EdgeMotionUseAlways = 0
    UpDownScrolling = 1
    LeftRightScrolling = 1
    UpDownScrollRepeat = 1
    LeftRightScrollRepeat = 1
    ScrollButtonRepeat = 100
    TouchpadOff = 0
    GuestMouseOff = 0
    LockedDrags = 0
    LockedDragTimeout = 5000
    RTCornerButton = 0
    RBCornerButton = 0
    LTCornerButton = 0
    LBCornerButton = 0
    TapButton1 = 1
    TapButton2 = 3
    TapButton3 = 2
    ClickFinger1 = 1
    ClickFinger2 = 1
    ClickFinger3 = 1
    CircularScrolling = 0
    CircScrollDelta = 0.1
    CircScrollTrigger = 0
    CircularPad = 0
    PalmDetect = 0
    PalmMinWidth = 10
    PalmMinZ = 199
    CoastingSpeed = 0.3
    PressureMotionMinZ = 29
    PressureMotionMaxZ = 159
    PressureMotionMinFactor = 1
    PressureMotionMaxFactor = 1
    GrabEventDevice = 1

[Peter Hutterer (peter-hutterer)]

weird. there's only one patch between 1.1.2 and 1.1.3 and that was the removal of the auto-scaling of the right edge (which broke scrolling on every touchpad I tested/emulated). just to be sure, please check that there aren't any distro-specific patches that may affect this.

If you remove the settings for the touchpad (except the edge scrolling on) from the config file do you still see the issue?
please enable shmconfig and run synclient -m 20 while moving the finger across this line. At what coordinates does the cursor jump?
also, I think the log file may help at this point, please attach this as well.

I'm beginning to think that the issue may be coordinates outside the kernel-reported range (which may make this a semi-duplicate of #23102).

[Kamil (kneczaj-gmail)]

I've deleted all options from config file except vertical scrolling and shmconfig. The problem still exist. My /etc/hal/fdi/policy/10osvendor/11-x11-synaptics.fdi now:

<?xml version="1.0" encoding="ISO-8859-1"?>
<deviceinfo version="0.2">
  <device>
    <match key="info.capabilities" contains="input.touchpad">
      <match key="info.product" contains="Synaptics TouchPad">
        <merge key="input.x11_driver" type="string">synaptics</merge>
        <!-- Arbitrary options can be passed to the driver using
             the input.x11_options property since xorg-server-1.5. -->

        <merge key="input.x11_options.VertEdgeScroll" type="string">true</merge>
        <merge key="input.x11_options.VertScrollDelta" type="string">100</merge>
        <merge key="input.x11_options.SHMConfig" type="string">on</merge>

      </match>
      <match key="info.product" contains="AlpsPS/2 ALPS">
        <merge key="input.x11_driver" type="string">synaptics</merge>
      </match>
      <match key="info.product" contains="appletouch">
        <merge key="input.x11_driver" type="string">synaptics</merge>
      </match>
      <match key="info.product" contains="bcm5974">
        <merge key="input.x11_driver" type="string">synaptics</merge>
      </match>
    </match>
  </device>
</deviceinfo>

But I have a problem with running synclient -m 20. It tells me that shmconfig is disabled although it's enabled in the config as you see above.

[Peter Hutterer (peter-hutterer)]

Please get the evtest repo and run evtest-capture against the device. Try to reproduce the bug and then attach the resulting xml file here.

http://people.freedesktop.org/~whot/evtest/

Note that you need to set option GrabEventDevice off, otherwise you won't see events on the device while the driver is running.
<merge key="input.x11_options.GrabEventDevice" type="string">off</merge>

[Kamil (kneczaj-gmail)]

Created an attachment (id=31513)
evtest file

This is the file you asked for.

[Sabras75 (sabras75)]

Confirmed here too.

I first saw it on Zenwalk distribution 6.2 with xorg 1.6.3 (synaptic 1.1.3) and it is still present with Zenwalk 6.4 with xorg 1.7.5 (synaptic 1.2.1).
Also present in other new distribution using xorg 1.7.5 (saw it on crunchbang linux 10 alpha1, unity linux 2010 RC1)

The output of synclient -m 20 shows that x values jumps from ~5900 to 8176 instantly when reaching the right of the touchpad.

Any chances of having this solved in the soon-to-be-released xorg 1.8 ?

thanx,

-S

[Lohmaier (lohmaier)]

same here. Pretty annoying.

1.1.0 shows the same coordinate behaviour (i.e. jumps from a little about 5900-6000 straight to 8176 (stays at that value, even when you move further to the right) but: It didn't move the cursor. No jumping cursor. This is far more usable.

Maybe the touchpad is physically divided into two areas..

Synaptics Touchpad, model: 1, fw: 6.1, id: 0xa3a0b3, caps: 0xa04713/0x10008

[hnrkg (hnrkg)]

Binary package hint: xserver-xorg-input-synaptics

1. When I move my finger from the left to right side and (accidentally) touching the scrolling area (on the right side) on the touchpad, the cursor jumps to the far right of the screen. This only happens when I'm moving my finger into the scrolling area, a single (or double) tap in the scrolling area doesn't do anything.

2. This concerns 'continuous scrolling' (I think it's called). First: in 9.10 I hadn't continuous scrolling activated (by default?), in 10.04 it is. But this isn't the issue. To do a continuous scrolling you do a long stroke up or down, and it continuous to scroll up or down. The problem is that it seems to continue to scroll until a tap/click is made. This often results in a in or out zooming of webpages in chrome, e.g.

First I scroll down a page, then I scroll up. And everything is fine. But when I am about to enter a different web address, using CTRL+L, the page zooms in (CTRL+scroll) continuously.

or

in Compiz desktop zoom: I've just scrolled up a page in Chrome and I'm going use the Scale function (Super+Tab). As soon as I'm pressing the Super button, Compiz zooms in.

Now, 1 and 2 are on one hand two different issues but since they both occurred after I upgraded to 10.04 and that I can't figure out how to change these behaviours, I'm filing them as one bug. Maybe there is a way of fixing this with udev rules or something, but I don't know how to do that.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: xserver-xorg-input-synaptics 1.2.2-1ubuntu4
ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
Architecture: i386
Date: Wed Jun 9 11:18:58 2010
DkmsStatus:
 vboxdrv, 3.2.4, 2.6.32-22-generic, i686: installed
 vboxnetflt, 3.2.4, 2.6.32-22-generic, i686: installed
 vboxnetadp, 3.2.4, 2.6.32-22-generic, i686: installed
Lsusb:
 Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LG Electronics F1-22PTV
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: root=UUID=e0f735bb-287d-4413-bfca-9800b20f3a8e ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=en_GB.utf8
 SHELL=/bin/bash
SourcePackage: xserver-xorg-input-synaptics
dmi.bios.date: 09/01/2006
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: A1034IL1 V1.20 09/01/06
dmi.board.name: MS-1034
dmi.board.vendor: MICRO-STAR INT'L CO.,LTD.
dmi.board.version: N/A
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: MICRO-STAR INT'L CO.,LTD.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA1034IL1V1.2009/01/06:bd09/01/2006:svnLGElectronics:pnF1-22PTV:pvrLG-1034:rvnMICRO-STARINT'LCO.,LTD.:rnMS-1034:rvrN/A:cvnMICRO-STARINT'LCO.,LTD.:ct10:cvrN/A:
dmi.product.name: F1-22PTV
dmi.product.version: LG-1034
dmi.sys.vendor: LG Electronics
system:
 distro: Ubuntu
 codename: ...

[Gursimran singh (simar)]

Hi there, please specify information about the settings you are using in System>Prefrences>pointing devices. This will help us to reproduce the bug.

Then set the status of the bug as New again

[hnrkg (hnrkg)]

I figured I'll give screenshots because I don't really know what you are looking for.

[Gursimran singh (simar)]

hnrkg, your information was helpful a bit but i'm still not able to reproduce the bug. I have the same driver xserver-xorg-inout-synaptics but there are no such unnatural behaviour.

To get more close to your bug hnrkg, I have a few points
1. Are you able to reproduce the bug now. I mean do still have the unusual behaviour.
2. The configration utility you are using is gsynaptics which is rather old now and ready to be removed from the universe. There appears to error in your gsynaptics. I would advice you to get a modern replacement of gsynaptics ie gpointing-device-settings. Try to search 'gsynaptics' in System>Aministration>Synaptics Package Manager . Install the gpointing-device-settings. Your gsynaptics will be automatically removed.

3.After trying this please see if you can reproduce the bug again.
4.Also try to verify if there is a error right in your hardware. hint- use some other os to confim..

Regards

[hnrkg (hnrkg)]

I'll try to answer your questions as concise as possible.

1. Yes. I can reproduce the first and second issue.

2 and 3. However, after I installed gpointing-device-settings my second
issue is not reproducible. In fact, I cannot use 'continuous scrolling' at
all; enabling and disabling does not make a difference. Issue #1 is
unaffected and is still reproducible.

4. Non of the these issues seems to be present in Windows XP (I haven't dig
in to the detailed configuration). Then I started up Xubuntu 10.04 from a
USB stick where I find that the issues are reproducible.

I hope this helps.

[leaf (jsycha)]

I also am experiencing the first problem -- please let me know how and what I can submit to help reconstruct the issue. This is my first time filing bugs on launchpad, so sorry if I miss a beat ahead of time.

Currently, I am using the gpointing-device-settings and altered my settings in /usr/lib/X11/xorg.conf.d/10-synaptics.conf to specify my edge area. The specifics are here: http://swiss.ubuntuforums.org/showthread.php?p=9325430

[Geir Ove Myhr (gomyhr)]

hnrkg, one thing that I think may help the developers to identify the problem is if you could use the program xev to capture the input events that the xserver receives.

For #1, you can run `xev -geometry 900x100-0+120 > ~/xev.txt`. That will give you a 900 px wide and 100 pixel high window at the right hand side of the screen and events are captured as long as the mouse pointer is inside the window. Drag the mouse pointer right inside the window and make it jump all the way to the right, still within the window, by touching the scroll area. Close the window with Alt+F4 (in order to not generate more mouse pointer moving events). Take care to not drag the mouse pointer over the window any more than necessary during this, since it will create noise in the log. Upload xev.txt here.

I don't quite understand #2, but you could probably do something similar. I would anyway recommend focusing on #1 here, since having more than one issue in one bug report is strongly discouraged.

[hnrkg (hnrkg)]

I tried to keep the cursor movements as "clean" possible. I can actually see
"the jump" in xev.txt from about the two last "MotionNotify" events at the
end of the file, but that's about it. Now, let's hope someone else sees more
than I do.

Well, #2 isn't really an issue anymore due to gpointing-device-settings;
let's just leave it and focus on #1 as Gier Ove Myhr proposed. Maybe I'll
file another bug for not being able to "scroll continuously" anymore.

[Geir Ove Myhr (gomyhr)]

Thank you. It is interesting that there are two jumps in the end which may indicate that it is a highly accelerated right movement rather than a move-all-the-way-to-the-right command.

I think we have more or less what we need to send this issue upstream. I read up a little yesterday and came over the program synclient, which should dump the state of the touchpad every X milliseconds. I don't have touchpad, so I can't try it, but you may see if you can get some useful output of that. See `man synclient` for how to use it. What I'm wondering about is whether a touch in the scroll area changes something in the hardware state or whether it is simply the driver that chooses to interpret touch in this area in a special way. This is may be obvious to someone who know more about touchpads and the synaptics driver than me.

If you can get anything useful from synclient, that would be nice. We should forward this upstream soon in any case.

[hnrkg (hnrkg)]

Now I've tried synclient.

First I had to enable SHMConfig, which in 10.04 is done
in /usr/lib/X11/xorg.conf.d/10-synaptics.conf (I learned).

After running synclient -m 1 I moved my finger really slow towards the right
and between time 9.651 (x=5979) and time 9.691 (x=8176) the touchpad made
"the jump". Since this is the coordinates on the touchpad and no
acceleration is noticeable---there is an actual "jump"---the problem seems
to lay in the "transition" from the regular "move-the-cursor" area into the
scrolling area. The questions is why the cursor jumps and not just stops at
x=5979 when my finger enters the scrolling area?

[Gursimran singh (simar)]

qoute
"What I'm wondering about is whether a touch in the scroll area changes something in the hardware state or whether it is simply the driver that chooses to interpret touch in this area in a special way."

Geir, I don't think that the cursor jump is due to something related to hardware in the scroll area as the scroll area is generally implemented in software rather than in hardware. Touchpad generally send only x,y location and the driver has to detect the scroll area themselves and implement the scroll. This seems to be a driver issue.

[Geir Ove Myhr (gomyhr)]

You may be right, simar. I thought the synclient output showed the raw hardware output before the driver processes it, but it may be that the xev output and synclient output shows essentially the same. Anyway, we have enough data to forward this bug to the upstream developers. Would you like to do that, simar? (I see you are new at bug triage) If not, I will do it.

[Geir Ove Myhr (gomyhr)]

This bug has also been reported for Ubuntu:
https://bugs.launchpad.net/xorg-driver-synaptics/+bug/591656

To me it doesn't look like there is anything new there compared to this bug report, but here are links to the output of xev and synclient -m 1 in case it's useful:
http://launchpadlibrarian.net/50400750/xev.txt
http://launchpadlibrarian.net/50431559/synclient.txt

[Geir Ove Myhr (gomyhr)]

I found that this bug had already been reported upstream: https://bugs.freedesktop.org/show_bug.cgi?id=23890. You may register at http://bugs.freedesktop.org and add yourself to the CC-field of that bug report in order to receive updates. It seems they have already figured out what we have figured out here, but I'll link to the attachments here anyway.

The one think I can think about that may accelerate a solution is to git-bisect between 1.1.2 and 1.2.2 to find the commit that introduced this problem. Before that it may be worth reverting the ubuntu-sepcific patches to see if any of those cases the problem.

[Gursimran singh (simar)]

Thanks Geir Ove Myhr for offering me such things to forward a bug upstream but unfortunately I was out of station for a robotics based project of freescale. I would like if you watch me as a new triager and involve me further in doing such things so that I would be able to do it myself and hep in bug triaging.. You can view my email address in my launchpad profile.

Regards

[Mjdiliscia (mjdiliscia)]

Created an attachment (id=38026)
Proposed fix

I have the same problem. So I made a little change to synaptics.c that seems to fix the problem.
Basically, what I do is fix hw->x to a maximum of param->right_edge when calculating delta x (on ComputeDelta(...)). So, it shouldn't mess with other parts of the driver, and anyway hw->x shouldn't be higher than RightEdge at that point of the code.

The modification is working great in my laptop, but i didn't try on other ones. If someone like to try it, I leave you the patch here. If this breaks something else, I would be glad to refix it (if I can, of course).
By the way, if the fix it's too dirty, the problem seems to reside on the fact that some touchpads' hardware 'x' jumps from around 5900 to exactly 8176 and back , close to their right edge. So maybe a better solution is to keep watch of the 8176 value.

[Mstlaurent (mstlaurent)]

(In reply to comment #13)
> Created an attachment (id=38026) [details]
> Proposed fix
>
> I have the same problem. So I made a little change to synaptics.c that seems to
> fix the problem.
> Basically, what I do is fix hw->x to a maximum of param->right_edge when
> calculating delta x (on ComputeDelta(...)). So, it shouldn't mess with other
> parts of the driver, and anyway hw->x shouldn't be higher than RightEdge at
> that point of the code.
>
> The modification is working great in my laptop, but i didn't try on other ones.
> If someone like to try it, I leave you the patch here. If this breaks something
> else, I would be glad to refix it (if I can, of course).
> By the way, if the fix it's too dirty, the problem seems to reside on the fact
> that some touchpads' hardware 'x' jumps from around 5900 to exactly 8176 and
> back , close to their right edge. So maybe a better solution is to keep watch
> of the 8176 value.

I'm using your patch on Debian Squeeze, and it seems to be working perfectly.
Thanks.

[Mk-halogen-dg (mk-halogen-dg)]

Martín J. Di Liscia,

thank you very much!

I had the same problem with my Asus F3JC notebook. This patch really helped me. The only thing is that when my finger slides from the "normal" zone of the touchpad to the scrolling zone, Y coordinate is still working when I'm sliding up or down.

Please let me know how can I help you to make this patch a part of the driver, so many people will be happy with that without manual patching? Should I vote somewhere or stuff like that?

[Mjdiliscia (mjdiliscia)]

I don't know if I'm understanding you well. But if I'm, that's how I felt was natural. I mean, when you slide past the right edge, is like staying on the border of the normal pad area, so it should keep processing the vertical slide.
Anyway, the two posible behaviors could be configured via a new variable handled from synclient. But that should be a design desicion from the mantainers of the driver.

About making this patch permanent part of the driver, sincerely it's my first patch commitment, so I have no idea how to do it. I was hoping that Hutterer saw the patch and do it himself. But yes, I would also like it, I would't want to apply it to every new version by myself.

[Peter Hutterer (peter-hutterer)]

Created an attachment (id=38536)
0001-eventcomm-Clip-x-y-coordinates-into-axis-range-23890.patch

how does this patch work for you? It clips the coordinates into the ones announced by the kernel so that right edge should just be clipped back.

[Mjdiliscia (mjdiliscia)]

That fixes the jumping problem, but it messes two other things. Now my pad doesn't work on the whole area (left edge principally, now have a inactive gap), and the vertical scroll isn't working either (horizontal scroll seems to work fine).
Maybe the kernel announce a smaller area then the real one.

[hnrkg (hnrkg)]

I'd just like to add that this bug is also present in Ubuntu 10.10.

[Peter Hutterer (peter-hutterer)]

Created attachment 43146
touchpad.svg

This plot of the X axis values shows the problem nicely. In the plot, the x axis is just the events in consecutive order, y axis is the actual X value the kernel gave us.

The kernel itself claims that the max value is 5472. You can see that many events go above this value (up to 5976). Then there are a few outliers at 8176 which I suspect is the scroll bar. So the clipping patch makes you lose all these outliers plus all data that goes above the announced maximum.

[bugbot (bugbot)]

Hey Henrik,

Thanks for testing maverick during its development period. Unfortunately it looks like this bug report didn't get attention during the maverick development period. But I see there's not been more comments on the bug since the release, which makes me wonder if this is still an issue for you?

If you've not seen this issue since maverick's release yourself, it may have been solved by kernel or X or other updates that occurred late in the release; if so, would you mind please closing the bug for us? Go to the URL mentioned in this bug report, click the yellow icon(s) in the status column and set to 'Fix Released'.

If you no longer have the hardware needed to reproduce the problem, or otherwise feel the bug no longer needs tracked in Launchpad, you can set the status to 'Invalid'.

If you are the original reporter and still have this issue, just reply to this email saying so. (Or set the bug status to Confirmed.) If you are able to re-test this against 11.04 Natty Narwhal (our current development focus) and find the issue still affects Natty, please also run 'apport-collect <bug-number>' while running natty, which will add fresh logs and debug data, and flag it for the Ubuntu-X development team to look at.

[Mantas (kaipgis)]

First problem still exists. I still have this problem in my asus s96j.

[hnrkg (hnrkg)]

Problem 1 is still present i Maverick.

2011/2/19 settle <email address hidden>:
> First problem still exists. I still have this problem in my asus s96j.
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/591656
>
> Title:
>  scrolling issues using touchpad
>
> Status in XOrg-Driver-Synaptics - synaptics driver for XOrg:
>  Confirmed
> Status in “xserver-xorg-input-synaptics” package in Ubuntu:
>  Incomplete
>
> Bug description:
>  Binary package hint: xserver-xorg-input-synaptics
>
>  1. When I move my finger from the left to right side and
>  (accidentally) touching the scrolling area (on the right side) on the
>  touchpad, the cursor jumps to the far right of the screen. This only
>  happens when I'm moving my finger into the scrolling area, a single
>  (or double) tap in the scrolling area doesn't do anything.
>
>  2. This concerns 'continuous scrolling' (I think it's called). First:
>  in 9.10 I hadn't continuous scrolling activated (by default?), in
>  10.04 it is. But this isn't the issue. To do a continuous scrolling
>  you do a long stroke up or down, and it continuous to scroll up or
>  down. The problem is that it seems to continue to scroll until a
>  tap/click is made. This often results in a in or out zooming of
>  webpages in chrome, e.g.
>
>  First I scroll down a page, then I scroll up. And everything is fine.
>  But when I am about to enter a different web address, using CTRL+L,
>  the page zooms in (CTRL+scroll) continuously.
>
>  or
>
>  in Compiz desktop zoom: I've just scrolled up a page in Chrome and I'm
>  going use the Scale function (Super+Tab). As soon as I'm pressing the
>  Super button, Compiz zooms in.
>
>  Now, 1 and 2 are on one hand two different issues but since they both
>  occurred after I upgraded to 10.04 and that I can't figure out how to
>  change these behaviours, I'm filing them as one bug. Maybe there is a
>  way of fixing this with udev rules or something, but I don't know how
>  to do that.
>
>  ProblemType: Bug
>  DistroRelease: Ubuntu 10.04
>  Package: xserver-xorg-input-synaptics 1.2.2-1ubuntu4
>  ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
>  Uname: Linux 2.6.32-22-generic i686
>  Architecture: i386
>  Date: Wed Jun  9 11:18:58 2010
>  DkmsStatus:
>   vboxdrv, 3.2.4, 2.6.32-22-generic, i686: installed
>   vboxnetflt, 3.2.4, 2.6.32-22-generic, i686: installed
>   vboxnetadp, 3.2.4, 2.6.32-22-generic, i686: installed
>  Lsusb:
>   Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>  MachineType: LG Electronics F1-22PTV
>  PccardctlIdent:
>   Socket 0:
>     no product info available
>  PccardctlStatus:
>   Socket 0:
>     no card
>  ProcCmdLine: root=UUID=e0f735bb-287d-4413-bfca-9800b20f3a8e ro quiet splash
>  ProcEnviron:
>   PATH=(custom, user)
>   LANG=en_GB.utf8
>   SHELL=/bin/bash
>  SourcePackage: xserver-xorg-...

[nuclear90 (nucleartux)]

Please accept this patch. This is major issue.

[Miceonacid (miceonacid)]

Created attachment 49443
xf86-input-synaptics-1.4.1-8176.patch

I've attached a patch file that work on synaptics 1.4.1. It is modified version of Martin's patch.

[Peter Hutterer (peter-hutterer)]

Please submit a evemu recording of the device. I've converted the evtest-capture file but it's not quite enough.

Specifically, I need:
- the event log of the bug when the cursor jumps (the previous file contained that)
- an event log of scrolling in that scroll area on the right
- an event log of movement in the left edge that wasn't working with my previous patch applied

http://people.freedesktop.org/~whot/evemu/

[penalvch (penalvch)]

hnrkg, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p xserver-xorg-input-synaptics REPLACE-WITH-BUG-NUMBER

Please note, given that the information from the prior release is already available, doing this on a release prior to the development one would not be helpful.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs