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 b
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)
https://bugs.launchpad.net/bugs
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 Ubu
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 beca
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.
Assumi
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)
https://bugs.launchpad.net/bugs/
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 X1
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 cou
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 b
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)
https://bugs.launchpad.net/bugs
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 Ubu
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 beca
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 X1
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 cou
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.
Assumi
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)
https://bugs.launchpad.net/bugs/
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 b
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)
https://bugs.launchpad.net/bugs
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 Ubu
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 beca
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 X1
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 cou
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.
Assumi
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)
https://bugs.launchpad.net/bugs/
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 X1
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 cou
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 b
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)
https://bugs.launchpad.net/bugs
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 Ubu
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 beca
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 b
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)
https://bugs.launchpad.net/bugs
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 Ubu
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 beca
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.
Assumi
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)
https://bugs.launchpad.net/bugs/
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 X1
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 cou
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.
Assumi
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)
https://bugs.launchpad.net/bugs/
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 b
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)
https://bugs.launchpad.net/bugs
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 Ubu
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 beca
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 X1
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 cou
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.
Assumi
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)
https://bugs.launchpad.net/bugs/
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 of
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 of
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 of
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 of
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 of
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 of
66 matches
Mail list logo