© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
> While I am sure LIRC has a lot of uses. I would wager 90% of its users are using kodi.
This might be the truth as seen from the kodi community. However, from an upstream lirc point of view I cannot really see that the number of kodi users are dominating in any way.
> forgot a couple steps, here was all of them:
While these steps worked for you, other users will have other needs. That said, disabling/stopping lircd-uinput might be a good idea in many cases. The last update to lirc has it disabled by default.
> also some discussion here: https:/
That discussion is utterly confused and does not mention the need to migrate (manual or automatic) the old 0.9.0 setup to the new one. Also, some users in that thread are using the default driver while other seem to be using the devinput one. No one seems to be reading the documentation, but still seems to be able to establish the "fact" that lirc is broken.
If it was possible to file a bug against the Kodi community overall I would consider doing that ;)
On top of that Kodi is the one and only application which misuses lirc by using the raw events from the socket -- this makes lirc seriously crippled compared to the real stuff. I filed a bug on this long ago, but at a glance it seems to be lost.
Unless there is more input I will close this as not-a-bug.