Closing since 0.4.x is not supported any longer.
** Changed in: easystroke (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/480807
Title:
easystroke
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.
--
easystroke at times doesn't recognize mouse movement
https://bugs.launchpad.net/bugs/480807
You received
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
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:
--
easystroke at times doesn't recognize mouse movement
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
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!
--
easystroke at times doesn't recognize mouse movement
https://bugs.launchpad.net/bugs/480807
You
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
Well, after the latest suspend/wake-up, it happened again. Here's the
log.
** Attachment added: Easystroke log during fail conditions
http://launchpadlibrarian.net/36261067/easystroke.log
--
easystroke at times doesn't recognize mouse movement
https://bugs.launchpad.net/bugs/480807
You
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
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.
--
easystroke at times doesn't recognize mouse movement
https://bugs.launchpad.net/bugs/480807
You received this bug notification
Does restarting easystroke fix this? Can you attach a log of when this
happens (easystroke - easystroke.log)?
--
easystroke at times doesn't recognize mouse movement
https://bugs.launchpad.net/bugs/480807
You received this bug notification because you are a member of Ubuntu
Bugs, which is
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.
--
easystroke at times doesn't recognize mouse movement
https://bugs.launchpad.net/bugs/480807
You
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
13 matches
Mail list logo
