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 545516 - Add setup callout
Add setup callout
Status: RESOLVED WONTFIX
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: 2008-07-30 13:52 UTC by Bastien Nocera
Modified: 2018-02-15 14:08 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Bastien Nocera 2008-07-30 13:52:12 UTC
When a hot-pluggable receiver is plugged, a callout provided by gnome-lirc-properties should do a minimum of setup.

If I don't have any receiver/remotes configured, or they use stock configurations, I should be able to:
- plug in the receiver
- callout is called
- checks if the hardware that was plugged in has a remote supplied with it by default
- checks if lircd is running, whether the default configuration is customised compared to "factory" (LIRC-provided) settings
- write out a lircd.conf and lircd.conf.gnome suitable for use with that receiver and the default remote that comes with it

This means that for a large number of configurations (USB receiver, with a remote supplied) gnome-lirc-properties would require no configuration at all.
Comment 1 Bastien Nocera 2008-07-30 13:56:24 UTC
This should be quite straight-forward for somebody with the necessary hardware, and more Python skills than me. Marking as gnome-love.

You would need to modify backend.py to dump more information to the disk about the setup status, and use it to detect devices/remotes, and write out the new configuration to the disk.
Comment 2 Bastien Nocera 2010-05-15 13:58:25 UTC
Reassign to alias.
Comment 3 Bastien Nocera 2018-02-15 14:08:41 UTC
gnome-lirc-properties is obsolete and relies on outdated technology (HAL instead of udev). Most of the functionality is now integrated directly into the kernel, and Wayland has support for passing some keys up the stack to applications, that were ignored/dropped with X11.