/etc/init.d/lirc broken when both REMOTE and TRANSMITTER are defined
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lirc (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Binary package hint: lirc
The patch is small.. I had to move the renaming of the TRANSMITTER_SOCKET variable into the if block that defines the default value. This is the proper behavior anyway, since if the user has defined a value for TRANSMITTER_SOCKET we shouldn't be touching it.
--- /etc/init.d/lirc 2009-10-17 06:06:53.000000000 -0400
+++ lirc 2009-11-05 12:49:36.700779791 -0500
@@ -80,7 +80,6 @@
#To make the second lircd connect
if [ ! -z "$REMOTE_DEVICE" ] || [ ! -z "$REMOTE_DRIVER" ]; then
- TRANSMITTER_
fi
@@ -129,6 +128,11 @@
fi
if [ -z "$TRANSMITTER_
+ #Now, if we ALSO have a remote defined,
+ #change the default transmitter socket
+ if [ ! -z "$REMOTE_DEVICE" ] || [ ! -z "$REMOTE_DRIVER" ]; then
+ TRANSMITTER_
+ fi
fi
case "$1" in
Related branches
Changed in lirc (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in lirc (Ubuntu): | |
status: | Triaged → Fix Committed |
Jeremy Yoder, could you check upstream and see if this has already been addressed, and if not, submit it? Thanks!