*** This bug is a duplicate of bug 204960 ***
https://bugs.launchpad.net/bugs/204960
** This bug has been marked a duplicate of bug 204960
[Hardy] Lirc devinput (linux-input-layer) broken
--
Very common infrared remotes not registered
https://bugs.launchpad.net/bugs/322483
You received th
I just upgraded to Jaunty J amd64 and noticed this file
[00:57][claudiu:/>~]$ cat /usr/share/hal/fdi/preprobe/20thirdparty/lirc.fdi
true
true
true
true
Does this mean it is fixed in Ubuntu 9.04 ? Can you con
I can't tell, but I think this file should give all the info we need...
I has the remote key codes - ALL WORKING AND TESTED.
I would like to stress the fact that this is a more general problem, as
the bug title says! So its not about a stupid Winfast remote, but its a
real need to include in the u
Do the other keys not produce any input event at all (in input-events),
or are they just >= 256, so that X.org cannot use them?
--
Very common infrared remotes not registered
https://bugs.launchpad.net/bugs/322483
You received this bug notification because you are a member of Ubuntu
Bugs, which i
If theyre planning to have evdev work with IR remotes, they will have to
collect lots of remote specs. Maybe the HardwareTesting info collector
in System->Administration could include scanning for IRremotes keycodes.
Anywas, for the time, evdev should IGNORE the remotes, as long as its
not capable
Thanks. Currently discussing with upstream where this file should be
placed best; I'm currently leaning towards lirc, thus tentatively
reassinging this. I'll wait a couple of days for comments, and then
apply it.
http://lists.freedesktop.org/archives/hal/2009-February/012977.html
** Changed in: l
Here it is...
Cheers,
** Attachment added: "hal.txt"
http://launchpadlibrarian.net/22512198/hal.txt
--
Very common infrared remotes not registered
https://bugs.launchpad.net/bugs/322483
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
Ah, thanks. Can you please do
lshal > /tmp/hal.txt
and attach it here?
--
Very common infrared remotes not registered
https://bugs.launchpad.net/bugs/322483
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
It seems that the ignore rule makes the hal system IGNORE the infrared
remote, so that lirc can register the remote.
Without this rule, the computer thinks my remote is a keyboard, reading only
the Enter key and the digits. So, basicly, the rule says something like
"this is a IR remote, m.f., leave
Can you please explain how setting info.ignore makes it work, and why?
How does that device appear in lshal if you arne't using those rules?
** Changed in: hal-info (Ubuntu)
Status: New => Incomplete
--
Very common infrared remotes not registered
https://bugs.launchpad.net/bugs/322483
You
** Attachment added: "lirc.fdi"
http://launchpadlibrarian.net/21729146/lirc.fdi
--
Very common infrared remotes not registered
https://bugs.launchpad.net/bugs/322483
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
11 matches
Mail list logo
