Comment 6 for bug 480807

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).