Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 533492 - x11-drivers/xf86-input-mtrack-0.3.0 - vertical pointer-tracking off-by-one
Summary: x11-drivers/xf86-input-mtrack-0.3.0 - vertical pointer-tracking off-by-one
Status: RESOLVED UPSTREAM
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Library (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Naohiro Aota
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-12-25 07:45 UTC by Duncan
Modified: 2017-01-26 06:52 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge --info xf86-input-mtrack (emerge.info,6.35 KB, text/plain)
2014-12-25 07:45 UTC, Duncan
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Duncan 2014-12-25 07:45:43 UTC
Created attachment 392352 [details]
emerge --info xf86-input-mtrack

I'm trying xf86-input-mtrack and input-synaptics with my new Logitech T650 touchpad (newly supported with the hid updates in kernel 3.19-rc1).

With input-mtrack, I can't get the autohide plasma (kde4) panel at the bottom of my screen to popup, tho I can get the "pre-glow" indicating I'm close to triggering the popup.  Testing with xev, the reason would seem to be that with a framebuffer height of 3*1080=3240 (three 1080p full-hd monitors stacked), the bottom row of pixels is 3239 (the top row being 0), while xev says the lowest I can get the pointer is 3238, still one row too high. =:^(

Input-synaptics doesn't have this trouble with the same touchpad (restarting X with the other driver configured), and a Logitech M510 mouse (on the same logitech unified wireless receiver), running with the standard evdev driver in the same x-session as the mtrack-driver touchpad, can reach 3239 according to xev, and pops up the panel just fine.

Which isolates the issue to the mtrack driver (despite my running xorg-server 1.16.2.901 and an rc1 kernel), and due to the one-pixel difference would seem to hint at an infamous off-by-one.  Unfortunately, at least so far finding where that is handled in the mtrack code seems to be beyond my limited non-coder code-reading and patching skills.. =:^(

FWIW, the x-axis seems fine, with xev saying it reaches 1919 on the 1920 px framebuffer. =:^)

emerge --info xf86-input-mtrack attached.
Comment 1 Matt Turner gentoo-dev 2017-01-26 06:52:37 UTC
Please file upstream. We're not capable of solving these issues.