Red Hat Bugzilla – Bug 131250
Touchpad acts weirdly on first use
Last modified: 2015-01-04 17:09:20 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2)
Description of problem:
My laptop is a Fujitsu/Siemens Lifebook S6210, with an integrated
When I first use my touchpad, it acts very strangely: the mouse cursor
moves from one place to another very quickly, clicks are performed on
their own, etc...
After a little while, teh touchpad goes back to normal behaviour, and
stays like that until the next reboot.
It feels like the touchpad needs to be used for a little while for it
to calibrate or something...
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Start my laptop
2.Use the touchpad for the first time since boot
3.The mouse cursor moves erratically, and clicks randomly...
4.Wait a little
5.All is back to normal, until next boot
Created attachment 103249 [details]
Created attachment 103250 [details]
The output os /sbin/lspci
Here's the output of /sbin/lspci
You're using the standard mouse driver with IMPS/2 protocol on a
Synaptics touchpad? If so, why aren't you using the "synaptics"
driver? Just curious.
Well, I didn't modify /etc/X11/xorg.conf after system-config-display
That said, I also have an external USB wheel-mouse (which works very
well, from the beginning). Maybe that's why there is:
Option "Protocol" "IMPS/2"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "yes"
Sounds to me like the device is configured to use the wrong protocol.
We ship the "synaptics" driver for synaptics touchpads. If you've
got a synaptics touch pad and our config tool isn't selecting that
driver, it's probably a tool misconfiguration. I'll reassign
to the config tool for investigation.
Can you give me the output of cat /proc/bus/input/devices so I can
seeif this is a synaptics or ALPS touchpad.
Here you are:
[julien@julien ~]$ cat /proc/bus/input/devices
I: Bus=0011 Vendor=0002 Product=0001 Version=0000
N: Name="PS/2 Generic Mouse"
H: Handlers=mouse0 event0
B: KEY=70000 0 0 0 0 0 0 0 0
I: Bus=0011 Vendor=0001 Product=0001 Version=ab54
N: Name="AT Translated Set 2 keyboard"
H: Handlers=kbd event1
B: KEY=4 2000000 3802078 f840d001 f2ffffdf ffefffff ffffffff fffffffe
I: Bus=0003 Vendor=046d Product=c00f Version=1110
N: Name="Logitech USB-PS/2 Optical Mouse"
H: Handlers=mouse1 event2
B: KEY=70000 0 0 0 0 0 0 0 0
B: ABS=100 0
OK this looks like an ALPS not synaptics.
Does your BIOS have an option for Legacy USB Mode in it - if so can
you disable it and see that fixes it for you.
My BIOS has such an option, but disabling it didn't change anything.
Does the erratic movement occur if you start the machine without the
USB mouse plugged in?
Yes, it occurs with or without the mouse plugged on startup.
Sounds like the input layer if it occurs booting just with the touch pad.
According to Ubuntu developers, it seems that this bug would be fixed
by using the Alps driver.
Please see https://bugzilla.ubuntu.com/show_bug.cgi?id=1721 and
A new kernel update has been released (Version: 2.6.18-1.2200.fc5)
based upon a new upstream kernel release.
Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.
This bug has been placed in NEEDINFO state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.
Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.
In the last few updates, some users upgrading from FC4->FC5
have reported that installing a kernel update has left their
systems unbootable. If you have been affected by this problem
please check you only have one version of device-mapper & lvm2
installed. See bug 207474 for further details.
If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.
If this bug has been fixed, but you are now experiencing a different
problem, please file a separate bug for the new problem.
(this is a mass-close to kernel bugs in NEEDINFO state)
As indicated previously there has been no update on the progress of this bug
therefore I am closing it as INSUFFICIENT_DATA. Please re-open if the issue
still occurs for you and I will try to assist in its resolution. Thank you for
taking the time to report the initial bug.
If you believe that this bug was closed in error, please feel free to reopen