setting the state of a pointer

[krastanov.stefan at gmail.com]

Many more details can be found here
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1015183
I am on different hardware but have the same issues, namely:

I may use imprecise terminology, I do not know much about X.

 - press, notify and release events are generated by all of the
following: xdotool, usb mouse, the touchscreen itself. xlib python
bindings, and any other tool that I tried
 - the state stubbornly rests 0x110 or 0x100 (depending on numlock)

I will send the output of evtest attached in the following mail.

On 25 June 2012 03:16, Peter Hutterer <peter.hutterer at who-t.net> wrote:
> On Fri, Jun 22, 2012 at 09:59:42PM +0200, krastanov.stefan at gmail.com wrote:
>> Due to a problem with a touchscreen the state of the pointer gets
>> stuck to 0x110. How can I reset the pointer state? Using xdotool and
>> xte and generating mouse event with them did not work. Using a usb
>> mouse works, however the state continues to be stuck to 0x110.
>
> best to fix the touchscreen drivers. 0x110 means 0x10 (numlock) and 0x100
> (button 1). ignore the numlock, so this just means that the touchscreen
> never sends a button release event (or touch up, depending on what version
> of X you're running).
>
> I'd need to see the evtest output for this device and the xserver/evdev
> version you're running to say more though.
>
> Cheers,
>  Peter