Closed
Bug 269136
Opened 20 years ago
Closed 20 years ago
Everytime I start Firefox, the quality feedback agent sends a crash report to Mozilla.org
Categories
(Firefox :: General, defect)
Tracking
()
VERIFIED
INVALID
People
(Reporter: debailey, Assigned: bugzilla)
Details
Attachments
(1 file)
|
75.26 KB,
text/plain
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 When I start Firefox a box appears from the quality feedback agent saying it's sending a crash report to Mozilla.org. This box should only come if FireFox fails not everytime at bootup Reproducible: Always Steps to Reproduce: 1. Click FireFox Icon on Desktop 2. When booting up a box will pop up just before FireFox opens 3. Box will send something to Mozilla.org Actual Results: I was able to reproduce the problem Expected Results: The box should only show when FireFox crashes not everytime at bootup. Specs: Athlon XP 2100+ 512MB DDR 400MHZ Ram Geforce FX 5200 Video Card
If the report could not be sent, TB retries on every startup. Look in TB if some incidents have status "queued".
Comment 2•20 years ago
|
||
I think this bug can be set to INVALID.
Comment 4•20 years ago
|
||
This is the details file from the Quality Feedback Agent.
Comment 5•20 years ago
|
||
Comment 1 is correct. If you have unsent incidents in the talkback agent, it will pop up next time you run Firefox. If you don't want to use it, disable it (in talkback window). Otherwise, bear with it. It always was like that and I don't think it's going to change. Marking invalid. Now if Firefox actually crashes each startup, it's a different bug, try reproducing it with latest trunk builds, and file it, noting incident IDs you get from talkback. A workaround is to create a new profile and/or reinstall Firefox.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
Updated•19 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•