← Back to team overview

mythbuntu-bugs team mailing list archive

[Bug 204960] Re: [Hardy] Lirc devinput (linux-input-layer) broken

 

closing

** Changed in: lirc (Ubuntu)
       Status: Incomplete => Invalid

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

Title:
  [Hardy] Lirc devinput (linux-input-layer) broken

Status in lirc package in Ubuntu:
  Invalid

Bug description:
  Hardy Beta1. Clean install.

  I have an SAA7134-based board with a remote control that I've been
  using for long with LIRC, before hardy. Now it seems support for this
  type of devices is broken.

  This is the info:

  cat /proc/bus/input/devices

  I: Bus=0001 Vendor=185b Product=c100 Version=0001
  N: Name="saa7134 IR (Compro VideoMate TV"
  P: Phys=pci-0000:05:01.0/ir0
  S: Sysfs=/devices/pci0000:00/0000:00:1e.0/0000:05:01.0/input/input6
  U: Uniq=
  H: Handlers=kbd event6 
  B: EV=100003
  B: KEY=108c0222 211080100000000 0 0 19080006801 e168000000000 ffc

  
  You can see 
  My hardware.conf is attached. I'll also attach lircd.conf.
  I noticed that hardware.conf format has changed, and adapted my configuration accordingly.

  After reboot irw stays mute, it doesn't get any remote keypress.

  Doing /etc/init.d/lirc stop; and then launching lircd in non-daemon
  mode gives me (I'm connecting to lircd with irw):

  $ sudo lircd -n --driver=dev/input --device=/dev/input/event6
  lircd-0.8.3pre1[10361]: you should specify a valid gap value
  lircd-0.8.3pre1[10361]: lircd(userspace) ready
  lircd-0.8.3pre1[10361]: accepted new client on /dev/lircd
  lircd-0.8.3pre1[10361]: initializing '/dev/input/event6'
  lircd-0.8.3pre1[10361]: can't get exclusive access to events comming from `/dev/input/event6' interface

  Then, nothing happens. The terminal that is on focus will get numeric
  keys from the remote (because this is a linux-input-layer type
  device), which also happened in gutsy. But in gutsy, lircd trapped
  those events and processed them, and sent them to the connected lirc
  clients (e.g. irw).

  BTW, those number keypresses I get in the terminals demonstrate that
  my hardware and the remote are fine, and also that the kernel module
  looks good as well.

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