easystroke at times doesn't recognize mouse movement

[juliobahar]

Binary package hint: easystroke

On Karmic and also was on Jaunty.
Easystroke 0.4.9, doesn't recognize any mouse movements. As if it wasn't there.
It happens on both of my computers (desktop and laptop), I'm also using Compiz.

[Redge (redgetrek)]

Same here, though for me it still worked in Jaunty. It wasn't directly after Karmic upgrade that it stopped working: after a while it just doesn't detect mouse gestures anymore. Now I've tried every button on the mouse, tried completely reinstalling easystroke but no luck.

Also using btnx, but the problem persists whether btnx is active or not.

[Redge (redgetrek)]

After I rebooted, easystroke was back. Now it's gone again. I'm not sure, but I suspect it might be related to suspend/wake-up. Other mouse related activities are also starting to act strangely.

[Tom Jaeger (thjaeger)]

Does restarting easystroke fix this? Can you attach a log of when this happens (easystroke -vvvv > easystroke.log)?

[Redge (redgetrek)]

So far I haven't had any problems since the last kernel update. When it happened, restarts did not fix the problem. If/when it occurs again, I'll post the log.

[Redge (redgetrek)]

Well, after the latest suspend/wake-up, it happened again. Here's the log.

[Tom Jaeger (thjaeger)]

Thanks for the log. I think what the issue is that you have two "Logitech USB Receiver" devices, one of which sends bogus motion events (or no motion events at all). Easystroke will only accept input from the device which emitted the first press, so if the buggy device wins the race, easystroke will not work. The troube is that they have the same name, so you can't turn one of them off selectively in the preferences.

You can completely deactivate the offending device (my guess would be that it's the absolute logitech device) using the xinput tool: Use "xinput list" to get the device number and then use "xinput set-prop <device-num> 'Device Enabled' 0" to disable the device. If this fixes the issue, I can add a workaround to easystroke for this particular situation (it's ultimately a bug in the driver, though).

[Redge (redgetrek)]

Hmm, the command xinput set-prop doesn't seem to work. For me, it just prints usage:

usage :
 xinput get-feedbacks <device name>
 xinput set-ptr-feedback <device name> <threshold> <num> <denom>
 xinput set-integer-feedback <device name> <feedback id> <value>
 xinput get-button-map <device name>
 xinput set-button-map <device name> <map button 1> [<map button 2> [...]]
 xinput set-pointer <device name> [<x index> <y index>]
 xinput set-mode <device name> ABSOLUTE|RELATIVE
 xinput list [--loop || --short || <device name>...]
 xinput query-state <device name>
 xinput test [-proximity] <device name>
 xinput version
 xinput list-props <device> [<device> ...]
 xinput set-int-prop <device> <property> <format (8, 16, 32)> <val> [<val> ...]
 xinput set-float-prop <device> <property> <val> [<val> ...]
 xinput set-atom-prop <device> <property> <val> [<val> ...]
 xinput watch-props <device>
 xinput delete-prop <device> <property>

I've tried it using set-int-prop, but I can't get it to work.

[Tom Jaeger (thjaeger)]

Sorry, I didn't realize the version of xinput in karmic was this old.
"xinput set-int-prop <device-num> 'Device Enabled' 8 0" should work then.

Redge wrote:
> Hmm, the command xinput set-prop doesn't seem to work. For me, it just
> prints usage:

[Redge (redgetrek)]

That disabled the device, but didn't solve the problem. It turns out one of those Logitech USB devices was for the mouse part of the mouse (Logitech MX Revolution btw), and the other device was listed as a keyboard. The mouse has a button on it that's equivalent to XF86Search, and this button was all that was disabled. Anyway, the easystroke problem persisted.

[juliobahar (yahalla-julio)]

This tweak worked so fine with me, easystroke started recognizing my mouse gestures after following your code, and this is what I did.

(1) Quit easystroke
(2) $ xinput set-int-prop "SynPS/2 Synaptics TouchPad" 'Device Enabled' 8 0
(3) Restarted easystroke again

of course my touchpad went off now after step (2). I didn't have time to figure out the xinput manual. Yet, I'm really very happy for the gestures of my Logitech mouse to work again without restarting the whole system.

Btw, how to switch the touchpad back again.. :d

[juliobahar (yahalla-julio)]

xinput set-int-prop "SynPS/2 Synaptics TouchPad" 'Device Enabled' 8 1

Returned my touchpad to on again. Moreover, I'm able to do gesture not only with the mouse now but with the touchpad too.

Nice!

[Redge (redgetrek)]

Well, after the problem occurred again I ran another xinput list, and I saw an entry titled "Macintosh mouse button emulation". After disabling that one, easystroke started working again.

[Tom Jaeger (thjaeger)]

Closing since 0.4.x is not supported any longer.