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 it.
On Wed, Sep 24, 2008 at 02:21, Neil <email address hidden> wrote:
> 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 could do is identify the defective remove in Hardy... But I
> don't have the old lircd.conf.atiusb.
>
> --
> Problems with licd.conf.atilibusb (Snapstream X10)
> https://bugs.launchpad.net/bugs/240537
> You received this bug notification because you are a member of
> Mythbuntu, which is subscribed to lirc in ubuntu.
>
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 lirc/remotes. Either way, if you identify something defective in
/usr/share/
either config, we can take care of it.
On Wed, Sep 24, 2008 at 02:21, Neil <email address hidden> wrote:
> I'm sorry, I thought I had posted back. /bugs.launchpad .net/bugs/ 240537
>
> 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 could do is identify the defective remove in Hardy... But I
> don't have the old lircd.conf.atiusb.
>
> --
> Problems with licd.conf.atilibusb (Snapstream X10)
> https:/
> You received this bug notification because you are a member of
> Mythbuntu, which is subscribed to lirc in ubuntu.
>
--
Mario Limonciello
<email address hidden>