support multiple crashdbs

Bug #957177 reported by Martin Pitt on 2012-03-16
This bug affects 6 people
Affects Status Importance Assigned to Milestone
apport (Ubuntu)
Martin Pitt
whoopsie (Ubuntu)

Bug Description

Right now Apport only supports sending reports to one crashdb.

With whoopsie we actually have two now, which we want to send reports to at the same time. whoopsie support is currently bolted on at the side, but it would be more elegant to create an actual whoopsie CrashDB backend, and then change /etc/apport/crashdb.conf to send to multiple DBs at the same time (e. g. launchpad+whoopsie during development, and just whoopsie post-release).

I just discussed the addition of a new "problem_types" CrashDB option with Evan, which is a list of "ProblemType" values this crashdb accepts. So e. g. after release, the launchpad DB could say "problem_types: ['Bug', 'Package']" if we don't want LP bug reports for crashes any more.

If we have that, could then check if any of the active CrashDBs takes that particular ProblemType, and present the report. If no crashdb takes it, it wouldn't show the report at all.

Martin Pitt (pitti) wrote :

To clarify, we need support for the problem_types option in Precise, to be able to selectively disable LP crash bugs. Support for multiple DBs and a whoopsie DB are fine for Ubuntu 12.10.

Changed in apport (Ubuntu):
status: New → Triaged
assignee: nobody → Martin Pitt (pitti)
importance: Undecided → Medium
Martin Pitt (pitti) wrote :

The part that's necessary for precise is tracked in bug 968121.

Following up from bug #1000945, if whoopsie isn't considered a direct dependency of apport, shouldn't the apport package at least have whoopsie in "Recommends"? It seems like apport doesn't actually do anything now without whoopsie being installed.

Martin Pitt (pitti) wrote :

Chris, it should be the other way round in my opinion: If you uninstall whoopsie because you don't want/can't use it, that should be possible. Apport should just not present/report crashes then (in released versions), but you should still be able to file bug reports to Launchpad with it (ubuntu-bug <packagename> or just "ubuntu-bug" for the symptoms).

Will whoopsie work without apport? If not, then it should have apport in "Depends". (It is not clear to me exactly what whoopsie does or how it works; there is no man page, and no relevant documentation in /usr/share/doc/whoopsie)

If either package benefits greatly from having the other installed, but it is not an absolute dependency, then the other package should be in "Recommends". That way the other package will be installed by default, but can be uninstalled if you want.

 affects ubuntu/whoopsie-daisy

Chris Bainbridge [2012-05-18 19:16 -0000]:
> Will whoopsie work without apport? If not, then it should have apport in
> "Depends".

I agree. Adding a whoopsie task.

Brian Murray (brian-murray) wrote :

I've tagged this rls-q-notfixing as it doesn't look like it will make the Quantal release.

tags: added: rls-q-notfixing
Evan (ev) on 2012-11-02
tags: added: whoopsie-daisy
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in whoopsie-daisy (Ubuntu Quantal):
status: New → Confirmed
Changed in whoopsie-daisy (Ubuntu):
status: New → Confirmed
Evan (ev) on 2012-11-28
no longer affects: whoopsie-daisy (Ubuntu)
no longer affects: whoopsie-daisy (Ubuntu Quantal)
no longer affects: apport (Ubuntu Quantal)
no longer affects: whoopsie (Ubuntu Quantal)
Changed in whoopsie (Ubuntu Raring):
status: New → Won't Fix
Changed in apport (Ubuntu Raring):
status: Triaged → Won't Fix
Changed in whoopsie (Ubuntu):
status: New → Confirmed
Martin Pitt (pitti) on 2014-07-30
Changed in apport (Ubuntu):
assignee: Martin Pitt (pitti) → nobody
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers