Hi,
The content of my lircd.conf:
include "lircd.conf.d/*.conf"
that explains why it works, however, I got this after the --purge and did not
modify
Happy for this to be a support request, not a bug.
Cheers
Michael
--
You received this bug notification because you are a member of Desktop
Pa
Glad that it works for you. The question is just how...
As noted in the README, from 0.9.4 all lircd.conf files needs names like
mce.lircd.conf i. e., with a lircd.conf suffix. The default lircd.conf
files only includes files with this suffix. That said, a custom
lircd.conf could of course include
Oops... seems that the default lircd.conf only requires .conf suffix,
not lircd.conf. All solved, my bad.
** Changed in: lirc (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
h
Hi,
I have now reinstalled lirc and followed the upgrade steps to no avail. No
response from irw. However purge helped:
apt-get remove --purge lirc
Had to copy mce.conf:
cp /usr/share/lirc/configs/mce.conf /etc/lirc/lircd.conf.d
Now everything is back to normal, irw gives a response and so does k
Hi
Thank you for the response.
I did all the automatic upgrades on this machine over the years. irw did not
give a response after the upgrade, but I can try this again. I removed lirc and
after remapping some of the keys ( because x does not accept codes >255) the
remote works without lirc. I
At a closer look, the configuration seems messy. E. g.,
/etc/lirc/lirc.conf includes a file from /usr/share/lirc/configs, a
directory not present in 0.9.4.
Have you worked through the necessary manual upgrade steps as described
in /usr/share/doc/lirc/README.Debian.gz?
Note that the missing remote
> I figured out that the lirc device path changed in the new version.
This was actually changed in 0.9.0, upstream release (2011)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1685394
Are you actually using lirc here i. e., have you configured kodi to use lirc?
If not, this bug should be assigned to the kernel. The ir-keytable stuff is
actually part of the kernel...
If you indeed are using lirc, as a starter: what does irw(1) tell you
when pushing a button or two on the remo
Thank you very much for the suggestion. Unfortunately it did not help.
If I remove lirc, some of the keys work after a replug of the receiver.
Could have to do with the drivers as well?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc
I had a similar problem. irw was working great, but lirc was not working
at all with kodi. After much hassle, I figured out that the lirc device
path changed in the new version.
Start kodi by telling it where the lirc device moved to:
kodi -l /var/run/lirc/lircd
--
You received this bug notifica
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lirc (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1685394
T
11 matches
Mail list logo
