Lirc 0.8.2 was released and includes this fix.
** Changed in: lirc (Ubuntu)
Status: Confirmed => Fix Released
--
lircd doesn't repeat key press with pinsys remote
https://bugs.launchpad.net/bugs/118515
You received this bug notification because you are a member of Ubuntu
Bugs, which is th
Uh, let me see Yes, it is!
http://lirc.cvs.sourceforge.net/lirc/lirc/daemons/hw_pinsys.c?view=log
It looks like the revision 5.9 broke it and the 5.10 solved it again.
--
lircd doesn't repeat key press with pinsys remote
https://bugs.launchpad.net/bugs/118515
You received this bug notif
Rodrigo,
Lirc 0.8.2 was released last month, was it resolved in that release, or is it
in a later version of CVS?
--
lircd doesn't repeat key press with pinsys remote
https://bugs.launchpad.net/bugs/118515
You received this bug notification because you are a member of Ubuntu
Bugs, which is the b
Well, It looks like this very problem was already solved in the CVS version of
the lirc homepage.
So I guess the next package update will fixed that.
Best regards.
Rodrigo.
--
lircd doesn't repeat key press with pinsys remote
https://bugs.launchpad.net/bugs/118515
You received this bug notifica
Unfortunately it is not always automatic (if an upstream author is
subscribed to Launchpad it is, but that's not true for LIRC). :)
Additionally, it's best to get fixes sent as far upstream as possible so
that when they release their next version it includes your fixes. As
for this problem in pa
Not that I know, I'm just new to this Open Source... just got a bug, kill it...
and find someone to tell about!
Seriously, should I notify upstream? Isn't it automatic? How do I do that? Is
this the place to ask this??
--
lircd doesn't repeat key press with pinsys remote
https://bugs.launchpad
Thanks for tracking this down! Is this something that upstream knows
about? I seem to remember pinsys issues recently.
** Changed in: lirc (Ubuntu)
Importance: Undecided => Low
Assignee: (unassigned) => Kees Cook
Status: Unconfirmed => Needs Info
--
lircd doesn't repeat key pres
Well... I think I've got it!
When you press a key in the remote it sends 3 bytes:
The first is always 0xFE, the second is some kind of checksum and the third is
the key code in the lower 6 bits and a repeat flag in the 7th bit.
The current code considers the two last bytes as the key code, with th
