may loose keyboard input

Bug #221177 reported by Patrice DUROUX
4
Affects Status Importance Assigned to Milestone
gnome-lirc-properties (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Binary package hint: gnome-lirc-properties

Hy,

I have 2 BTC USB Multimedia Cordless Kit:
1 for cordless keyboard and mouse (/dev/input/event2)
1 for an IRC (/dev/input/event3)

Using the gnome-lirc-properties and the auto-detect, it sets the (IRC) Device to /dev/input/event2 without being
possible to change it and then my keyboard input is no more working.

Regards,
Patrice.

Revision history for this message
Patrice DUROUX (patrice-duroux) wrote :
Revision history for this message
Mathias Hasselmann (hasselmm) wrote :

AFAIK the Linux input device system doesn't provide sufficient information to distinguish between keyboards, mouses and IR receivers. For that reason g-l-p checks the human readable name of such devices to filter out keyboards during auto detection. Can you attach the contents of your /proc/bus/input/devices file (with all those devices attached)? Need this file to decide how to filter out the keyboard.

I also wonder why the device selection dialog doesn't show up during auto-detection, as you seem to have two input devices attached.

Revision history for this message
Patrice DUROUX (patrice-duroux) wrote :

Sorry, but I was wrong on the situation that is given by the attached devices.txt
In fact I have only 1 BTC USB Multimedia Cordless Kit with 2 possible cordless devices
(keyboard and mouse) but only the keyboard is connected, as I otherwise use an USB
cord mouse.
Also the lirc_mceusb2 module is correctly loaded but the "Philips eHome USB IR Transciever and
Microsoft MCE 2005 Remote Control driver for LIRC" used to connect my IRC does NOT appear as
an Linux Input Device (wrong?), it creates a /dev/lirc0.
Then, how to proceed with the gnome-lirc-properties?

Revision history for this message
Mathias Hasselmann (hasselmm) wrote :

Patrice, thanks for that information. I finally figured out how to retrieve the list of supported keys for an input device, so I commited this change: http://svn.gnome.org/viewvc/gnome-lirc-properties?view=revision&revision=31

> Use better method for filtering out keyboards during auto-detection.
> Currently just the device name is checked to contain the sub-string
> "keyboard". Now each input device with at least 85 keys is considered
> a keyboard. Should fix LP#221177.

Your USB IR Transciever is not listed as Linux Input device since lirc_mceusb2 only implements the LIRC interface, but not the Linux Input Device interface.

Changed in gnome-lirc-properties:
status: New → Fix Committed
Changed in gnome-lirc-properties:
importance: Undecided → Low
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gnome-lirc-properties - 0.2.7-0ubuntu1

---------------
gnome-lirc-properties (0.2.7-0ubuntu1) intrepid; urgency=low

  * New upstream version (LP: #218691)
    - Fix crash with ValueError in __init__() (LP: #226745)
    - Fix crash with error in io() (LP: #224954)
    - Better method for filtering type of IR device (LP: #221177)
  * debian/rules
    - removal of rmdir of the locale dir, since it is not empty anymore.
    - clean up of help/gnome-lirc-properties.pot
  * Bump to Standard-Version 3.8.0
  * debian/copyright:
    - corrected the location of the GPL-2
    - Addition of the copyright of Openismus GmbH

 -- Christophe Sauthier <email address hidden> Mon, 11 Aug 2008 14:42:36 +0200

Changed in gnome-lirc-properties:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.