mythbuntu-bugs team mailing list archive

[Alec Leamas <1788235@xxxxxxxxxxxxxxxxxx>]

> 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://forum.kodi.tv/showthread.php?tid=324727

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.

-- 
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1788235

Title:
  lirc broken on 18.04

Status in lirc package in Ubuntu:
  Confirmed

Bug description:
  Lirc 0.10.0-2 is never configured after installation. Manually running
  "dpkg-reconfigure lirc " also does not do anything. I also noticed
  that /usr/share/lirc/remotes is empty, which is where I had my config
  file for Ubuntu 16.04.

  This was an upgrade install from 16.04.
  Searching the web indicates others have this problem. Some have reverted to the lirc from 16.04. Others recommend using pip3 to install lirc 0.10.10, but I have been unsuccessful so far.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1788235/+subscriptions