Enabling the crash reporter for Lucid

Bug #623962 reported by Chris Coulson on 2010-08-25
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
firefox (Ubuntu)
Undecided
Unassigned
Lucid
Wishlist
Unassigned

Bug Description

Starting in Maverick, we now send Firefox crash reports directly to Mozilla, using the google-breakpad integration shipped with Firefox. I'd like to switch this on in Lucid for the next point release (scheduled for September 7th).

Unlike other packages in the archive where we aren't particularly interested in crash reports in the stable release (so we disable Apport), Mozilla rely on crash reporting as part of the feedback from testers of their point releases (which we ship). Enabling the crash reporter will hopefully help Mozilla catch regressions earlier, and avoid fire-drill releases like 3.6.8 which are a pain for us.

The change will go in to the staging PPA - ppa:ubuntu-mozilla-security/ppa (today hopefully, as we already have the first spin of 3.6.9). It will sit there for testing until the official release, as with all the other point releases.

The change is pretty low risk (building breakpad, turning on the signal handler in Firefox and shipping the crashreporter binary in the Firefox package).

The crash reporter can be tested with this extension: http://code.google.com/p/crashme/

affects: ubuntu → firefox (Ubuntu)
description: updated
description: updated
Changed in firefox (Ubuntu):
status: New → Invalid
Changed in firefox (Ubuntu Lucid):
status: New → Triaged
importance: Undecided → Wishlist
Martin Pitt (pitti) wrote :

Does that affect any build/compile options as well (like optimization, debug symbols, etc.), or is it merely building and shipping some additional code? Does it have a considerable impact on the package size?

If upstream actually wants us to enable this, then I see no reason to decline that, as long as it doesn't potentially cause regressions.

Chris Coulson (chrisccoulson) wrote :

Hi Martin,

It doesn't change any other build options (we just need to build with --enable-crashreporter) - it just enables the breakpad code, signal handler and the new crashreporter binary and associated support files. The existing debug symbols are unaffected by the change, but it does produce a new package (firefox-mozsymbols), which is purely to allow me to get access to the breakpad symbols and send them to Mozilla. The additional crashreporter binary is ~60kB, and additional support files are ~4kB

Chris Coulson (chrisccoulson) wrote :

The packaging changes are in lp:~mozillateam/firefox/firefox-3.6.lucid for anybody who is interested

Chris Coulson (chrisccoulson) wrote :

This is in the PPA now

Changed in firefox (Ubuntu Lucid):
status: Triaged → Fix Committed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package firefox - 3.6.9+build1+nobinonly-0ubuntu0.10.04.1

---------------
firefox (3.6.9+build1+nobinonly-0ubuntu0.10.04.1) lucid-security; urgency=low

  * New upstream release v3.6.9 (FIREFOX_3_6_9_BUILD1)
    - see USN-975-1

  * Add support for mozilla breakpad symbols and in turn enable
    crashreporter (LP: #623962)
    - update debian/control
    - update debian/rules
 -- Chris Coulson <email address hidden> Wed, 25 Aug 2010 16:20:35 +0100

Changed in firefox (Ubuntu Lucid):
status: Fix Committed → Fix Released
Brian Kemp (brian-kemp) wrote :

Does this mean "nobinonly" is a misnomer?

Chris Coulson (chrisccoulson) wrote :

No, it means that we cleaned the binary-only files that we can't redistribute from the tarball

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers