[Jaunty] Upgrade 8.10->9.04: Double click works in xterm but not firefox or gtk application

[Craig Harding]

Binary package hint: xfree86-driver-synaptics

Since upgrading from 8.10 I've had a few issues with the synaptics touchpad.

I added SHMConfig support using this method (https://help.ubuntu.com/community/SynapticsTouchpad#Enabling%20SHMConfig).

Since then I've been trying for over a day to adjust my touchpad settings using synclient from the command line. Once thing I have noticed is that double clicking a word within xterm works ok but doing the same action in pidgin or firefox does not work. If I triple click a word, it finally highlights the word but then clicks off the word (as it should).

If I try to double click on a word in firefox or pidgin, I cannot highlight that word.

I have used the ubuntu-bug report tool so extra information should be attached.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
Package: xserver-xorg-input-synaptics 0.99.3-2ubuntu4
ProcEnviron:
 PATH=(custom, user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcVersion: Linux version 2.6.28-15-generic (buildd@palmer) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #49-Ubuntu SMP Tue Aug 18 18:40:08 UTC 2009
SourcePackage: xfree86-driver-synaptics
Uname: Linux 2.6.28-15-generic i686

[Gursimran singh (simar)]

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. If you could test the current Ubuntu stable version, this would help us a lot. If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect <bug #>, and any other logs that are relevant for this particular issue.

[bugbot (bugbot)]

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.