Problems with licd.conf.atilibusb (Snapstream X10)

Bug #240537 reported by Neil
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lirc (Ubuntu)
Expired
Low
Unassigned

Bug Description

Binary package hint: lirc

After the last update lirc fails:
 * Loading LIRC modules [ OK ]
 * Starting remote control daemon(s) : LIRC [fail]

Even reverting to the last version doesn't work.

Revision history for this message
Mario Limonciello (superm1) wrote :

Please post the relevant configuration files that you have /etc/lirc/*conf so that we can diagnose this.

Changed in lirc:
status: New → Incomplete
Revision history for this message
Neil (n-layne) wrote :

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.

Revision history for this message
Neil (n-layne) wrote :

Oh, also the bug title was a mistake:
"Problems with **licd.conf.atiusb** (Snapstream X10)"

Revision history for this message
Mario Limonciello (superm1) wrote :

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:
status: Incomplete → Confirmed
Revision history for this message
Neil (n-layne) wrote :

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?

Revision history for this message
Mario Limonciello (superm1) wrote :

This is the latest one that ships with lirc 0.8.3 in Intrepid.

Revision history for this message
Mario Limonciello (superm1) wrote :

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:
status: Confirmed → Incomplete
importance: Undecided → Low
Revision history for this message
Neil (n-layne) 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.

Revision history for this message
Mario Limonciello (superm1) wrote : Re: [Bug 240537] Re: Problems with licd.conf.atilibusb (Snapstream X10)

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 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.
>

--
Mario Limonciello
<email address hidden>

Revision history for this message
Neil (n-layne) wrote :

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.

Assuming it was the first item (ATI something or other) I removed that one, and put the everything else back. Fail.

For whatever reason the Snapstream must be at the top of the file.
If you put it below _anything_ it will fail.

It works fine if other items are below it... though, I couldn't say how they fair, as this is the only remote I own.

UNRELATED:
Lastly, I straightened out the code, because I thought it might be causing the issue (However unlikely, I thought I'd turnover every rock.)
It wasn't the issues, but I'm attaching it anyways, because it looks awful compared to the neatness of all the other remotes.

Revision history for this message
Mario Limonciello (superm1) wrote :

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:
status: Incomplete → Triaged
Revision history for this message
Steffen Barszus (steffenbpunkt) wrote :

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.

Revision history for this message
Alec Leamas (leamas-alec) wrote :

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 0.9.4c. Please test if you are still interested in this bug.

Setting status triaged -> incomplete since the status against current code is unknonw

Changed in lirc (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for lirc (Ubuntu) because there has been no activity for 60 days.]

Changed in lirc (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.