https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1788235/comments/16
is a beginning...
--
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/1788235
Title:
lirc broken on 18.04
Status in li
I did already
# libdir=/usr/lib/x86_64-linux-gnu/python3.6/site-packages
# cp /usr/share/lirc/python-pkg/config.py $libdir/lirc
# ln -s $libdir/lirc /usr/lib/python3/dist-packages/
# ln -s $libdir/lirc-setup /usr/lib/python3/dist-packages/
as superuser and
'systemctl disable --no
^fails. If I add the lirc group, then I can run 'sg dialout lirc-setup',
and setup, and even make ir receiver react, but testing by irw still
does not display anything. Is there some guide for what has changed so
that setting up correctly would be easier?
--
You received this bug notification bec
I tried running lirc-setup on fresh 18.04 install, but it fais as group
lirc does not exist.
--
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/1788235
Title:
lirc broken on 18.04
Status in
Thanks Alec. I'm a Linux nobi and your fixes are definitely better
suggestions.
--
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/1788235
Title:
lirc broken on 18.04
Status in lirc package
> Kodi definitely works with the latest versions of Lirc and the problem i
> is very easy to fix so stop downgrading your systems to an older version of
> Lirc
Right.
> The problem is Kodi defaults to looking for a Lirc socket at /dev/lircd which
> doesn’t exist anymore.
Has anyone cared t
Kodi definitely works with the latest versions of Lirc and the problem
is very easy to fix so stop downgrading your systems to an older version
of Lirc
The problem is Kodi defaults to looking for a Lirc socket at /dev/lircd
which doesn’t exist anymore. In Lirc > 0.9.0 the socket is now defined
So, changing status.
@xekon: dpkg-reconfigure doesn't do anything at all...
** 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.
https://bugs.launchpad.net/bugs/
> @»ekon, @Alec, thanks for your comments, reading those it looks like
you are stating that there is no real bug, just that the changes in the
software and its configuration files confused users that were used to
the old way? E.g nothing that needs to be resolved?
Right, from my point of view this
@seb128) So to answer your question directly, Yes, that is what I was
saying, at least in my situation, that Lirc is functioning properly and
I have zero complaints.
I have not yet tested the ir sending functionality yet, but ir receiving
is working here. I planned to test sending ir commands to c
---
sudo apt purge ir-keytable lirc
sudo apt-get install -y lirc lirc-compat-remotes
sudo dpkg-reconfigure lirc
sudo irw
sudo systemctl stop lircd-uinput.service
sudo systemctl disable lircd-uinput.service
sudo cp /usr/share/kodi/system/Lircmap.x
sudo apt purge ir-keytable lirc
sudo apt-get install -y lirc lirc-compat-remotes
sudo dpkg-reconfigure lirc (no screen opens, but i ran this anyway incase it
creates files)
sudo irw
sudo systemctl stop lircd-uinput.service
sudo systemctl disable lircd-uinput.service
sudo cp /usr/share/kodi/system
@»ekon, @Alec, thanks for your comments, reading those it looks like you
are stating that there is no real bug, just that the changes in the
software and its configuration files confused users that were used to
the old way? E.g nothing that needs to be resolved? Or is there some
action needed?
--
@seb128: The missing UI refers to the reconfiguration UI which was part
of lirc up to 0.9.0. This reflected even older code containing kernel
modules where lirc was rebuilt from source depending on configuration.
Nowadays lirc is a just a server with configuration files and there is
no need to make
Hi Alec Leamas and Sebastien Bacher, I did not actually open this bug
report. Somebody else did. I merely added to it my experience, also from
my point of view you are both exactly right, because currently my Lirc
0.10.0-2 is working perfectly :)
--
You received this bug notification because you
Trying to understand the bug here, the title is not very describtive,
how is it broken? reading the comments the issue seems to be rather
"lirc can't be easily configured" is that correct? (you miss a "dpkg-
reconfigure lirc" UI that allow easy configuration)?
--
You received this bug notificatio
The configuration format/system units, etc are described in
https://sourceforge.net/p/lirc/git/ci/debian-0.10/tree/debian/README.Debian
. Does that cover the questions/problems described there? In any case
having a better description of what you are trying to do and what you
expect/isn't as you thi
Seems that we agree that the idea that lirc as of 18.04 is "broken" is
plain wrong.
The problem is about making a correct upgrade which involves manual
steps as described in README.Debian (with a notification in the upgrade
message).
--
You received this bug notification because you are a member
I will try to file a bug, they just recently moved their bug tracker to
github: https://github.com/xbmc/xbmc/issues
Thank you.
--
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/1788235
Title
> Is there more documentation at a website that I could read to learn
more?
The official site is http://lirc.org. Among other things, here is an
updated Configuration Guide.
> I am particularly interested in the info about the raw events from the
socket.
At the same site there is info on the API
I appreciate that input! I learned a lot just from reading what you
posted there.
Is there more documentation at a website that I could read to learn
more?
I am particularly interested in the info about the raw events from the
socket.
I am wondering if I can get lirc to work with kodi without do
> 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, her
While I am sure LIRC has a lot of uses. I would wager 90% of its users
are using kodi. At times it can be difficult to find a good howoto
guide, that walks you through a freshly installed ubuntu system, to a
working LIRC remote. I am very happy to have mine working again.
I forgot a couple steps,
Now, considering these reports one cannot IMHO really say that lirc is
'broken'. What could be said is that the upgrade to the new version
requires manual steps, none of which mentioned in this report.
The manual steps are documented in the file
/usr/share/doc/lirc/README.Debian.gz -- this is pres
I actually have lirc 0.10.0-2 working again:
I actually had lirc_0.10.0-2 installed and working (and it still does on
my other system)
but for some reason after dist-upgrade and a reboot it was broken.
I followed the workaround listed 0.9, it worked.
I then unmarked the package as held and dist-
I just wanted to report that initially I was using Ubuntu 18.04 and the
lirc from the repository worked, appears to be:
apt-cache show lirc
Package: lirc
I can confirm that the workaround works.
I think the main problem is that bionic's lirc is using a different
configuration file for lirc (lirc_options.conf instead of
hardware.conf). I can make my remote work by setting the driver up in
lirc_options.conf manually. By installing lirc-compat-remotes
@leamas-alec Any ideas on a proper fix?
--
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/1788235
Title:
lirc broken on 18.04
Status in lirc package in Ubuntu:
Confirmed
Bug description
I've tried the workaround, and it worked for me as described. :-)
--
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/1788235
Title:
lirc broken on 18.04
Status in lirc package in Ubuntu:
I can confirm the issue on a recently fresh installed Ubuntu Server
18.04. The goal was to transform the installation to a HTPC running kodi
and tvheadend (hts). Here are some links to guys who had the same
experience and offer a workaround until the fix of the package.
Same experience:
https://fo
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/1788235
T
** Tags added: boinic
--
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/1788235
Title:
lirc broken on 18.04
Status in lirc package in Ubuntu:
New
Bug description:
Lirc 0.10.0-2 is nev
32 matches
Mail list logo
