synaptics touch pad(laptop) clicks too easily

Bug #47971 reported by Josh on 2006-06-02
118
Affects Status Importance Assigned to Milestone
xorg-driver-synaptics (Ubuntu)
Undecided
Unassigned
Nominated for Hardy by hybox
xserver-xorg-input-synaptics (Ubuntu)
Critical
Unassigned
Nominated for Hardy by hybox

Bug Description

By default in Ubuntu the touchpad always detects taps. In other operating systems tap detection is disabled when users are typing. This is currently achieved using an insecure mechanism - a shared memory region. This shared memory region is disabled under Ubuntu because it is a possible security hole. The driver should be changed to allow tap detection to be controlled via the X protocol, which would allow this to be done securely, and would make it work correctly.

There is a workaround that can be used: setting MaxTapTime 0 in the xorg.conf.

Josh (josh-ground-impact) wrote :

oh yeah this is for dapper drake 6.06.. all up to date

LyleBrown (lylejbrown) wrote :

I can confirm that this happens with my Synaptic Touchpad. Am running an IBM Thinkpad R31 - Pentium 3 1Ghz, 256 Mb memory, also running Intel 810 onboard graphics.

Josh (josh-ground-impact) wrote :

i have a gateway laptop, 1.8ghz amd64 1gb ram

ati radeon expres 200m video

Jimmy the shoe (jdshewey) wrote :

I can confirm this on my HP pavillion ZV6000. To those posting bugs here please remember: there are two kind of touchpad's, the ALPS touchpad and they synaptics touchpad. They both use the synaptics driver. Please make sure you know exactly which one you have. This can vary according to model. For instance, I used to have a ZV5000 but was upgraded due to a warrenty issue. The 5000 used the ALPS touchpad. The 6000 uses synaptic.

Jimmy the shoe (jdshewey) wrote :

Upon a little further research, I also noted that I am haveing trouble with shared memory for the device. In my xorg.conf file I have 'Option SHMConfig" "on"' But running qsynaptic and well as "synclient TapButton1=0" gets the error "Can't access shared memory area. SHMConfig disabled?". Research for a prior issue seemed to indicate that if the shared memory cannot be access then you will not be able to change the mouse settings. Can anyone else confirm problems with their shared memory as well?

Jimmy the shoe (jdshewey) wrote :

In the interim, i have been able to find a work-arround.

"sudo apt-get install xfree86-driver-synaptics"

will install xfree86's driver (and uninstall xorgs)

You will then need to symlink the driver into it's proper location for xorg by typing

"sudo ln -sf /usr/X11R6/lib/modules/input/synaptics_drv.o /usr/lib/xorg/modules/input/synaptics_drv.o"

Now finally a quick re-boot should send you on your way.
(from http://www.ubuntuforums.org/showthread.php?t=157889)

Josh (josh-ground-impact) wrote :

that fixed the problem for me "the shoe" thanks alot!! but its still a bug that needs to be worked out.. if i ever reinstall in the future i dont want to have to do that all the time

Daryl R. (darylr) wrote :

I'm having the same problem with my touchpad, but this did not resolve it. Perhaps it is because I installed xubuntu64? Since there have to be 64bit drivers and all, that would be my guess. Any other ideas? Thanks.

jri (jri) wrote :

I had the same problem on a 64-bit machine with ubuntu, but the solution posted above worked perfectly.

necronudist (metal-lord85) wrote :

i've the same problem with my HP Pavillion zv6000 (AMD64) and the solution above doesn't work. mainly because:

- "sudo apt-get install xfree86-driver-synaptics", it says that I'm trying to install a package (the one for xorgs) who's already installed. on my desktop-i686 distribution the package for xfree exists.

- "sudo ln -sf /usr/X11R6/lib/modules/input/synaptics_drv.o /usr/lib/xorg/modules/input/synaptics_drv.o", I haven't a directory like that, neither in /usr/X11R6/lib/, nor in /usr/X11R6/lib64/ I've a "modules" directory.

I should install the i686 version on my AMD64 laptop, but I think there will be much more problems...

You might try to remove the xorg driver. Also you can download the xfree one
and force install it using dpkg. What distro of linux are you using and are
you sure that you do not have xfree86 installed (instead of x11)?

On 6/14/06, necronudist <email address hidden> wrote:
>
> i've the same problem with my HP Pavillion zv6000 (AMD64) and the
> solution above doesn't work. mainly because:
>
> - "sudo apt-get install xfree86-driver-synaptics", it says that I'm
> trying to install a package (the one for xorgs) who's already installed.
> on my desktop-i686 distribution the package for xfree exists.
>
> - "sudo ln -sf /usr/X11R6/lib/modules/input/synaptics_drv.o
> /usr/lib/xorg/modules/input/synaptics_drv.o", I haven't a directory like
> that, neither in /usr/X11R6/lib/, nor in /usr/X11R6/lib64/ I've a
> "modules" directory.
>
> I should install the i686 version on my AMD64 laptop, but I think there
> will be much more problems...
>
> --
> synaptics touch pad(laptop) clicks when i dont want it to
> https://launchpad.net/bugs/47971
>

--
On 5/17/6, a spammer known as PharmaMaster (PM) attacked Blue Security (BS).

Using a program called Blue Frog, BS created a distributed network of over ½
mil users who would automatically send opt out requests to spammers'
clients. This was so effective that PM declared that BS "found the right
solution to stop spam, and I can't let this continue." PM then DDoSd BS,
endangered the net by hacking a major router on the net's backbone to block
BS' webpage and finally attacked typepad, where BS had just surrendered 30
min earlier. This attack caused about 2000 servers to go down including
typepad and livejournal.While BS gave up because they felt this would
"prevent a full-scale cyber-war that we just don't have the authority to
start" The community disagreed and started a Blue Frog clone called okopipi
which will prevents DDOS attacks by using decentralization.

With your help we can fight back against PM and his spam mafia. Please join
at okopipi.org and help take back our internet.

thanks Jimmy, now it works, but I have another problem (maybe is another bug?): if I leave the finger off the touchpad and then put on again, the arrow "jump" on another point of the window (like if the window was "mapped" on the touchpad :-s )

can you almost tell me if it is another bug and where to find further infos?

Not sure. I've never had that problem before... Sorry.

On 6/14/06, necronudist <email address hidden> wrote:
>
> thanks Jimmy, now it works, but I have another problem (maybe is another
> bug?): if I leave the finger off the touchpad and then put on again, the
> arrow "jump" on another point of the window (like if the window was
> "mapped" on the touchpad :-s )
>
> can you almost tell me if it is another bug and where to find further
> infos?
>
> --
> synaptics touch pad(laptop) clicks when i dont want it to
> https://launchpad.net/bugs/47971
>

--
On 5/17/6, a spammer known as PharmaMaster (PM) attacked Blue Security (BS).

Using a program called Blue Frog, BS created a distributed network of over ½
mil users who would automatically send opt out requests to spammers'
clients. This was so effective that PM declared that BS "found the right
solution to stop spam, and I can't let this continue." PM then DDoSd BS,
endangered the net by hacking a major router on the net's backbone to block
BS' webpage and finally attacked typepad, where BS had just surrendered 30
min earlier. This attack caused about 2000 servers to go down including
typepad and livejournal.While BS gave up because they felt this would
"prevent a full-scale cyber-war that we just don't have the authority to
start" The community disagreed and started a Blue Frog clone called okopipi
which will prevents DDOS attacks by using decentralization.

With your help we can fight back against PM and his spam mafia. Please join
at okopipi.org and help take back our internet.

I am having the same problem, intermittently my pointer will go "crazy" - jerking all over the screen and appearing to have random mouse clicks without me moving or even touching the mouse or touchpad. Open programs get focus, and often taskbar menu commands are randomly activated. This behaviour occurs when I am using the mouse or the touchpad. I followed the instructions to above regarding this issue (Synaptic touchpad) but this did not resolve my problem.

This issue making it exteremly difficult to use Ubuntu... In fact almost imipossible. I am a noob to Linux having used Windows for many years, but am otherwise enjoying my Ubuntu experience.

I am using an Dell Inspiron 3800 with touchpad, with dapper installed, mouse is Logitech PS2. Any help with this would be greatly appreciated. If there is any further information that I could provide to assist with resolution please let me know, I may need detailed instructions (I'm new to Linux :-) ) if debugging info is required.

Thanks!

This thread has degenerated into two seperate issues: 1) Cannot disable the
tap to click "feature" 2) crazy and random mouse. This fix resolves the tap
to click issue. It has had mixed success on the random mouse issue. If you
are sure that your setup works with windows, I would try using a purely
xfree and xorg environment and see if one or the other works better. This
will require using two different live CDs I believe debian has xfree86
instead of xorg, so I recommend you give it a try and see if it works. If it
does not, it is likely a probelem with the configuration of your kernel. You
might try scaling back your mouse module to the most basic mouse by adding
the proper switch to the proper module in the /etc/modules file. Also,
previously ALPS pads were slightly different than synaptics pads. You should
find out which pad you use (which can be a chore) and see if anyone else is
having a problem with it. At one point I had to build a custom configged and
patched kernel to get this feature work because the ALPS pad was not
supported by the kernel at that time. This issue sounds like the mouse is
getting out of sync with the driver. This is a common problem among those
who use KVM switches. Try to also make sure that you are not doing anything
weird with your screen. You may be able to fix the issue by switching to a
terminal (ctrl + alt + f1) and then switching back to the graphical
interface (... + f7).

Sorry I don't have a definite answer for you reguarding this issue.

James

This bug seems to be solved (at least on my laptop) with new xserver-xorg-input-synaptics 0.14.3

Carthik Sharma (carthik) wrote :

Sorry, hardhu, but the xserver-xorg-input-synaptics version you mentioned does not work fine on my AMD64 system that I installed today (Jul 26 2006) - Dapper Final, fully up to date.

hardhu (qzerty) wrote :

In fact it doesn't work now for me too. I don't know why at this point, maybe because of some other updates in dapper to the kernel (I am using 2.6.15-26-amd64-k8) or to xserver-xorg, or to ati drivers for my x700 (I am using the the proprietary one, version 8.26.18).

Travis Watkins (amaranth) wrote :

Add
    Option "MaxTapTime" "0"
to your synaptics section in xorg and it should fix this (it also disables tap-to-click completely).

We know. This is the first step we tried. The lack of effectiveness is noted
in the origional bug report. This fix was developed when adding this didn't
work, but thanks for the suggestion.

On 7/27/06, Travis Watkins <email address hidden> wrote:
>
> Add
> Option "MaxTapTime" "0"
> to your synaptics section in xorg and it should fix this (it also disables
> tap-to-click completely).
>
> --
> synaptics touch pad(laptop) clicks when i dont want it to
> https://launchpad.net/bugs/47971
>

--
On 5/17/6, a spammer known as PharmaMaster (PM) attacked Blue Security (BS).

Using a program called Blue Frog, BS created a distributed network of over ½
mil users who would automatically send opt out requests to spammers'
clients. This was so effective that PM declared that BS "found the right
solution to stop spam, and I can't let this continue." PM then DDoSd BS,
endangered the net by hacking a major router on the net's backbone to block
BS' webpage and finally attacked typepad, where BS had just surrendered 30
min earlier. This attack caused about 2000 servers to go down including
typepad and livejournal.While BS gave up because they felt this would
"prevent a full-scale cyber-war that we just don't have the authority to
start" The community disagreed and started a Blue Frog clone called okopipi
which will prevents DDOS attacks by using decentralization.

With your help we can fight back against PM and his spam mafia. Please join
at okopipi.org and help take back our internet.

