You are indeed right. Python libraries are not multilib, and should live
in /usr/lib/python3/site-packages. Will fix, but the process starts at
the Debian side.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
The core issue here is the dependency in vdr. There is a ticket [1]
about this.
Otherwise, the simple work-around is uninstall the lirc package.
This is an old bug. I see no new reports or comments lately, which seems
to indicate that it is fixed in current release.
[1]
Filed vdr issue: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=1012274
** Bug watch added: Debian Bug tracker #1012274
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012274
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Sorry for late reply.
The python module contains binary. architecture-dependent code and can
for that reason not be installed in /usr/lib/python3/ due to overall
multi-arch requirements.
That said, the official Debian documents I find are not explicit on how
to install these kind of modules.
lirc does not spam the log if correctly configured. The repeated
messages is a actually a feature since it's an easy way to detect status
when configuring and hot-plugging a device.
The basic issue here is if lirc is pulled in as a dependency. It should
not, it's designed to be used by users
[sorry for late walking through bugs]
Have you tried the installation instructions as described in the
upstream docs[1] ?
[1] https://www.lirc.org/html/configuration-guide.html
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in
Late comment: vlc does not depend on lirc any more, so this should not
happen to new installations.
Work around for existing installations is to either remove the lirc
package or simply disable lircd.socket, lircd.service and lircd-uinput
using systemctl.
--
You received this bug notification
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
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
> 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 Desktop
Packages,
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
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
> 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
To further investigate this issues, a question is if the main lirc
package is installed. If so, the lircd.socket, lircd.service and lircd-
uinput.services should be disabled and stopped. If problem persists,
with or without liblircclient installed, this should be re-assigned to
the kernel
--
You
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
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.
> @»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
@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
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
> 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
> 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,
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
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
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.
The package contains a README.Debian.gz file which explains the changes
done. A reference to this file was displayed when you upgraded lirc, but
perhaps you missed it (such things happens, for sure).
The update 0.9.0 -> 0.9.4 is a breaking update requiriung manual
intervention as described in
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
Previous versions needed some configuration to basically make a
conditional compilation. Possibly, submitter expects the configuration
menu as of 0.9.0. However, there is no such menu in 0.9.4 - all
configuration is done after installation using regular configuration
files
Given this, my
Re-assigning to kernel packagem possiblye the wrong one.,
** Package changed: lirc (Ubuntu) => kernel-package (Ubuntu)
--
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/1681838
Title:
IR
> 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.
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
For the sake of order, this bug should be re-assigned to the kernel
package instead of the user-space lirc package.
--
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/1681838
Title:
IR
This bug is 8 years old, The primary culprits hald and hardware.conf are
gone and this bugf shouldI MHO be closed.
--
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/206495
Title:
hvr-1100
After a second thought I think this is wontfix. Setting up lirc is a
complex task, and enabling a service in the standard session GUI tools
is a small problem compared to other. Also, the 'parse .lircrc'approach
just don't work since applications can store them anywhere. And does so.
--
You
Setting Incomplete to let bug expire. Please change if you don't wan
bug to expire-
** Changed in: lirc (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
So,I'm not allowed set it to wontfix. Setting Incomplete, please change
you don't want this bug to be closed.
** Changed in: lirc (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in
Now, suspend-resume is about the kernel, the extra modules secion. But
which iof them? Just don't know.
** Package changed: lirc (Ubuntu) => linux-lts-xenial (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
Re-assigning to kernel - this is teh way to clarify whether it's a bug
or just documented behaviour.
--
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/359356
Title:
USB device attached to
Closing as fixed, since release 0.9.4c does not use sysV scripts or
hardware.conf.
** Changed in: lirc (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
As for the lirc part, the last 0.9.4 release solves this since the lircd
output socket is created at an very early point in the boot sequence.
lircd is started using socket activation when irexec or some otther
client connects to the socket. So, no race is possible.
IMHO, mysql should do the
At second thogt this is a mythbuntu issue, re-assigning.
Please note that that from 0.9.4 lirc no longer supports hardware.conf.
In short, each lircd instance is configured as a systemd service. There
is also a ren lirc_options.conf file which defines default values for
command line options. See
This do belong to mythbuntu since it's about the automatic generation
of config files. Still unsure which of the mythbuntu packages, sorry.
** Package changed: lirc (Ubuntu) => mythbuntu-common (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which
The last release 0.9.4c dos not support hardware.conf anymore, so this
is bug is obsoleted. Closing as "FixReleased", short of better options.
** Changed in: lirc (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages,
* Last parts of libirman dependencies removed.
* Changing Vcs-* headers to point to upstream packaging branch.
* Fixes existing large number of upgrade bugs.
* Enhance hardening flags.
* Add a lintian pbuilder test, this requires --hookdir and B92-test-pkg
therein.
* Tested (build-w
ed.
* Changing Vcs-* headers to point to upstream packaging branch.
* Fixes existing large number of upgrade bugs.
* Enhance hardening flags.
* Add a lintian pbuilder test, this requires --hookdir and B92-test-pkg
therein.
* Tested (build-wise) on stretch and sid.
-- Alec Leamas
At a second thought; Since it's now supported, let's close bug
** Changed in: lirc (Ubuntu)
Status: Incomplete => Fix Committed
** Changed in: lirc (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages,
expiring manually
** Changed in: lirc (Ubuntu)
Status: Incomplete => 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/238032
Title:
lircd doesn't find dvico usb IR remote
Expiring
** Changed in: lirc (Ubuntu)
Status: Incomplete => 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/663651
Title:
Streamzap remote control not operating correctly
mber of upgrade bugs.
* Enhance hardening flags.
* Add a lintian pbuilder test, this requires --hookdir and B92-test-pkg
therein.
* Tested (build-wise) on stretch and sid.
-- Alec Leamas <leamas.a...@gmail.com> Thu, 26 May 2016 11:14:25
+0100
** Changed in: lirc (Ubuntu)
The patch is for kernel code, reassigning.
--
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/626633
Title:
Missing MCE remote from default config file
Status in linux-lts-utopic package
Any news on this? Otherwise, without further input, I suggest this is
closed.
** Changed in: lirc (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
Possibly , wrog version
** Package changed: lirc (Ubuntu) => linux-lts-utopic (Ubuntu)
--
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/626633
Title:
Missing MCE remote from default
eaders to point to upstream packaging branch.
* Fixes existing large number of upgrade bugs.
* Enhance hardening flags.
* Add a lintian pbuilder test, this requires --hookdir and B92-test-pkg
therein.
* Tested (build-wise) on stretch and sid.
-- Alec Leamas <leamas.a...@gmail.com&g
+ explicit link
to walk around #801719 (dh_python3 shortcomings).
* Last parts of libirman dependencies removed.
* Changing Vcs-* headers to point to upstream packaging branch.
* Fixes existing large number of upgrade bugs.
* Enhance hardening flags.
* Add a lintian pbuilder test, th
indeed the kernel,media subsystem,possibly wrong version
** Package changed: lirc (Ubuntu) => linux-lts-utopic (Ubuntu)
--
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/663497
Title:
Same expired goes for lirc...
** Changed in: lirc (Ubuntu)
Status: Triaged => Incomplete
--
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/238032
Title:
lircd doesn't find dvico
..unless there is more input
--
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/238032
Title:
lircd doesn't find dvico usb IR remote device correctly (expects
/dev/lirc)
Status in
Perhaps wrong kernel version, duuno. But it's the kernel, media
susbsystem.
** Package changed: lirc (Ubuntu) => linux-lts-utopic (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
Closing bug, as it's very old and a fix is committed,
** Changed in: lirc (Ubuntu)
Status: Triaged => Fix Released
--
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/626030
Title:
Does this mean that the bug is gone after updating hardware.conf?
** Changed in: lirc (Ubuntu)
Status: Confirmed => Incomplete
--
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/991116
The last lirc update 0.9.4 more or less obsoletes this bug since this
kind of configuration doesn't take place. In order to verify this bug we
need some testing on the latest version.
If you are still interested in this bug, please provide some feedback
from testing with 0.9.4c- Otherwise,
confirmed -> incomplete since we have no info on the status with recent
lirc versions.
--
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/786254
Title:
lirc not working, irw empty, irrecord
We think this bug is resolved in the last update 0.9.4c (zesty). If you
are still interested in it, could you please provide som feedback from
testing this version? There are backport version available at my ppa:
https://launchpad.net/~leamas-alec/+archive/ubuntu/lirc-0.9.4.
Otherwise, without
The kernel (media susbsystem), possibly wrong version
** Package changed: lirc (Ubuntu) => linux-lts-utopic (Ubuntu)
--
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/826562
Title:
Marking as incomplete since we have no information if this bug is still
present in recent versions.
--
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/614289
Title:
LIRC MCE USB Config
The former lirc modules now belongs to kernel (media subsystem)
** Package changed: lirc (Ubuntu) => linux-lts-xenial (Ubuntu)
--
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/912251
We believe this bug has been fixed by lirc updates since 0.6.0. In
particular, the last release 0.9.4 does not rebuild lirc in any way and
these kind of problems just cannot occur (not to say other probklems
couldn't).
Please let us know if you are still interested in this. Otherwise,
without
Possibly wrong kernel version... but still the kernel (media subsystem)
** Package changed: lirc (Ubuntu) => linux-lts-utopic (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
The key issue her is how irexec is started. When you add the irexex
entry, do you provide the --daemon/-d option? If so, try without it.
If the --daemon option isn't active, this is likely a gnome bug.
program started from ~/.config/autostart is certainly a session issue.
If you are still
Indeed the kernelk (media subsystem), but possibly the wrong version...
sorry
** Package changed: lirc (Ubuntu) => linux-meta-lts-xenial (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
Well, that lien explains some of these bugs. However, it's old and the
question now if is you are still interested in this.
That said, a missing remote is not a bug but a support request. Please
refer to the upstream mailing list at http://sf.net/p/lirc if you need
assistance with unknown
** Changed in: lirc (Ubuntu)
Status: New => 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/657991
Title:
lirc fails to work with mce remote
Status in lirc package in
This bug is old. Does it still affect you? if so , please let us know.
Otherwise, without further input, let's close this bug.
** Changed in: lirc (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
This bug is obsoleted by the new 0.9.4 version which doos not build
rebuild lirc in any case.
If you are still interested in this bug please let us know. Otherwise,
without further input, let's close this bug.
** Changed in: lirc (Ubuntu)
Status: New => Incomplete
--
You received this
This bug is old. Does it still affect you? In this case, let us know.
Otherwise, without firther input, let's close this bug
** Changed in: lirc (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Also, note that the new version 0.9.4 (zesty) basically obsoletes this
bug since it does not support hardware.conf
--
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/635947
Title:
I cannot see that this qualifies as a bug, it's more like a support
request "How should I configure lirc"· it's also very old. Closing.
Please refer to the upstream mailing list at http://sf.net/p/lirc if you
are still interested in this.
** Changed in: lirc (Ubuntu)
Status: New =>
We believe this problem is solved by the latest lirc update 0.9.4 in
zesty (it does not do any kernel module loading whatsoever). If you are
still ibterested in this bug, please provide some feedback from testing
zesty.
Otherwise, without further input, let's close this bug.
** Changed in: lirc
This is a HAL problem, and HAL is since long gone from modern linux'es.
If you are still interested in this bug please let us know. Without
further input the bug will be closed
** Changed in: lirc (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a
This is not a bug but a support request - lirc contains all the tools
and documentation to cope with an unknown remote. See e. g.,
http://lirc.org/html/configuration-guide.html which refers to the latest
lirc version 0.9.4 (zesty).
Closing thius bug. Please refer to the upstream maling list at
As of current lirc (zesty + all other distros) remote configurations
lives at http://sf.net/p/lirc-remotes. Please submit this config there
to make it availale to others.
This bug is old. Unless there is more input, lets close it. The remote
configurations used by 0.9.0 are dropped upstream and
This bug is old. Furhermore, lirc cannot accept bugs for each each and
every remote.not supported - lirc is designed to be able to cope woih
unknown remotes, but it requires user intervention.
If you are still intteresteed in this see the documentaion at
This is basaically a support request. Please refer to the upstream
mailing list at http://sf.nety/p/lirc; see also the configuration guide
at http://lirc.org/html/configuration-guide.html (which refers to latest
version 0.9.4 in zesty)
Closing bug
** Changed in: lirc (Ubuntu)
Status: New
Belongs to kernel, media subsystem, but will most likley expire
** Package changed: lirc (Ubuntu) => linux-lts-vivid (Ubuntu)
--
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/484796
Title:
Is this bug still valid? it needs to be tested on a more recent ub
ubuntu version to be processed. If you are still interested in this
byug, please let us know.
Re-assigning to kernel, since this is about the kernel module.
** Changed in: lirc (Ubuntu)
Status: New => Incomplete
--
You
This bug has too little information to be handled:
- what does irreccord say?
- what does dmesg say?
If you are till interested in this bug, please provide some more info
along these lines
** Changed in: lirc (Ubuntu)
Status: New => Incomplete
--
You received this bug notification
Any news here, or vcan we close this bug?
** Changed in: lirc (Ubuntu)
Status: New => Incomplete
--
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/398362
Title:
Unsupported Remote
If you are still interested in this bug, it needs to be tested with the
new 0.9.4c release, basically on a zesty host.
In the updated package you could use mode2 using --driver devinput to
check whether the kernel decodes the signals or not. If it doesn't, it
might be perfectly possible to
Have you still any problem with this? Otherwise, without further input,
let's close this bug.
** Changed in: lirc (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
Kernel, possibly wrong version... media subsystem, though.
** Package changed: lirc (Ubuntu) => linux-meta-lts-xenial (Ubuntu)
--
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/657954
This is basically about the kernel modules. Re-assigning to kernel. My
own opinion is that the bug should be closed as expired unless thee is
more input
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
This is not a bug but a support request. If you are still interested in
this bug, please refer to the upstream mailing list at
http://sf.net/p/lirc.
** Changed in: lirc (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages,
We need more info in order to advance this bug.
First, what is the "IR Tray"?. This is certainly not part of the lirc
package.
Secondly, testing with mode2(1) will reveal if this is about the kernel
not delivering timing ingo, or about a lircd failure.
Third, if the problem persists it needs
endencies removed.
* Changing Vcs-* headers to point to upstream packaging branch.
* Fixes existing large number of upgrade bugs.
* Enhance hardening flags.
* Add a lintian pbuilder test, this requires --hookdir and B92-test-pkg
therein.
* Tested (build-wise) on stretch and sid.
--
The last note in this bug is five years old, end both the kernel and
lirc startup sequence is heavily changed. Could you please test this bug
on upcoming zesty and lirc0.9.4c if you are still interested in this
bug?
Setting status to Incomplete, since without input on status on current
code we
These links makes no sense, at least not on a reasonable updated lirc.
The /dev/lirc? devices are lircd input stuff whereas the /var/run//lircd
devices are lircd output sockets. Linking input to output is, well, not
ideal.
Partly due to the the bad linking, partly due to the sheer age I'mn
Rwe-assigning to lernel. After all, missing drivers is a kernel issue.
--
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/1065138
Title:
Module lirc_wpc8769l not provided
Status in
Moving to kernel,, media subsystem. My own opinion is that this is
wontfix
** Package changed: lirc (Ubuntu) => linux-meta-lts-xenial (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
Probab,ly the kernel, put perhaps wrong version. Sorry. meda
subsystem, though.
** Package changed: lirc (Ubuntu) => linux-meta-lts-trusty (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
Re-assigning to kernel, this is seemingly about kernel modules and
mutexes..
--
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/574432
Title:
Lirc unable to initialise IR portion of Mplay
Definitely the kernel (meda subsystem), but perhaps wrong version.
Sorry, rookie doing my best...
** Package changed: lirc (Ubuntu) => linux-meta-lts-trusty (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
1 - 100 of 189 matches
Mail list logo
