Comment 1 for bug 982767

Edward,

The request was that people file new *crash* reports; i.e., to use the apport interface to report a new bug which would show us the crash. You write:

> I myself cannot reproduce it.

Which makes this bug report of dubious value.

> A number of users have tried to report the crash through apport, but the traceback has always been duped to bug 628104.

The last such duplicate was filed in May 2011. There have been no duplicate bugs reported since then.

In your first comment on bug #628104, you say:

> Apport just sent me here, from an apparent crash,

But how exactly did apport send you there? There is no bug pattern in place for bug #628104 and never has been. Nor did you file a new bug report and have it marked as a duplicate by the retracer. Did apport really send you there at all, or did you simply follow a link to that bug in your browser when offered as a "possibly similar" existing bug?

The only new bug report filed against update-manager or aptdaemon showing this crash is bug #976889, which was filed a week ago.

So I don't see any evidence that bug #628104 should be reopened, and this new bug report doesn't contain any actionable information.