I saw this tapping issue after a recent update on an IBM ThinkPad T41 running Dapper. Any fix yet? MaxTapTime was already set previously, and somehow, things broke after we updated. I can say that it did work in kernel revision 2.6.15-25-386, but broke when we upgraded an booted 2.6.15-26-386. However, trying kernel 2.6.15-25-386 from GRUB does not resolve the issue now. It appears that something got really broken between the update a few weeks ago, and the recent update like a week and a half ago. Hrm...

Any ETA on a fix yet? Does anyone even have an idea what happened? Could it be that it got broken in the attempt to fix the "crazy touchpad" symptoms mentioned in June? And that the July fix broke the ability to disable the tapping functionality?

THIS IS NOT AN AMD64 SPECIFIC ISSUE! YOU CANNOT DISABLE THE TOUCHPAD EVEN ON AN IBM THINKPAD (PENTIUM 32-BIT) RUNNING AN i386 KERNEL!!!
--
Kristian Hermansen

dsiddens (angel03) wrote :

This is a "me too" note. I think I can claim to have experienced all the behaviors above at various times. I'm ignorant of the linux command line; just want the pad to work as a full-on synaptics optioned device. System is a hp dv8000, amd turion64, 1meg ram, ubuntu 6.06.

I confirm this also happens in Edgy on a Toshiba Sattelite

I can confirm on emachines laptop running 64 bit dapper on AMD64. Fix with xfree worked perfectly.

Hi Paul,
Can you send me detailed lines as to making the "xfree" fix?

I'm a transplant from MS land and do not know how to get around in Linux
if it doesn't exist on the GUI.

Thank you, Doug

paultbeck wrote:
> I can confirm on emachines laptop running 64 bit dapper on AMD64. Fix
> with xfree worked perfectly.
>
>

Another toshiba A10 satellite here, and i'm getting this bug, since the last upgrade.

The only change seems to be:

xserver-xorg-input-synaptics (0.14.6-0ubuntu3) edgy; urgency=low

  * Add the ugly ALPS hack back

 -- Matthew Garrett <email address hidden> Mon, 7 Aug 2006 22:55:42 +0100

Lakin Wecker (lakin) wrote :

I also have a similar problem on an Acer Ferrari 4005 WLMi.

Alex Muntada (alex.muntada) wrote :

Had no problem with my ALPS touchpad (Sony VAIO) on Dapper, but double-tapping started to behave badly after upgrading to Edgy. It seems that that "ugly APLS hack" could be the cause, isn't it?

AaronPeterson (alpeterson) wrote :

Option "MaxTapTime" "0"

MaxTapTime is the biggest deal here.

This bug needs to stay open until gnome and kde have a control panel module to configure this.

----
Aaron Peterson

Section "InputDevice"
        Identifier "Synaptics Touchpad"
        Driver "synaptics"
        Option "SendCoreEvents" "true"
        Option "Protocol" "PS/2"
        Option "Device" "/dev/psaux"
# Option "Protocol" "auto-dev"
        Option "HorizScrollDelta" "0"
        Option "SHMConfig" "on"
        Option "TappingOff" "1"
        Option "MaxTapTime" "0"

EndSection

AaronPeterson (alpeterson) wrote :

ok, I should have seen that this was another issue, and I know nothing about it.. but it took me a couple of weeks to find the Option "MaxTapTime" "0" way to turn off the dang touch pad.

It's just generally broken, and I was happy to actually stumble across somebody saying similar stuff.

On 9/18/06, AaronPeterson <email address hidden> wrote:
> It's just generally broken, and I was happy to actually stumble across
> somebody saying similar stuff.

Yes, MaxTapTime is very broken and I have seen this bug on more than
one machine now...
--
Kristian Hermansen

The ubuntu driver showed up as 0.14.3 and upstream 0.14.4 had a bunch of fixes for 64 bit issues.

I was having the same problem with random pastes caused by phantom 3rd button presses each time I put my finger on the touchpad (even if I had "disabled" tapping). I have since manually updated to the latest version from the git tree. It's working a lot better now.

I would recommend the synaptics driver is updated to the latest release.

Yeah well... Dapper 6.06.1 LTS... none of the above work for me :| I always get the "SHMConfig disabled?" error, even though it's enabled *and* I've installed the xfree driver :|

Andrew Hunter (rexbron) wrote :

For the "SHMconfig" option in Xorg.conf, you must change it to "on"
 for programs like ksynaptic (and possibly others) to work.

See https://launchpad.net/distros/ubuntu/+source/ksynaptics/+bug/63276 for more info.

Andrew Hunter (rexbron) wrote :

Just a note: I am using the xorg driver, but used ksynaptics to disable touch clicking. Ksynaptics is a nice gui for modifying synaptic options.

otchete (cbpoindexter) wrote :

Um, I know this will sound stupid, but I have no idea what anyone here has said in this post except the problem....

I am having this same problem with my laptops ALPS mouse, but I do not understand any of the solution because I'm not incredible with computer know-how or open source, etc..... I'm sure some people will say, "Well you're in the wrong place-", but this is the only place I've found where people have said they are having the same problem, let alone that there is a solution.

Is there anyway somebody here could "dumb this solution down", step-by-step it, or guide me to some place where I could find an easier or more detailed explaination?

I'm sorry if I'm being a pain, but I would very very much appreciate this.

Thanks.

BobNJ (bob-nj) wrote :

This is merely an 'me too' comment with yet another workaround suggestion, working for me.

My environment:
HP NX6325
Ubuntu 6.0.6 lts
Linux user-laptop 2.6.15-27-amd64-generic #1 SMP PREEMPT Sat Sep 16 01:50:50 UTC 2006 x86_64 GNU/Linux

Symptoms, same as with original poster, touchpad started to misbehave after certain, yet unknown upgrade.

Workaround:
1. Downloaded Synaptics driver package from maintainer's site and recompiled. http://web.telia.com/~u89404340/touchpad/files/

2. The recompile worked fine, but resulted in synaptics_drv.o while xorg server as it is running at my Ubuntu is requiring shared object, synaptics_drv.so

3. Hacked the driver package makefile, to force the xorg recognition, and built the .so driver. Here is my diff to original, quick and dirty, basically forcing the recognition of xorg.

user@user-laptop:~/Desktop/synaptics-0.14.6$ diff makefile.rs Makefile
29d28
< BUILD_MODULAR = y
33d31
< INSTALLED_X = /usr/X11R6
35d32
< INPUT_MODULE_DIR = /usr/lib/xorg/modules/input
40,41c37
< # SDKDIR = $(shell pkg-config xorg-server --variable=sdkdir)
< SDKDIR = /usr/include/xorg
---
> SDKDIR = $(shell pkg-config xorg-server --variable=sdkdir)
user@user-laptop:~/Desktop/synaptics-0.14.6$

4. Copied .so driver over the original, misbehaving one. Restarted.

5. Writing this post, touchpad back to normal. :)

Conclusion: This is yet another workaround, and Ubuntu packagers should provide us with synaptics-0.14.6 XORG driver package, which apparently solved the problem, at least on my setup.

Tks,

Bob

BobNJ (bob-nj) wrote :

Undoing wrong assignment

Changed in xorg-driver-synaptics:
status: Unconfirmed → Rejected
BobNJ (bob-nj) wrote :

And now realizing that this package has already been built, for feisty:
https://launchpad.net/distros/ubuntu/feisty/+package/xserver-xorg-input-synaptics

Learning to use launchpad.net ... I apologize for triple-posting... probably just too excited about working touchpad...

Bob

Francesco Conti (madmoose) wrote :

Edgy + synaptics-0.14.6 XORG driver package

my xorg.conf synaptics section:

Section "InputDevice"
        Identifier "Synaptics Touchpad"
        Driver "synaptics"
        Option "SendCoreEvents" "true"
        Option "Device" "/dev/psaux"
        Option "Protocol" "auto-dev"
        Option "HorizScrollDelta" "0"
        Option "TouchpadOff" "2"
        Option "SHMConfig" "on"
        Option "TapButton1" "0"
        Option "TapButton2" "0"
        Option "TapButton3" "0"
        Option "RTCornerButton" "0"
        Option "RBCornerButton" "0"
        Option "VertScrollDelta" "0"
        Option "MaxTapTime" "0"
        Option "MaxDoubleTapTime" "0"
        Option "MaxTapMove" "0"
