← Back to team overview

mythbuntu-bugs team mailing list archive

[Bug 786742] [NEW] MCEUSB remote configuration can fail with multiple lirc devices

 

Public bug reported:

Binary package hint: lirc

The Mythbuntu Control Centre MCE USB remote configuration failed because
I had another lirc device attached to the computer. The first lirc
device came up as /dev/lirc0 and the MCE USB remote control as
/dev/lirc1. The MCC seems to assume that when configuring the MCE USB
remote control that it will be /dev/lirc0. Therefore, the MCE USB
configuration didn't work out of the box for me (the issue was easily
fixed by modifying the value of REMOTE_DEVICE in
/etc/lirc/hardware.conf). If it were possible to determine what type of
remote each /dev/lirc* corresponds to, then the configuration logic
could perhaps do a better job of assigning /dev/lirc* to REMOTE_DEVICE?

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: lirc 0.8.6-0ubuntu4.2 [modified: usr/share/lirc/remotes/imon/lircd.conf.imon-knob]
ProcVersionSignature: Ubuntu 2.6.32-28.55-generic 2.6.32.27+drm33.12
Uname: Linux 2.6.32-28-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Mon May 23 01:01:17 2011
InstallationMedia: Mythbuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1)
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: lirc

** Affects: lirc (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug lucid

-- 
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/786742

Title:
  MCEUSB remote configuration can fail with multiple lirc devices

Status in “lirc” package in Ubuntu:
  New

Bug description:
  Binary package hint: lirc

  The Mythbuntu Control Centre MCE USB remote configuration failed
  because I had another lirc device attached to the computer. The first
  lirc device came up as /dev/lirc0 and the MCE USB remote control as
  /dev/lirc1. The MCC seems to assume that when configuring the MCE USB
  remote control that it will be /dev/lirc0. Therefore, the MCE USB
  configuration didn't work out of the box for me (the issue was easily
  fixed by modifying the value of REMOTE_DEVICE in
  /etc/lirc/hardware.conf). If it were possible to determine what type
  of remote each /dev/lirc* corresponds to, then the configuration logic
  could perhaps do a better job of assigning /dev/lirc* to
  REMOTE_DEVICE?

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: lirc 0.8.6-0ubuntu4.2 [modified: usr/share/lirc/remotes/imon/lircd.conf.imon-knob]
  ProcVersionSignature: Ubuntu 2.6.32-28.55-generic 2.6.32.27+drm33.12
  Uname: Linux 2.6.32-28-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Mon May 23 01:01:17 2011
  InstallationMedia: Mythbuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1)
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lirc


Follow ups

References