Here are two scenarios: 1. Remote: Streamzap 2. Transmitter: Serial IR Blaster 3. debconf defaults
TRANSMITTER_DEVICE and REMOTE_DEVICE are not set. Because TRANSMITTER_DEVICE is not set, the lircd does not load for the transmitter. 1. Remote: Streamzap 2. Transmitter: Serial IR Blaster 3. debconf defaults + manually set TRANSMITTER_DEVICE to /dev/lirc1 (since it is loaded 2nd) Since TRANSMITTER_DEVICE is now set, lirc init script refuses to "guess" the REMOTE_DEVICE. First instance of lircd is not loaded. Since REMOTE_DEVICE is not set, lircd for transmitter device refuses to load. Needed changes to debconf logic: 1. Always set TRANSMITTER_DEVICE since we never try to guess. 2a. Always set REMOTE_DEVICE and remove "guess" logic from lirc init script. 2b. Only set REMOTE_DEVICE when TRANSMITTER_DEVICE is set. This should allow both instances of lircd to start. On Mon, Mar 24, 2008 at 2:18 AM, Mario Limonciello <[EMAIL PROTECTED]> wrote: > I prefer the solution here to be debconf. There is some logic already > in place for how this happens, but it clearly isn't complete. Would you > mind posting an example that you are running into difficulties with this > in it's current state? Or is this more of a hypothetical just looking > to fix problems before they arise sort of thing? > > ** Changed in: lirc (Ubuntu) > Status: New => Incomplete > > -- > /etc/init.d/lirc requires TRANSMITTER_DEVICE to be set in hardware.conf > https://bugs.launchpad.net/bugs/204769 > You received this bug notification because you are a direct subscriber > of the bug. > -- Andrew Barbaccia MonolithMC Sales & Support (631) 865 - 1025 -- /etc/init.d/lirc requires TRANSMITTER_DEVICE to be set in hardware.conf https://bugs.launchpad.net/bugs/204769 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