EndSection

Well...after every system boot I have to restart X with CTRL-ALT-BKSPC to have tap click finally disabled.

Someone out there knows why? :-)

Thanks
Mad

Adrian (ruewan) wrote :

I have the same problem on my hpzv5000

Caleb (caleb-marcus) wrote :

Same problem here on my Dell Inspiron 5160. Annoying as hell because I'll be typing and suddenly it'll start typing in a different place because the touchpad clicked. This is pretty serious, as far as I know Synaptics makes all of Dell's touchpads... and Dell's pretty popular.

Installed Edgy on an old Compaq 712AU for testing.. yes it is very annoying. It kept on opening Evoloution mail when I tried to tap the pad to open Firefox. And the cursor moves too fast.

James Tait (jamestait) wrote :

I had a similar problem on my Acer Ferrari 4005 WLMi. I added the FingerHigh and FingerLow options to the InputDevice section as follows:

Section "InputDevice"
        Identifier "Synaptics Touchpad"
        Driver "synaptics"
        Option "SendCoreEvents" "true"
        Option "Device" "/dev/psaux"
        Option "Protocol" "auto-dev"
        Option "HorizScrollDelta" "0"
        Option "SHMConfig" "on"
        Option "FingerHigh" "40"
        Option "FingerLow" "20"
EndSection

Francesco Conti (madmoose) wrote :

Hi James,
after adding FingerHigh and FingerLow options, the tap click is automagically disabled after every reboot?

description: updated
James Tait (jamestait) wrote :

Hi Madmoose,

I arrived at those figures by a lot of experimentation and X restarts. It could be that those figures are too high for your particular machine -- try tweaking the FingerHigh value down gradually and hopefully it will eventually work. See man(5) synaptics for more info.

Nick Fishman (bsdlogical) wrote :

It's so good to know that this problem is being exposed. I share Madmoose's problem - I have to restart gdm for the mouse taps to stop working entirely, even when properly configured in xorg.conf.

Karl Hegbloom (karl.hegbloom) wrote :

Re: Pointer going crazy once in a while, or suddenly jumping across the screen.

I had a laptop that did that, and what I discovered is that if I had the Gnome battery meter running, it did that, but when I shut it off, the problem went away. The Gkrellm battery meter did not seem to cause it. It turns out that the Gnome battery meter was calling on the ACPI battery check, via /proc, a lot more often than the Gkrellm one was.

The hypothesis is that the code run by the ACPI BIOS has the interrupt mask on, and it takes too long to return a result to the operating system. Or, perhaps the OS has it set? I think that the pointer jump is caused by missed interrupts or something.

The solution was to not poll the battery state more often than once every minute or so. (And the ultimate solution was to quit trying to use that infernal touchpad by getting a nice optical mouse for the laptop.)

Ketil Malde (ketil-ii) wrote :

While one solution is to disable touchpad clicking altogether, I think configuring the touchpad to require a more decisive tap before sending an event could be a more satisfactory solution for many.

Just pointing out: there is a 'synclient' tool that lets you monitor the touchpad, and tweak settings. IIRC, you need to add

  Option "SHMConfig" "on"

to the Synaptics section in xorg.conf and restart X.

linuxguy123 (linuxguy123) wrote :

+100 from me on this issue !

I've been using an HP laptop with a Synaptics touchpad and Linux for over 2 years now. There has always been a problem getting the touchpad set up right. I DO NOT think editing xorg.conf is the answer. I have friends with similar laptops and one refused to install Linux specifically because of this problem.

In Fedora land there was a Synaptics specific driver floating around that allowed a whole bunch of adjustments for pad properties. I think its high time that a Linux distro started shipping it. These touchpads are very popular and the grief the stock driver causes is major.

Just my $0.02.

