Open Bug 1401938 Opened 7 years ago Updated 2 years ago

Need a "submit all pending reports" button in Troubleshooting

Categories

(Thunderbird :: Mail Window Front End, enhancement)

enhancement

Tracking

(Not tracked)

UNCONFIRMED

People

(Reporter: luweitest, Unassigned)

References

Details

(Whiteboard: [notacrash])

Attachments

(1 file)

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:52.0) Gecko/20100101 Firefox/52.0 Build ID: 20170802111520 Steps to reproduce: I see lots of files in Application Data\Thunderbird\Crash Reports\pending, and want to send them. So I click Help->Troubleshooting information, click "All Crash Reports" under "Crash Reports" section. Actual results: TB did not respond. Expected results: TB should show all crash reports, including those failed to send, and let me send them manually.
(In reply to Lu Wei from comment #0) > User Agent: Mozilla/5.0 (Windows NT 5.1; rv:52.0) Gecko/20100101 Firefox/52.0 > Build ID: 20170802111520 > > Steps to reproduce: > > I see lots of files in Application Data\Thunderbird\Crash Reports\pending, Please post a screen shot of these files > and want to send them. So I click Help->Troubleshooting information, click > "All Crash Reports" under "Crash Reports" section. anything in tools > error console?
Component: Untriaged → Mail Window Front End
Flags: needinfo?(luweitest)
Whiteboard: [notacrash]
Attached image pending files
Flags: needinfo?(luweitest)
submit.log: [12/23/15 14:23:46] Crash report submission failed: An error occurred in the secure channel support [12/31/15 18:09:16] Crash report submission failed: An error occurred in the secure channel support [04/01/16 09:47:21] Crash report submission failed: The server name or address could not be resolved [04/06/16 14:37:20] Crash report submission failed: 操作成功完成。 [04/25/16 14:46:30] Crash report submitted successfully [07/08/16 14:06:56] Crash report submission failed: 操作成功完成。 [Fri Dec 9 09:10:26 2016] Crash report submitted successfully [Fri Dec 16 12:25:23 2016] Crash report submission failed: The connection with the server was reset [Wed Dec 21 09:17:45 2016] Crash report submitted successfully [Wed Dec 21 09:18:15 2016] Crash report submitted successfully [Wed Dec 21 09:19:58 2016] Crash report submitted successfully [Mon Mar 20 23:23:17 2017] Crash report submission failed: Unknown error, error code: 0x00002f19 [Sat Mar 25 18:20:16 2017] Crash report submitted successfully [Tue Apr 18 08:54:08 2017] Crash report submission failed: An error occurred in the secure channel support [Tue Aug 22 13:56:19 2017] Crash report submission failed: An error occurred in the secure channel support [Tue Aug 22 14:00:18 2017] Crash report submission failed: An error occurred in the secure channel support [Sun Sep 17 10:46:16 2017] Crash report submission failed: An error occurred in the secure channel support Error console after a TB restart: Webconsole context has changed JavaScript 1.6's for-each-in loops are deprecated; consider using ES6 for-of instead[Learn More] AutoProxy.js:213:8 Use of Mutation Events is deprecated. Use MutationObserver instead. calendar-widgets.xml:506:18 Direct3D 9 DeviceManager Initialized Successfully. Driver: igxprd32.dll Description: Mobile Intel(R) 965 Express Chipset Family Version: 6.14.10.5218 Couldn't find Asia/Beijing calTimezoneService.js:199:13 JavaScript 1.6's for-each-in loops are deprecated; consider using ES6 for-of instead[Learn More] browserWindow.js:78:6 TypeError: browser is undefined[Learn More] browserWindow.js:160:3 There has been an error reading data for calendar: occupation. However, this error is believed to be minor, so the program will attempt to continue. Error code: DAV_NOT_DAV. Description: The resource at http://localhost:2080/users/wei.lu@astronergy.com/calendar is either not a DAV collection or not available calCalendarManager.js:969:13 There has been an error reading data for calendar: occupation. However, this error is believed to be minor, so the program will attempt to continue. Error code: READ_FAILED. Description: calCalendarManager.js:969:13 [calCachedCalendar] replay action failed: null, uri=http://localhost:2080/users/wei.lu@astronergy.com/calendar, result=2147500037, operation=[xpconnect wrapped calIOperation] calCachedCalendar.js:330:29 Selector expected. Ruleset ignored due to bad selector. blank:39 Unexpected end of file while searching for closing } of invalid rule set. blank:41 Webconsole context has changed
After restart in safe mode, the link "All Crash Reports" works. I should have check the safe mode first. But there's still no button to let me send them again, only "remove all reports".
Summary: "All crash reports" link do not work → Can not send "Unsubmitted Crash Reports"
No button exists for submitting. You just click on each ID in the screen, like a web link. Not all old crashes will be accepted. If it is accepted, the ID will change to have a prefix of BP-
(In reply to Wayne Mery (:wsmwk, NI for questions) from comment #5) > No button exists for submitting. You just click on each ID in the screen, > like a web link. Not all old crashes will be accepted. If it is accepted, > the ID will change to have a prefix of BP- I wonder why there's no "submit them all" button. It is a huge design flaw in my view. Anyway I managed to click them all one by one. The most frequent crash recently is: ID: d4bf9868-68aa-4742-a011-b5cca0170926 Signature: shutdownhang | _PR_MD_WAIT_CV | _PR_WaitCondVar | But the related bug 1358564 seems irrelevant. TB is not saving email attachment when quitting and hanging. I can see lots of gpg.exe hanging as child process of thunderbird.exe. I suspect it is related to enigmail add-on or gpg.exe.
Summary: Can not send "Unsubmitted Crash Reports" → Need a "submit all pending reports" button
I'm not sure we'd do this - it would seem preferable to put manpower instead into fixing bugs that cause crashes to not be submitted.
Severity: normal → enhancement
Flags: needinfo?(richard.marti)
Summary: Need a "submit all pending reports" button → Need a "submit all pending reports" button in Troubleshooting
We use a copy of the Firefox about:support with some extensions which are needed for the message part. And we're not enough developers to implement this. If you can convince the FX developers, it would then be easy to port it to TB.
Flags: needinfo?(richard.marti)
(In reply to Wayne Mery (:wsmwk) from comment #7) > I'm not sure we'd do this - it would seem preferable to put manpower instead > into fixing bugs that cause crashes to not be submitted. I agree. I have submitted bug 1410103 to address this. But in order to debug, it is not efficient to wait TB or Fx crashing again. Is there someway to manually cause a test crash?
> Is there someway to manually cause a test crash? https://addons.mozilla.org/en-us/thunderbird/addon/nightly-tester-tools/
See Also: → tb-NoCrashReport, 1410103
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: