Chase, I'm a little unclear on what the two distinct issues are: could you explicitly state them? And indicate which issue this ticket should be addressed to? We can then create a second ticket for the other one.
At least partially, it sounds to me that the issue that MacRules/Vincent is having may be driver/firmware-related? I haven't seen this problem on supported hardware list at all (since I calibrated my N-trig-based Lenovo); have you? Every touch I make one the screen with one finger results in a movement of the cursor to the new touch point. However, Chase you mentioned a fix that is targeted for Natty. Was that in response to this part of MacRules/Vincent's comment: "The other thing is, when I use the driver that does not send the mtY and mtX (both) then this issue also does not occur. So linking all that, I would think that when a touch is performed, some mechanism checks if both mtX and mtY are there and if so, tries to determine something about a simple touch that couses a different interpretaton to X then expected." Chase, to be explicit: * do you think that MacRules/Vincent's issue is grail-related? * if there are two issues at play in his comment, is one of them appropriately associated with this bug? * if so, which one? * if one or more of his issues aren't grail-related, where should they be filed? * are there files or any command output that MacRules/Vincent: on the calibration side of things, my N-trig device was also consistent with the placement of the cursor (position-wise). However, many (most) times it would simply not interpret a touch unless I pressed very hard. Calibrating with our N-trig calibration tool (written by Rafi Rubin) fixed all of that for me. Does your "GeneralTouch Win7 TwoFinger device" have a calibration tool for Linux? If they only have a Windows calibration tool and you have a Windows partition, I'd highly recommend running it. If there's even a chance that it could fix this issue, it's worth pursing. If after calibration you are still experiencing the issue, and it's a problem with grail, once grail is fixed, you'll be able to test it out simply by adding the appropriate PPA to your apt sources. No need to upgrade your whole system (which isn't actually an option right now, since the debian sync doesn't finish until December... though it should be starting nowish). To be clear, though: our target for Maverick was publicly announced to a very limited initial set of 4-touch hardware. This list of devices has already doubled in size (including several 10+ touch devices), so we're making great progress. For supported devices, uTouch is most definitely working. Let's see if we can get your hardware supported as well :-) (Henrik and Chase have been working to get other 2-touch devices supported). -- XInput single-touch events aren't always filtered https://bugs.launchpad.net/bugs/637106 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
