After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 618901 - receivers.conf generation bugs
receivers.conf generation bugs
Status: RESOLVED FIXED
Product: gnome-lirc-properties
Classification: Other
Component: general
git master
Other Linux
: Normal normal
: ---
Assigned To: gnome-lirc-properties-maint
gnome-lirc-properties-maint
Depends on:
Blocks:
 
 
Reported: 2010-05-17 17:20 UTC by Bastien Nocera
Modified: 2010-05-20 18:45 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Bastien Nocera 2010-05-17 17:20:11 UTC
- lirc_mceusb2 doesn't exist any more
- add "compatible-remotes = " for devices we know
- lirc_atiusb is dead, we use the "atilibusb" lirc driver instead
- some remote definitions (their IDs) are duplicated, see:
"X10 Wireless Technology: Wireless Transceiver (ACPI-compliant)"
which breaks detection
Comment 1 Bastien Nocera 2010-05-19 16:16:40 UTC
For atilibusb and other devices for which we have user-space drivers, we need to extract the devices from the "static usb_device_id" tables in each of those.

Those are the ones:
gnome_lirc_properties/ui/RemoteControlProperties.py:        no_device_node = ('atilibusb', 'awlibusb', 'caraca', 'commandir', 'dfclibusb')

We should probably move this to a shared file.
Comment 2 Bastien Nocera 2010-05-20 18:45:09 UTC
(In reply to comment #0)
> - lirc_mceusb2 doesn't exist any more

Fixed.

> - add "compatible-remotes = " for devices we know

Not done yet

> - lirc_atiusb is dead, we use the "atilibusb" lirc driver instead

Added a hack to ignore the lirc_atiusb driver

> - some remote definitions (their IDs) are duplicated, see:
> "X10 Wireless Technology: Wireless Transceiver (ACPI-compliant)"
> which breaks detection

Fixed

(In reply to comment #1)
> For atilibusb and other devices for which we have user-space drivers, we need
> to extract the devices from the "static usb_device_id" tables in each of those.

Fixed