One more comment, from my syslog:
Nov 25 21:35:26 compy lircd-0.8.3[8067]: lircd(userspace) ready
Nov 25 21:36:16 compy lircd-0.8.3[8067]: caught signal
Nov 25 21:36:16 compy lircd-0.8.3[8118]: error in configfile line 16:
Nov 25 21:36:16 compy lircd-0.8.3[8118]: "2147483648": must be a valid (lir
I put the wrong URL for the defect I think might be related. The proper
URL is https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/275549.
--
lircd segfaults on startup with large codes in lircd.conf
https://bugs.launchpad.net/bugs/302266
You received this bug notification because you are a memb
Public bug reported:
Binary package hint: lirc
(This might be related to
https://bugs.launchpad.net/mythbuntu/+bug/50)
The Hauppauge PVR-150 raw codes can be quite large. It appears that if
you have a code in your lircd.conf file that is >= 2^31, you will get a
segfault starting lircd. The
As I struggled with this, I found this thread that got me around it.
There is a bug somewhere in here, I'm sure...
http://ubuntuforums.org/showthread.php?p=6110256#post6110256
tj
--
hauppauge pvr-150 ir blaster cannot use standard lircd.conf definitions for
cable box
https://bugs.launchpad.net
** Attachment added: "kernelinfo.tar.bz2"
http://launchpadlibrarian.net/9943419/kernelinfo.tar.bz2
--
Resume after suspend to disk or suspend to ram fails
https://bugs.launchpad.net/bugs/151471
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contac
Public bug reported:
Binary package hint: linux-source-2.6.22
I am seeing what looks like the same behavior on my Latitude D820 with
Gutsy. Note that my laptop has an nvidia graphics card and I am using
the restricted nvidia new driver.
Linux nefarian 2.6.22-14-generic #1 SMP Wed Oct 10 06:00:4
