evtouch crashes Xorg on AMD GEODE

[Romeo]

Xorg locks-up only when i'm using evtouch touchscreen.

when i do double or tripple click on touchscreen Xserver locks-up. i can ssh into my box, see the logs, etc. but there're no something suspecious in it. i have enabled debug options in evtouch - all log activity stops when X is halt.

if i kill Xorg it stops, but display continues to show static image.
if i start Xorg again - it starts as usual.

i mentioned strange dependencies on system load
if i use touchscreen on pure X (only icewm manager is started) there're no lock-ups mentioned. if i start any GTK app (which doesn't consumes much CPU) lock-ups are very rare. but if GTK application starts consuming a lot of processing resources (i.e. starts frequent redraws, etc.) system can lock-up in some taps. but when i use mouse under the same conditions - no lock-ups are detected

this is not HAL-related problem as i do not use it,
i do enable send core events in evtouch config, so this issue is not goes from this.

I'm using Latest Karmic release with all packages up to date. this bug wasn't mentioned on 8.10

[John Jacob Jimgleheimer Schmidt (jeff-at-werk)]

I was getting the crash on Jaunty using evtouch with HAL and it stopped happening when I turned off 3 button emulation.

    <merge key="input.x11_options.Emulate3Buttons" type="string">false</merge>

Before that I could crash Xorg over and over again.

[johnnynyquist (johnnynyquist)]

"me too". Crashes occur during fast-clicking activity on the touchscreen; X ceases to respond entirely, but the machine continues to operate normally. Problem observed using both vesa and fglrx video drivers.

JJJS, you posted a code excerpt to turn off 3-button emulation. Where does that go? I would like to try it to see if it stops the symptoms on my system. (what does 3-button emulation even do on a touchscreen?)

[johnnynyquist (johnnynyquist)]

More info: my system is an AMD X2 5050e with ATI HD 3200 video card integrated in the motherboard. The 3200 is not supported by ati, radeon, or radeonhd but it runs [minimally] with vesa and [fully] with fglrx. system is up-to-date karmic. touchscreen is 0eef:0001 D-WAV Scientific Co., Ltd eGalax TouchScreen (from lsusb)

evtouch is xserver-xorg-input-evtouch 0.8.8-0ubuntu6.1

[Romeo (romeo-deepmind)]

I confirm that this is the evtouch driver bug! i've rewritten the driver for my custom needs and everything has gone. the problem was in libtouch timers, so i've disabled all unneded functions for my application.

if you don't need 3 button emulation an right-click emulation i can send you my source or precompiled version to try.

[johnnynyquist (johnnynyquist)]

Hmm.. well, considering I'm already making do without click and drag (pending a fix for #357832), I don't think I could operate if right-click didn't work either.

I don't need (or know how to access) 3-button emulation, and it looks like just disabling that might help (comment #1). How do I do it?

[Romeo (romeo-deepmind)]

that's my custom build of evtouch driver. it has minimal possibilities but fully answers the demands for my application (touchscreen for pay terminals). it traces only button_press, button_release, and cursor positioning events. if you need to emulate right-click or other stuff you need to write your own state-machine over this build. i've cut out practically everything from this driver, so it is rather simple to understand the code.

some words about configuration and calibration. this driver needs manual configuration, so be patient as you will be "modifying xorg.conf-restarting xorg" for some time before you get it work properly.

config options are:

Option MinX "200"
Option MaxX "2000"
Option MinY "200"
Option MaxY "2000"

Option ButtonNumber "1" #this shows which button click do we emulate - default is the left one

Option Rotate "CW" # or CCW

Option SwapX "0" #or 1
Option SwapY "0" #or 1

any other doesn't makes sense, except

Option ScreenNumber 0

which i don't know is made for (for multi-screen setups i guess)

feel free to ask any questions concerning the code. hope this will help you.

[Bryce Harrington (bryce)]

[This is an automatic notification.]

Hi Romeo,

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 492679

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 492679 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/492679

[Bryce Harrington (bryce)]

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.

[johnnynyquist (johnnynyquist)]

I can confirm that this problem has gone away on lucid (just in time for maverick, of course)