You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using a noname USB remote control with my HTPC. It was working perfectly
on FreeBSD 9.2 and r209 of uhidd.
After I upgraded to FreeBSD 10 and the latest trunk version of uhidd I've got a
problem. Half of the buttons work as expected, but other half now behaves
strangely.
For example, when I press the play button (and release it):
KeyPress event, serial 47, synthetic NO, window 0x1c00001,
root 0x299, subw 0x0, time 295413843, (958,495), root:(960,540),
state 0x0, keycode 135 (keysym 0x70, p), same_screen YES,
XKeysymToKeycode returns keycode: 33
XLookupString gives 1 bytes: (70) "p"
XmbLookupString gives 1 bytes: (70) "p"
XFilterEvent returns: False
KeyRelease event, serial 47, synthetic NO, window 0x1c00001,
root 0x299, subw 0x0, time 295413884, (958,495), root:(960,540),
state 0x0, keycode 135 (keysym 0x70, p), same_screen YES,
XKeysymToKeycode returns keycode: 33
XLookupString gives 1 bytes: (70) "p"
XFilterEvent returns: False
And then another KeyPress, then KeyRelease, and so on indefinitely. Only the
time field changes. I have to hit Ctrl-C in xev.
I am not holding the button pressed, just a short press and release.
Other keys like arrows or enter give one Press and one Release as it was on
FreeBSD 9.2.
I start uhidd like this (with other flags the remote won't work at all):
uhidd_enable="YES"
uhidd_flags="-ou"
The remote is identified as:
ukbd0: <www.irfmedia.com W-01RN USBV3.1, class 0/0, rev 2.00/29.82, addr 2> on
usbus2
I tried to downgrade to r209 but it didnt help. Everything else in the system,
except upgrading to 10.0, is the same (uhidd.conf, xmodmap).
Can you help me please?
Original issue reported on code.google.com by [email protected] on 6 Feb 2014 at 6:18
The text was updated successfully, but these errors were encountered:
Original issue reported on code.google.com by
[email protected]
on 6 Feb 2014 at 6:18The text was updated successfully, but these errors were encountered: