Update diagnosis script/runbook
Categories
(Toolkit :: Application Update, enhancement, P2)
Tracking
()
People
(Reporter: agashlin, Unassigned)
Details
(Whiteboard: [iu_tracking])
There are a few common pieces of data that we want to collect when we receive a report of an update issue, besides things like OS and Firefox version which are usually present:
- app.update log (file or console)
- updater log
- maintenance service log
- ...?
Often we have to provide basically the same instructions to the user for how to collect this, but I end up rewriting it every time, and may be overlooking or misstating steps.
It would be handy to have a document to copy from as a basis, or to just link to directly, with a form of this that can be improved over time. Not all of this is relevant to every issue, and the instructions may need to be tuned to the apparent expertise of the reporter, but commonly it will be the same. Having this in one place would also provide a menu of options to consider so that sources of data won't be overlooked.
This will make it easier to over-request, but that seems manageable. I don't know if this would belong in SUMO, on the mozwiki, or elsewhere. (Is there already something similar in SUMO?)
As starting points:
- app.update.log.file (though in retrospect collecting the update log would have been more helpful there)
- app.update.log and copy from console
- Maintenance service and update log (this should just say to use the Open Folder button for the Update Folder in about:support)
It may be out of scope for this to include broader support-style suggestions for how to fix the issue. There is a SUMO page for that, though it may need some more work.
Description
•