[Expired for lirc (Ubuntu) because there has been no activity for 60
days.]

** Changed in: lirc (Ubuntu)
       Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/993202

Title:
  lircd crashing on boot in precise.  Can be restarted and then stays up

Status in lirc package in Ubuntu:
  Expired

Bug description:
  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:~$

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/993202/+subscriptions

_______________________________________________
Mailing list: https://launchpad.net/~mythbuntu-bugs
Post to     : mythbuntu-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mythbuntu-bugs
More help   : https://help.launchpad.net/ListHelp

Reply via email to