[Expired for lirc (Ubuntu) because there has been no activity for 60
days.]
** Changed in: lirc (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to lirc in Ubuntu.
Basically, it isn't buggy but requires manual intervention when
updating.
A script called lirc-setup is however broken. It's primary use-case is
fresh installs rather than updates which have no need for it. A
workaround to make it wotk could be found in comment #2.
Some users have had problems
@Alec, could you provide some details on how buggy it is/the
Debian|upstream fix, which would help to at least fix that issue in
bionic...
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to lirc in Ubuntu.
> I suppose it is a bug, as lirc should work after upgrade without
manual reconfiguration.
No it should not, as apparent if you read the comkplete discussion in
this bug or, more on the spot, bug #1788235.
--
You received this bug notification because you are a member of Mythbuntu
Bug Team,
I upgraded from 16.04 to 18.04 and lirc does not work anymore. systemd shows
errors such as "lircd-0.10.0[928]: Error: Cannot glob
/sys/class/rc/rc0/input[0-9]*/event[0-9]*"
I suppose it is a bug, as lirc should work after upgrade without manual
reconfiguration.
--
You received this bug
The main issue described in this bug is bogus, as apparent from bug
#1788235
However, the configuration script lirc-setup *is* indeed broken . This
is fixed in Debian upstream from 0.10.1, but hasn't trickled down. That
said, users will still need to read README.Debian, and the process to
That said, if someone filed a bug against lirc because lirc-setup is
broken, that bug is certainly valid. But IMHO, that's a very different
story. And since there is a usable work-around it would probably just be
closed as fixed upstream.
--
You received this bug notification because you are a
What's the issue exactly? That the package doesn't show a text interface
to configure things anymore? That seems the same than bug #1788235 which
has been closed as not being a bug
@Alec, the issue you are referring to is different right?
** Changed in: lirc (Ubuntu)
Importance: Undecided =>
I can confirm the issue on Ubuntu 18.04 Server.
If there is a fixed upstream version, what is needed to see an updated package
in Ubuntu?
Is there anything I can help with?
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to lirc in
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 Mythbuntu
Bug Team, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1791409
This is fixed in debian upstream. Until this trickles down, the walk-
around is something like
# 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
Lirc configure script still dosen't work in 18.10 beta. It seems there
hasn't been any attempt to fix this...
--
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/1791409
Title:
LIRC not
12 matches
Mail list logo
