Confirmed users
360
edits
Gaia/Email/RequiredBugInfo: Difference between revisions
Jump to navigation
Jump to search
no edit summary
(cleanup to make things more bold so things are hopefully more readable) |
No edit summary |
||
| Line 15: | Line 15: | ||
; A log of what was happening around the time the problem happened: This can take the form of the GeckoDump logcat category or a log generated by the secret debug mechanism. | ; A log of what was happening around the time the problem happened: This can take the form of the GeckoDump logcat category or a log generated by the secret debug mechanism. | ||
* logcat log of what the e-mail app was doing: | * logcat log of what the e-mail app was doing: | ||
** | ** Make sure that e-mail logging is enabled. It probably is. If you are running logcat and see "LOG: Mail universe/bridge created, notifying", then it's working! Congrats! Otherwise, to turn it on: | ||
*** You can enable the preference in your own gaia builds by creating a file GAIA/build/custom-prefs.js (note: this used to be GAIA/custom-prefs.js, but it changed) and making sure it includes the line: pref("browser.dom.window.dump.enabled", true); | *** You can enable the preference in your own gaia builds by creating a file GAIA/build/custom-prefs.js (note: this used to be GAIA/custom-prefs.js, but it changed) and making sure it includes the line: pref("browser.dom.window.dump.enabled", true); | ||
*** I hope there's a better way, but if not, if you just want to change the setting on the device, you will need to modify /data/b2g/mozilla/PROFILEDIR/prefs.js to include the line. See below for one way to do this. | *** I hope there's a better way, but if not, if you just want to change the setting on the device, you will need to modify /data/b2g/mozilla/PROFILEDIR/prefs.js to include the line. See below for one way to do this. | ||
*** Please provide the logcat by running '''adb logcat -v time -s GeckoDump:V Gecko:V | tee FILENAME-TO-LOG-TO'''. Please start running this command BEFORE you attempt to reproduce the problem. logcat uses a circular buffer that discards older entries when the buffer fills up, so if you run logcat only after the problem happens, you may not have all of the logic. Once you are done, hit control-C and send us the file. | ** Second: make sure the logcat stays connected even when the screen locks / the display turns off. You have to have both "remote debugging" enabled (which is what makes logcat work at all), and you need to disable the lock screen in order for logcat to remain connected. There are other ways to make this happen, but they are technical and I don't know them. Feel free to include instructions here. | ||
** Please provide the logcat by running '''adb logcat -v time -s GeckoDump:V Gecko:V | tee FILENAME-TO-LOG-TO'''. Please start running this command BEFORE you attempt to reproduce the problem. logcat uses a circular buffer that discards older entries when the buffer fills up, so if you run logcat only after the problem happens, you may not have all of the logic. Once you are done, hit control-C and send us the file. | |||
**** The logcat arguments filter out a lot of the noise that we don't care about and gives us timestamps. | **** The logcat arguments filter out a lot of the noise that we don't care about and gives us timestamps. | ||
**** The "tee" command lets you see the output while also logging the output directly to a file. This way you don't have to copy and paste the log. | **** The "tee" command lets you see the output while also logging the output directly to a file. This way you don't have to copy and paste the log. | ||