touchscreen only outputs right angles

Bug #204633 reported by Nathan Eckenrode
6
Affects Status Importance Assigned to Milestone
X.Org X server
Invalid
Undecided
Unassigned
xf86-input-evtouch (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Binary package hint: xserver-xorg

after getting touchscreen on Fujitsu U810 to work under gutsy, I upgraded to hardy and found that all output from the touchscreen was only in right angles.

this maybe within the xserver-xorg-evtouch package or the way xorg interacts with the driver.

please let me know what further information is needed in order to fix this bug, or to at least diagnose it properly.

Revision history for this message
Steve Magoun (smagoun) wrote :

This affects the Samsung Q1 running Ubuntu Mobile, too

Revision history for this message
Dustin Spicuzza (dustin-virtualroadside) wrote :

The evtouch driver is improperly configured by default (I've been meaning to file a bug about this.... this is as a good place as any to get someone to actually fix this ) with an undocumented option called "MoveLimit". It's set by default to a value like 180 or something like that... try setting it to < 50 or so, and see if you get better results.

Add the following to your xorg.conf file in the evtouch section:

   Option "MoveLimit" "40"

Adjust the value suitably, and it should fix it.

Revision history for this message
Dustin Spicuzza (dustin-virtualroadside) wrote :

I had this issue also.

Changed in xorg:
status: New → Confirmed
Revision history for this message
Nathan Eckenrode (nathaneckenrode) wrote :

ok i have edited my xorg.conf to have

    Option "MotionLimit" "2" #gives the best possible results so-far

but thehandwriting strokes in Xournal has the fuzzy appearance of bleeding ink now. it is usable but not optimal.

Bryce Harrington (bryce)
Changed in xorg-server:
status: New → Invalid
Revision history for this message
HITMAn (hitmansoft) wrote :

Option "MoveLimit" "10"

makes sense for me.

I am running Ubuntu Hardy on Samsung Q1U-EL.

Revision history for this message
Eric Drechsel (ericdrex) wrote :

It seems that this can be resolved with .FDI files like in
https://bugs.launchpad.net/ubuntu/+source/xf86-input-evtouch/+bug/261873

Revision history for this message
alsuren (alsuren) wrote :

This really shouldn't be fixed by setting movelimit really small. If you take a look at libtouch.c, once you get into the S_MOVING state, the code appears to not look at movelimit again until you release. It *should* work perfectly, but it doesn't.

If anyone wants to mentor me to fix this bug (or any others in evtouch), I'm happy to put in the hours over the next few weeks, because evtouch is really beginning to piss me off on my eeepc. I don't really know how to run X under a debugger though, so I'm currently limited to staring at code.

Bryce Harrington (bryce)
tags: added: hardy
Revision history for this message
Bryce Harrington (bryce) wrote :

[This is an automatic notification.]

Hi Nathan,

This bug was reported against an earlier version of Ubuntu, can you
test if it still occurs on Lucid?

Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue through
normal support channels, please see:

    http://www.ubuntu.com/support

If you are the original reporter and can still reproduce the issue on
Lucid, please run the following command to refresh the report:

  apport-collect 204633

If you are not the original reporter, please file a new bug report, so
we can work with you as the original reporter instead (you can reference
bug 204633 in your report if you think it may be related):

  ubuntu-bug xorg

If by chance you can no longer reproduce the issue on Lucid or if you
feel it is no longer relevant, please mark the bug report 'Fix Released'
or 'Invalid' as appropriate, at the following URL:

  https://bugs.launchpad.net/ubuntu/+bug/204633

Changed in xf86-input-evtouch (Ubuntu):
status: Confirmed → Incomplete
tags: added: needs-retested-on-lucid-by-june
Revision history for this message
Bryce Harrington (bryce) wrote :

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

Changed in xf86-input-evtouch (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.