[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/240537
This is fixed in current 0.9.4c release - the "fix" being that the
remote definitions no more are part of lirc. The new remote definitions
lives at http://sf.net/p/lirc-remotes: please file there bugs if you
consider them wrong.
To work on with this bug we need it confirmed on current version
Still a problem. In that file many remotes share the same keys and those
one remote is overwriting the other or can not be overwritten. There
needs to be a seperate file for those.
--
Problems with licd.conf.atilibusb (Snapstream X10)
https://bugs.launchpad.net/bugs/240537
You received this bug
Sorry about the delay on this... But I just installed Intrepid.
The bug persisted, so I removed every remote, one at a time, until only the
Firefly was left.
Each time I removed one, I restarted lirc. The remote did not work in any way
(via irw) until it was completely alone in the file.
That's entirely bzr, but thanks for the thorough diagnosis! Will try to
get this implemented in a cleanish way and hope nothing else breaks :)
** Changed in: lirc (Ubuntu)
Status: Incomplete = Triaged
--
Problems with licd.conf.atilibusb (Snapstream X10)
Neil:
I'd like to see this fixed in Intrepid while there is still time. Could
you try to isolate the bad remote?
** Changed in: lirc (Ubuntu)
Status: Confirmed = Incomplete
** Changed in: lirc (Ubuntu)
Importance: Undecided = Low
--
Problems with licd.conf.atilibusb (Snapstream
I'm sorry, I thought I had posted back.
The conf.atiusb in Intrepid uses entirely different codes for the
Snapstream. I don't have anything to install Intrepid on, and have no
idea how to pass a USB remote through VirtualBox. That version of the
conf might have even solved the bug.
The best I
Hi Neil:
Even though that conf uses entirely different codes, you should still be
able to use the conf on hardy.
Alternatively, the old hardy defective remote should have been stored in
/usr/share/lirc/remotes. Either way, if you identify something defective in
either config, we can take care
Please post the relevant configuration files that you have
/etc/lirc/*conf so that we can diagnose this.
** Changed in: lirc (Ubuntu)
Status: New = Incomplete
--
Problems with licd.conf.atilibusb (Snapstream X10)
https://bugs.launchpad.net/bugs/240537
You received this bug notification
Oh, also the bug title was a mistake:
Problems with **licd.conf.atiusb** (Snapstream X10)
--
Problems with licd.conf.atilibusb (Snapstream X10)
https://bugs.launchpad.net/bugs/240537
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I was able to resolve the issue by removing all the other entries in:
/usr/share/lirc/remotes/atiusb/lircd.conf.atiusb
It works fine, now. I'm not sure which was causing the issue, though.
** Attachment added: lircd.conf.atiusb
http://launchpadlibrarian.net/16768100/lircd.conf.atiusb
--
So something in that lircd.conf is doing it. By chance could you narrow
down what block was causing the errors? We can just remove that one.
** Changed in: lirc (Ubuntu)
Status: Incomplete = Confirmed
--
Problems with licd.conf.atilibusb (Snapstream X10)
I can try, but I no longer have a copy of the shipping default
lircd.conf.atiusb... Is there a way to just download that part of the
src?
--
Problems with licd.conf.atilibusb (Snapstream X10)
https://bugs.launchpad.net/bugs/240537
You received this bug notification because you are a member of
This is the latest one that ships with lirc 0.8.3 in Intrepid.
** Attachment added: lircd.conf.atiusb
http://launchpadlibrarian.net/16768371/lircd.conf.atiusb
--
Problems with licd.conf.atilibusb (Snapstream X10)
https://bugs.launchpad.net/bugs/240537
You received this bug notification
14 matches
Mail list logo