Check the TRANSMITTER logic for errors w/ lirc-mceusb
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lirc (Ubuntu) |
Fix Released
|
Wishlist
|
Mario Limonciello |
Bug Description
Binary package hint: lirc
<j-rod> do you know who maintains the lirc packages for ubuntu?
<superm1> it's a ~mythbuntu team effort to maintain them, but usually ends up being me when i find time
<j-rod> aha
<j-rod> can you *please* add some informative text in hardware.conf and/or whatever twiddles it to explain to users when they actually need that separate TRANSMITTER thing set?
<superm1> in what scenario?
<superm1> it's generally dynamically built
<j-rod> there's a disgustingly huge volume of questions about screwed up hardware.conf files, where people are setting up two lircd instances when a single one would do -- i.e., when using lirc_mceusb or lirc_zilog
<superm1> it's quite possible the logic is building it wrong
<j-rod> seems a lot of people are hand-editing it too
<superm1> well if that's the case, then yeah some comments in there will hopefully fix the problem for them
Changed in lirc (Ubuntu): | |
importance: | Undecided → Wishlist |
milestone: | none → ubuntu-10.04-beta-1 |
<j-rod> basically, just some text that says "only use the separate transmitter config stuff if your transmitter is a different piece of hardware with a different driver than your recevier"
<j-rod> would probably help a lot