Oops page should explain what is done with the report

I do not think this is necessary. The OOPSes for each environment are classified, sorted, and reported every 24 hours. The report is read by 30 engineers and bugs are reported based on the context and frequency. The QA engineers review the history of all oops to identify problems that are not visible in the daily and weekly reports.

Bugs reported by users will be duplicates of the bugs that the engineers are already reporting.

There may be value in us getting the report directly from the user, describing what they where doing, etc.
We would need to get a good mechanism for oops dupe detection, but this may be better than us trying to guess.

I agree with Martin (obviously).
A bug which does not allow bug reporting at all (bug 500856) has not been fixed since over half a month, I've heard on IRC that "we're getting OOPses a lot lately" and some such.

This is unacceptable and does not get fixed by not allowing users to report the problem easily!

What is required to mark the bug as "complete" now?

btw: you might want to improve on the report/review process if such things are being unfixed for such a long time!

In this specific case, the bug was a duplicate that gmb is working on. It is the dominate bug in the oops reports in fact. When an oops is obscure, we contact the user (yes we do know who did, what browser was used and how the person got there).

We mad a consious decision to to not not allow users to report these bugs because when the do, we do not collect informaiton that helps us close the bug. Again consider the bug that was trying to be reported, it is an Ubuntu bug that the Ubuntu community want the user to report using Ubuntu rather than direcly in Launchpad because they need better information.

> Again consider the bug that was trying to be reported, it
> is an Ubuntu bug that the Ubuntu community want the user to report using
> Ubuntu rather than direcly in Launchpad because they need better
> information.

Well, I'm the maintainer of this source package (to be still included) and
wanted to create a bug report for maintenance and linking it with the upstream
bug report.
It failed.
Using "ubuntu-bug tvbrowser" also fails: "no real ubuntu package"

Apart from that, I think it's very frustrating for users to just see the OOPS
page, having the browser history/user input destroyed/removed and no hint
about what to do next.

Every OOPS hitter is a possible Launchpad hater, you really should lend them a
hand!
Just imagine you having registered an account on Launchpad to report a
particular (maybe even minor) issue, trying to help something better. Then you
hit a major bug like this..!
Why aren't there regression tests in place which prevent f*ckups like this?

--
http://daniel.hahler.de/

This sounds like issue a communication Issue. The page could explain what will happen with the captured information.
The process that agregates the oopses is not real-time so there is not enough information at the time of the OOPs to show which bug it relates to.

We are near realtime now, but there is no guarantee for a given oops that there will be a bug existing etc. That said, more prose would likely be useful.