Take the 2-minute tour ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free, no registration required.

When I connect my Surface Pro running 12.04 to a second (non-touch) monitor (Westinghouse Digital Electrons 19'', 1280x1024 for example, but happens with another Dell monitor), the touch screen on my surface responds but places the cursor in the wrong location. If I have the 2nd monitor set to display above my surface, the cursor appears about 1-2 inches directly above where my finder or stylus is touching the screen.

Actually if I touch the screen at the bottom of the Surface screen, the cursor is directly under my finger as expected. The further I move the finger up, the further the cursor moves away from the finger. With my finger at about the midpoint of the surface screen, the cursor is in the black bar, nearly on the second screen. If the second monitor is displayed to the left of the Surface, the cursor is too far to the left, etc.

share|improve this question

closed as off-topic by user68186, Braiam, Seth, Eric Carvalho, Alaa Ali Sep 10 '13 at 16:18

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Bug reports and problems with the development version of Ubuntu should be reported on Launchpad so that developers can see, track and fix these issues." – user68186, Braiam, Seth, Eric Carvalho, Alaa Ali
If this question can be reworded to fit the rules in the help center, please edit the question.

    
This looks like a serious bug. It sounds like the algorithm for encoding and decoding touch points has something to do with it. Maybe it's mapping touch coordinates using an analog method, and applying it to the screen based on a percentage of the total screen size/resolution, when it should specify the screen of the touch device itself. There might be a fix someone knows, but I would suggest reporting this to Canonical's bug team somehow, if it's not already on their list. (I don't know anything about this stuff, I'm just trying to brainstorm) –  Alex Aug 5 '13 at 13:32
    
Have you tried to recalibrate your device and can you tell me when this issue first appeared? –  user191516 Sep 9 '13 at 20:59