mouse pointer no longer has 1 pixel precision
Bug #327428 reported by
BotLobsta
This bug affects 6 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xserver-xorg-input-synaptics (Ubuntu) |
Fix Released
|
Low
|
Unassigned |
Bug Description
Binary package hint: xserver-
After upgrading to the latest X server and all of the accompanying packages (version 0.99.3-2ubuntu2 for xserver-
I am running the 2.6.28-6 amd64 kernel on the latest jaunty.
tags: | added: jaunty |
tags: | added: karmic lucid |
Changed in xserver-xorg-input-synaptics (Ubuntu): | |
status: | New → Confirmed |
tags: | added: hardy |
tags: | added: patch |
Changed in xserver-xorg-input-synaptics (Ubuntu): | |
importance: | Undecided → Low |
tags: | added: oneiric |
Changed in xserver-xorg-input-synaptics (Ubuntu): | |
status: | Confirmed → Triaged |
To post a comment you must log in.
I can confirm that this bug is a problem, and only affects Jaunty, not Intrepid. My touchpad is an ALPS type touchpad. In an effort to fix it on my own system, I tried a few things. You can't fix it using xinput, synclient, xset, or other common terminal commands. I also tried altering the relevant .fdi files for the HAL.
I tried using an external mouse, and it worked flawlessly, so it's definitely a problem with the synaptics driver. I tried running Intrepid through LiveUSB on the same system, and the touchpad works flawlessly there.
My laptop, which is being affected by this bug, has a 1440x900 screen. Using "xinput query-state", I was able to confirm that, in Intrepid, the touchpad allows for coordinates from 0,0 to 1439,899. I was also able to confirm that, in Jaunty, it only allows for coordinates up to 1023,767 (representing the bottom-right corner of the screen). This indicates that there is a problem with the resolution that the touchpad is being set up to register.
I also tried copying the relevant .fdi file from the LiveUSB version of Intrepid over to Jaunty - no good. Same problem, the only change was the ID given to the touchpad for xinput purposes. The only other hint is that, in Intrepid, the "max_value" values for the touchpad are set to -1 for both axes, but they're set to 1023 and 767 in Jaunty.
Problem is, for all my searching, I can't find a place, anywhere, to change the "max_value" numbers for each axis of the touchpad, so as a result I can't get the touchpad to correct itself to the appropriate "resolution". I can only think that either there's a mistake making the driver incorrectly detect the resolution, or someone forgot to document an added functionality making the resolution a manual input rather than automatically detected. Other mentions I've seen of this issue around the net (only a few instances) all seem to indicate the "max_value"s are set to 1023 and 767.