George Voiculet (voiculeg) wrote :

I have a Dell Inspiron 1501 running Fedora Core 6.
The following disabled my touchpad.

Add to the xorg.conf file (found in /etc/X11):

          Option "SHMConfig" "on"
          Option "TouchpadOff" "1"

and restart computer (or the X server).
I found this reading all the above postings plus:
man synaptics
and
man synclient

Good Luck!

I think that modifying the touchpad driver to only send tap events if the touchpad is tapped more sharply has led to my problem, where not all taps are recognized.

Se more details here: http://ubuntuforums.org/showthread.php?t=526654

Anthony S (aaaantoine) on 2007-09-05
Changed in xserver-xorg-input-synaptics:
assignee: nobody → pascal-devuyst
Changed in xserver-xorg-input-synaptics:
assignee: pascal-devuyst → nobody
VousDeux (launchpad-blahdot) wrote :

I'm still having problems with this touchpad sensitivity on Gutsy x86_64. My computer is an MSI MS-1719. I have tried every which way that I have found (and I think I have probably found them all) to configure the xorg.conf, but no matter what I do, the end result is the same. If I try to launch ksynaptics, or synclient, I get the warning about shared memory being inaccessible.

There is absolutely no doubt that I have the 'Option "SHMConfig" "on"' setting in the correct section of the xorg.conf, but it just seems like this cannot be read by the process that needs it.

I also tried 'Option "TouchpadOff" "1"', and 'Option "TouchpadOff" "0"', but neither of these actually turned the touch pad off.

I saw above, in the original description, where someone commented that the shared memory was disabled because of security. Could this be preventing this from functioning?

I really have no idea what else to do here, but I can't even type on this darn thing without that touchpad messing me up!

VousDeux (launchpad-blahdot) wrote :

I just wanted to add the attached files. They seem to be showing that the touch pad is not being detected, so the driver is being unloaded.

Mike Dahlgren (dahlgren) wrote :

I think there are more then one issue being discussed in this bug. As for myself this issue was fixed in later beta release of Gutsy.

  Thanks,
       ~ Mike

I've exactly the same problem in my Acer Aspire 5920...

