Bug 584833 - Input problems on Thinkpad T42
Input problems on Thinkpad T42
Status: CLOSED CURRENTRELEASE
Product: Fedora
Classification: Fedora
Component: xorg-x11-server (Show other bugs)
14
All Linux
low Severity medium
: ---
: ---
Assigned To: X/OpenGL Maintenance List
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-04-22 10:33 EDT by Owen Taylor
Modified: 2010-11-24 16:43 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-11-24 16:43:12 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Owen Taylor 2010-04-22 10:33:27 EDT
With the upgrade from 1.8.0-6 to 1.8.0-7, I suddenly started having my cursor jump around when trying to navigate with the Trackpoint on my T42. This made the desktop unusable. Downgrading made the problem go away. 

My guess was that the problem was that some sort of suppression of events from the trackpad got lost, so the events were coming from me brushing against the trackpad or from dirt on the trackpad, but I didn't investigate long enough to conclusively say that was the probpem.
Comment 1 Michal Schmidt 2010-04-22 10:43:24 EDT
Do you use compiz? Does it work better if you disable it?
Comment 2 Owen Taylor 2010-04-22 10:52:29 EDT
This was with normal metacity, both in gdm and logged into the session. 

(I'd have trouble figuring out how compiz could cause something like this - compiz doesn't have any say in where the mouse cursor appears.)
Comment 3 Michal Schmidt 2010-04-22 10:54:09 EDT
I was thinking that compiz could somehow cause a very slow refresh of the screen which might seem like the cursor was jumping. But nevermind.
Comment 4 Rob Whalley 2010-04-22 13:28:37 EDT
Same problem on Samsung NC10 netbook. Check out: https://admin.fedoraproject.org/updates/xorg-x11-drv-synaptics-1.2.2-3.fc13?_csrf_token=e2e11a7e9fadfa0f43a56541a7d69446b5e2159c - was pushed to stable yesterday but looks like it hasn't hit the mirror I'm using yet. 

The following should serve as a workaround for now:
yum localinstall http://kojipkgs.fedoraproject.org/pack/xorg-x11-drv-synaptics/1.2.2/3.fc13/i686/xorg-x11-drv-synaptics-1.2.2-3.fc13.i686.rpm --nogpgcheck

...solved the mouse cursor jumping issue for me.

I'm guessing that the issue is caused by the X server using /etc/xorg.conf.d instead of /etc/X11/xorg.conf.d to store the configuration files - see bug 582468:
https://bugzilla.redhat.com/show_bug.cgi?id=582468
Comment 5 Adel Gadllah 2010-04-23 16:33:01 EDT
(In reply to comment #4)
> Same problem on Samsung NC10 netbook. Check out:
> https://admin.fedoraproject.org/updates/xorg-x11-drv-synaptics-1.2.2-3.fc13?_csrf_token=e2e11a7e9fadfa0f43a56541a7d69446b5e2159c
> - was pushed to stable yesterday but looks like it hasn't hit the mirror I'm
> using yet. 
> 
> The following should serve as a workaround for now:
> yum localinstall
> http://kojipkgs.fedoraproject.org/pack/xorg-x11-drv-synaptics/1.2.2/3.fc13/i686/xorg-x11-drv-synaptics-1.2.2-3.fc13.i686.rpm
> --nogpgcheck
> 
> ...solved the mouse cursor jumping issue for me.
> 
> I'm guessing that the issue is caused by the X server using /etc/xorg.conf.d
> instead of /etc/X11/xorg.conf.d to store the configuration files - see bug
> 582468:
> https://bugzilla.redhat.com/show_bug.cgi?id=582468    

Yeah, the result was that evdev was driving the touchpads which well ... it can't do very good ;)

The updated xorg-x11-drv-synaptics indeed fixes it.
Comment 6 Bug Zapper 2010-07-30 07:26:26 EDT
This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle.
Changing version to '14'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 7 Magnus Glantz 2010-11-24 16:43:12 EST
House-keeping. 

xorg-x11-drv-synaptics-1.3.0-1 in current, consensus seems to be that this is a fixed issue. If that is not the case, please feel free to re-open the bug. Thank you.

Now closing.

Note You need to log in before you can comment on or make changes to this bug.