Unfortunately, the actual crash happens somewhere in Avahi or D-Bus and the stacktraces do not show through which part of CUPS the crashing piece of code was reached. Probably it is in a thread started by Avahi. So it is far from simple to find the place in CUPS where an additional NULL check is needed (this would be the real fix).
Therefore and keeping in mind that the CUPS broadcasting/browsing patch will go away in Raring, I suggest the general blocking of cupsd crash reports via /etc/apport/blacklist.d/cups. In addition, CUPS was very stable all the time, so the chance of other crashes to happen is rather low. So I think we can take the risk. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1086019 Title: cupsd crashes regularly (daily) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1086019/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
