Ubuntu logo


Continued development of the Ubuntu error tracker

2012-05-10 17:05..18:00 in Jr. Ballroom 1

Integration with a hardware database. Pig or Hive (Hadoop) support. Backporting the reporting client (whoopsie) to previous Ubuntu versions. Discuss the state of Upstart's inotify event support. Further changes to the statistics website. API requirements. Sort out our story on mean time between failures (http://paste.ubuntu.com/957235/, http://instagr.am/p/KDe4WPhRxl). Additional problem types (desktop application hangs, package installation failures, debconf dialogs during package installation, ...) Providing an apport API for applications handling recoverable errors. Surfacing architecture (and other data points) only when relevant Should we continue to process and retrace crashes from derivatives? Can we set /proc/sys/fs/suid/dumpable to 2? (programs not normally dumped are dumped, but only readable by root). We need some way of ensuring we never ever send cores from ssh-agent, among others. ...

Other crash database blueprints: https://blueprints.launchpad.net/ubuntu/+spec/foundations-q-crash-database-2 https://blueprints.launchpad.net/ubuntu/+spec/foundations-q-metrics https://blueprints.launchpad.net/ubuntu/+spec/foundations-q-updates-from-crash-reports https://blueprints.launchpad.net/ubuntu/+spec/foundations-q-fix-ddebs https://blueprints.launchpad.net/ubuntu/+spec/foundations-q-bucketing-improvements https://blueprints.launchpad.net/ubuntu/+spec/foundations-q-phased-updates

Additional background information: http://paste.ubuntu.com/958213/

Specification (read this first): http://wiki.ubuntu.com/ErrorTracker