Package: inputlirc Version: 16-1 Severity: important Hello,
I have a Hauppauge remote which is driven by lircd. When inputlircd is
started after lircd, I cannot control clients anymore with this remote.
This is easily reproducible provided you have a lircd-driven device:
# /etc/init.d/lirc start
Loading LIRC modules:.
Starting remote control daemon(s) : LIRC :.
Starting remote control mouse daemon : LIRCMD :.
#
$ xawtv
---> At this point I can control xawtv via remote
$
# /etc/init.d/inputlirc start
Starting inputlirc
#
$ xawtv
---> At this point the remote doesn't affect xawtv anymore
$
# /etc/init.d/lirc restart
Stopping remote control mouse daemon: LIRCMD:.
Stopping remote control daemon(s): LIRC:.
Loading LIRC modules:.
Starting remote control daemon(s) : LIRC :.
Starting remote control mouse daemon : LIRCMD :.
#
$ xawtv
---> At this point I can control xawtv via remote again
$
It seems like once inputlircd is started, it inhibits lircd from
/dev/lircd, i.e. clients cannot connect to lircd anymore via /dev/lircd.
I assume, the same applies vice-versa, but cannot test it myself since I
have no multimedia-keyboard currently available on the machine where the
remote is connected to.
The usual Debian-way to handle this issue would be to conflict with the
lirc package. However, since the devices handled by lirc and inputlirc
are mutually exclusive, none of the packages is a true substitution for
the other and users can easily have a set of devices for which they need
both packages. Thus, a more co-operative solution would probably be
better.
Most likely this is something to forward upstream.
Thanks for your work & regards
Mario
--
It is practically impossible to teach good programming style to students
that have had prior exposure to BASIC: as potential programmers they are
mentally mutilated beyond hope of regeneration. -- Dijkstra
signature.asc
Description: Digital signature
