On my fresh install of Precise Ubuntu, I am suffering an lircd crash on boot. This occurs most boots and apport has sent a few error reports in, but I didn't see an official bug open yet. I am using a usbuirt receiver. Judging by the SegvAnalysis, it looks like a null pointer deference.
Some interesting information is that once the system is booted, I can restart lircd using '/etc/init.d/lircd restart' and the daemon starts and stays stable (up for days no new crashes). This makes me suspicious that this could be an initialization race where the driver is trying to access something that is not yet available or initialized during the boot strip.
I am attaching the crash report along with an included file that contains button signal definitions that is referenced in my lircd.conf file.
jheck@twilightzone:~$ lsb_release -rd
Description: Ubuntu 12.04 LTS
Release: 12.04
jheck@twilightzone:~$ apt-cache policy lirc
lirc:
Installed: 0.9.0-0ubuntu1
Candidate: 0.9.0-0ubuntu1
Version table:
*** 0.9.0-0ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
100 /var/lib/dpkg/status
jheck@twilightzone:~$
I'm wondering if more information is needed. If someone can point me to some detailed instructions on how to compile the offending driver with symbols for Ubuntu, to provide a more meaningful stack trace I'd be happy to try. This bug is causing me grief one out every two boots.
Also, although I have only seen it twice, I have experienced a system lockup long after boot, where I'm pretty sure an LIRC bug trace was generated on reboot. This may or may not be the same problem, as the LIRC crash could have just been sitting there from the initial boot, and just got reported on the reboot.