At the countrary all works well in my TravelMate 290 (and not-so-well in another older Aspire I've).

Sterner Regnix (regnix) wrote :

Same problem on a Samsung R70, the MaxTapTime 0 option fixed the tapping issue for me.

Seán T Mac An Oghaim (shanet) wrote :

Same problem on Latitude D620, fixed by above workaround.

VousDeux (launchpad-blahdot) wrote :

Hello again:

As a follow-up, I just wanted to note that I have continued to try every workaround that I have found, but nothing seems to get me past this problem. None of the updates have changed anything either. All I can do is use my hotkeys and disable the touchpad each time I boot the computer. I sure hope someone can fix whatever it is that keeps my touch pad driver from loading when I boot.

Thanks again,

Jerry

P.S. Since I have already attached the necessary files above, I have not included any new files. If I can provide any additional information that would be helpful, I would be happy to do so. Please feel free to contact me if there is anything at all I can do to help further troubleshoot this issue.

Mircea Deaconu (mirceade) wrote :

Hello! First of all let me say I am truly regretting doing this. This is a spam message sent to all critical bug message lists. It's purpose: making this (https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/59695) bug critical too. This is a long standing bug and has a very serious impact on laptop type of hardware. It's priority is set to "wishlist" and I just cannot take this anymore. I DO NOT CARE if my account gets suspended. I am doing what's right for all my friends using Ubuntu on their laptops.

sibidiba (sibidiba) wrote :

If SHMConfig is set to "on", use

$ syndaemon -i 1 -t -d

to start a daemon that disables tapping and scrolling (but not pointer movement) for one second after the last key was pressed.

Claudio Moretti (flyingstar16) wrote :

I used this app (http://packages.ubuntu.com/hardy/gsynaptics) to avoid the problem..
After having manually set "SHMConfig" "true" in my xorg.conf, gsynaptics started and allowed me modifying tapping interval for my Dell Vostro 1500..
I think this is the best workaround we can have..

linuxonbute (normanelliott) wrote :

A simple way to disable the touchpad is to add this line:

rmmod psmouse

to the end of rc.local.

If you do want to enable it to try a new configuration you can comment that line out and reboot.

I have a zepto znote 3215W with an elantech touchpad. The synaptics driver is used to drive it.
It still is super sensitive running Ubuntu 8.04

Otherwise it works as expected. Still useless because of tapping problem.

SHMConfig optin does not work.
MaxTapTime 0 does not work.
I will try the xfree86 driver and see what that does.

linuxonbute (normanelliott) wrote :

apt-get install decided that I already had the latest xorg driver which it said was the regex of the xfree one!!!!!!!!

searched for synaptics_drv.o but could not find it anywhere on my system

linuxonbute:
http://packages.ubuntu.com/search?searchon=contents&keywords=synaptics&mode=filename&suite=hardy&arch=any
finds /usr/lib/xorg/modules/input/synaptics_drv.so from package xserver-xorg-input-synaptics :-)

Marius Gedminas (mgedmin) wrote :

lunuxonbute: I've got an elantech touchpad in my Asus EeePC. The synaptics driver *does not* recognize it (in Hardy), and therefore cannot configure it, instead it is picked up by the generic X mouse driver. Check your /var/log/Xorg.0.log.

Timo Aaltonen (tjaalton) wrote :

Intrepid has support for input properties, which means that you can configure the device during the session without any SHMConfig hacks. Closing as fixed.

Changed in xserver-xorg-input-synaptics:
status: Confirmed → Fix Released
Wladicus (walt-dutchak) wrote :

I am running Kubuntu 8.04 LTS (Hardy Haron) in Wubi mode. None of the solutions ever mentioned for this touchpad problem has been effective in my case. I have tried all the solutions that I could find on several forums. NOTHING! nada!
A challenge to the developers---Let's get this very basic necessity fixed and show that Linux is really in the game with other operating systems. I have spent too long trying to make this work and now I just want to go back to something more comfortable - like Windows. Don't give me a reason to do it!
walt

Wladicus (walt-dutchak) wrote :

*** SOLVED ** HOW TO DISABLE TOUCHPAD IN KUBUNTU ***
sudo rmmod psmouse ( disables the touchpad )
sudo modprobe psmouse ( re-enables the touchpad )
for the original author's explanation, see this link:
http://ubuntuforums.org/showpost.php...9&postcount=13

Harvey Muller (hlmuller) wrote :

Timo,

I'm currently testing Intrepid Beta. The AlpsPS/2 ALPS Glidepoint does NOT trigger the Touchpad tab in Mouse Properties. See Bug #267611.

Since I cannot see what is provided on the Touchpad tab, can you confirm that there is an option which will turn the touchpad off when an external mouse is attached?

The current philosophy is that X is supposed to autodetect all input devices. But past experience has been that I have had to customize the Synaptics section heavily for my touchpad to perform reasonably. If there's anything I can do to improve this as a user, then point me the way.

Currently I have no way of configuring the touchpad other than doing what Ubuntu and the Xmen are trying to prevent, and that is by modifying xorg.conf. The default setup is a PITA, because as others have observed, the cursor jumps in an unpredictable fashion all over the place.

Thanks,

Harvey

I finally met my satisfaction business company: daisyele.com ,
high quality products, heavy discounts, friendly service, fast delivery,
and it is really long-awaited product when I open the package.

Good for you, Jimmy.

On Mon, Jan 3, 2011 at 7:03 PM, Jimmy the shoe <email address hidden> wrote:

> I finally met my satisfaction business company: daisyele.com ,
> high quality products, heavy discounts, friendly service, fast delivery,
> and it is really long-awaited product when I open the package.
>
> --
> You received this bug notification because you are a direct subscriber
> of a duplicate bug (49270).
> https://bugs.launchpad.net/bugs/47971
>
> Title:
> synaptics touch pad(laptop) clicks too easily
>

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments