Touchpad too much sensitive after upgrading from Jaunty to Karmic

Bug #442629 reported by Ricardo Pérez López
44
This bug affects 8 people
Affects Status Importance Assigned to Milestone
xserver-xorg-input-synaptics (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: xserver-xorg-input-synaptics

After upgrading my LG E500 laptop from Jaunty to Karmic, the touchpad is now too much sensitive. It's almost unusable now.

When I put my finger firmly on the touchpad, without moving it, the mouse cursor "shakes" and "trembles" erratically. I'm unable to click on any window border or corner using the touchpad due to this erratic movement. The mouse cursor should not move if I don't move my finger on the touchpad (like before, with Jaunty).

The touchpad sensitivity is so high that it detects my finger even before touching the touchpad, when I put the finger very close to it but without touching it.

Reverting to the Jaunty version of xserver-xorg-input-synpatics seems to fix the issue.

Tags: jaunty karmic
Bryce Harrington (bryce)
tags: added: karmic
tags: added: jaunty
Revision history for this message
Piotr Kęplicz (keplicz) wrote :

Same here on a Compaq Evo N410c with Synaptics Touchpad, model: 1, fw: 5.6, id: 0x165eb1, caps: 0x804713/0x0.

Revision history for this message
Mark W. Tomlinson (mark-tomlinson) wrote :

After a clean install of 9.10 64-bit on my Toshiba Satellite A505-S6960 I've encountered what seems to be the same touchpad problem. Moving or even just hovering a finger over certain parts of the touchpad (approx. the right 1/3, not including edge) causes the cursor to go nuts. It flies all over the screen and I never know where it's gonna wind up.

I've adjusted the mouse/touchpad sensitivity as low as it will go with no change (other than to make other parts of the touchpad unusable). Also, it works correctly in Windows 7, so I don't think it's a hardware issue.

Please let me know know what other information I can provide.

Revision history for this message
molecule-eye (niburu1) wrote :

I've also noticed increased touchpad sensitivity after a clean install of Karmic over previous releases. I'm using a Gateway NX100X. The cursor doesn't go crazy but sensitivity is noticeably higher, even when set to its lowest setting.

Revision history for this message
Andrew Levey (ag-levey) wrote :

Same Problem ?

Advent 5421 laptop with clean install of Ubuntu Karmic 9.10

The touchpad is very sensitive and with tapping enabled will select any icon that is passed over without tapping.
I created the /etc/hal/fdi/policy/shmconfig.fdi
and entered the contents as listed.
I then installed gsynaptics package.. Attempts to reduces sensitivity with gsynaptics fail. Sensitivity resets itself to anywhere between about 30% to 100% sensitivity. If setting at 30% 'sticks' which it does sometimes, it's still way too sensitive and tapping unusable. Scrolling settings don't seem to work but acceleration pointer speed does.
I have tapping disabled currently.

Revision history for this message
Andrew Levey (ag-levey) wrote :
Revision history for this message
Andrew Levey (ag-levey) wrote :
Revision history for this message
Andrew Levey (ag-levey) wrote :
Revision history for this message
Andrew Levey (ag-levey) wrote :
Revision history for this message
Andrew Levey (ag-levey) wrote :
Revision history for this message
Andrew Levey (ag-levey) wrote :
Revision history for this message
Ahmed Shams (ashams) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner.
There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test the current Ubuntu development version (10.10). If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running <apport-collect 442629> , and any other logs that are relevant for this particular issue.

Gursimran singh (simar)
Changed in xserver-xorg-input-synaptics (Ubuntu):
importance: Undecided → Low
Ahmed Shams (ashams)
Changed in xserver-xorg-input-synaptics (Ubuntu):
status: New → Incomplete
Revision history for this message
Piotr Kęplicz (keplicz) wrote :

Still an issue (upgraded to 10.10 development version today).

Revision history for this message
Bryce Harrington (bryce) wrote :

@keplicz - thanks for providing that info, but we would like to see it from the original reporter. We may want to send this bug report upstream, but upstream has a hard and fast rule that logs from someone other than the original reporter are not acceptable. The reason for that is that quite often with X.org bug reports, two people may *think* they have the same issue based on commonality of symptoms and/or hardware, but in truth they have separate issues and mixing the report and the files can cause the developers some confusion.

If this bug report seems not to be getting attention, I would encourage you to file a new bug report with this data, and simply reference this bug report in your bug description.

Changed in xserver-xorg-input-synaptics (Ubuntu):
status: Incomplete → New
status: New → Incomplete
Revision history for this message
Mark (m-shanley) wrote :

Bryce,
This is the problem. Many people report this bug. You give this garbage answer that you want to hear from the original reporter or you will do nothing as evident from your posts. Really, does it matter if it is the original poster or the many more that report this same bug. Maybe the original poster gave up because you are giving the same answer that Microsoft would give. Fine you guys are busy and everyone can appreciate that fact. Hell maybe you just volunteer your time and don't even get paid and if so then thank you. But please stop giving these types of answer because then even any time you may volunteer is a waste of everyone's time including yours.

And yes I am having this issue also on a Dell XPS M1710 running Linux xps-lnx 2.6.32-24-generic #42-Ubuntu SMP Fri Aug 20 14:24:04 UTC 2010 i686 GNU/Linux

I am also having the same issue on another Dell E6500 running Ubuntu same as above but the 64 bit version.

Revision history for this message
Ahmed Shams (ashams) wrote :

@Mark
Thank you for taking time to report and comment on this bug. To maintain a respectful atmosphere, please follow the code of conduct - <http://www.ubuntu.com/community/conduct/> From which I quote:
"
      '''Be respectful.''' The Ubuntu community and its members treat
      one another with respect. Everyone can make a valuable
      contribution to Ubuntu. We may not always agree, but
      disagreement is no excuse for poor behaviour and poor
      manners. We might all experience some frustration now and then,
      but we cannot allow that frustration to turn into a personal
      attack. It's important to remember that a community where people
      feel uncomfortable or threatened is not a productive one. We
      expect members of the Ubuntu community to be respectful when
      dealing with other contributors as well as with people outside
      the Ubuntu project and with users of Ubuntu.

      '''When you disagree,''' consult others. Disagreements, both
      political and technical, happen all the time and the Ubuntu
      community is no exception. The important goal is not to avoid
      disagreements or differing views but to resolve them
      constructively. You should turn to the community and to the
      community process to seek advice and to resolve
      disagreements. We have the Technical Board and the Community
      Council, both of which will help to decide the right course for
      Ubuntu. There are also several Project Teams and Team Leaders,
      who may be able to help you figure out which direction will be
      most acceptable. If you really want to go a different way, then
      we encourage you to make a derivative distribution or
      alternative set of packages available using the Ubuntu Package
      Management framework, so that the community can try out your
      changes and ideas for itself and contribute to the discussion.
"
End of Quotation.

If you feel unsatisfied with the measures taken to handle this bug, Please File another one describing your issue, complete it as much as you can and thus all same bugs will be considered duplicates of the complete one and even in case that you suffer a different bug, in cause or in symptoms, you wont need to waste more time here.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for xserver-xorg-input-synaptics (Ubuntu) because there has been no activity for 60 days.]

Changed in xserver-xorg-input-synaptics (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Piotr Kęplicz (keplicz) wrote :

Expired? Maybe. Fixed? Not at all.

Changed in xserver-xorg-input-synaptics (Ubuntu):
status: Expired → Confirmed
Revision history for this message
Ahmed Shams (ashams) wrote :

@Piotr Kęplicz, thank you for helping triaging this bug ;) but in fact it doesn't have enough info to get confirmed.
If it makes you nervous, believe me it will be much easier to us all if you reported your own bug.
thnx

Changed in xserver-xorg-input-synaptics (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
bugbot (bugbot) wrote :

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

Gursimran singh (simar)
Changed in xserver-xorg-input-synaptics (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Thomas Hernandez (tjhernandez) wrote :

I see the problem too. Wonderful OS, touchy touchpad (pardon the pun). SynPS/2 Synaptics Touchpad on an HP Pavillion dv2000. Running 10.10 with all system updates. I'll enter a new bug once I learn my way around.

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.