mythbuntu-bugs team mailing list archive

[Launchpad Bug Tracker <697999@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package lirc - 0.9.0-0ubuntu5

---------------
lirc (0.9.0-0ubuntu5) trusty; urgency=medium

  * debian/lirc.postinst, debian/lirc.templates, debian/po: drop a number of
    debconf templates that are no longer being prompted for at all due to
    the dropping of the lirc-modules-source package and the lirc.config some
    time ago.
  * debian/lirc.postinst: clean up the remaining debconf handling to not
    override settings in /etc/lirc/hardware.conf.
  * debian/lirc.postinst: drop code for removing /var/log/lircd, which has
    been gone for more than a decade.
  * fix blacklist handling, which creates files not used by modprobe, and
    doesn't put all the contents in a single file.
  * drop obsolete Ubuntu migration code that dates from jaunty and lucid.
  * fix a bug that causes transmitter device/driver settings to always be
    cleared on config change.
  * Adjust lircd handling for multiple devices so that events for all of
    them will appear on /dev/lircd as intended.  Thanks to Joel Ebel for
    the patch.  LP: #697999.
  * Use /run/lirc, the canonical name for /var/run/lirc.  LP: #474701.
  * Fix the init script to not report failures when stopping an
    already-stopped daemon.
 -- Steve Langasek <steve.langasek@xxxxxxxxxx>   Sun, 16 Mar 2014 05:35:47 -0700

** Changed in: lirc (Ubuntu)
       Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/697999

Title:
  lirc init script seems to load things backwards

Status in “lirc” package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: lirc

  The lirc manual describes how to load multiple devices here:
  http://www.lirc.org/html/configure.html#multiple

  Assuming that the primary device get started on lircd and the
  secondary device gets started on lircd1:

  In short the proper method is to start lircd1 with --listen, and then
  lircd with --connect

  The lircd init script does this backwards, lircd with --listen, and
  then lircd1 with --connect.

  The result is that only the primary device is visible on lircd.  Both
  devices are visible on lircd1, however, most applications will require
  additional configuration in order to communicate with both devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/697999/+subscriptions