Confirmed users
99
edits
CloudServices/Sync/File a desktop bug: Difference between revisions
Jump to navigation
Jump to search
CloudServices/Sync/File a desktop bug (view source)
Revision as of 23:00, 19 June 2018
, 19 June 2018Add how to capture logs from stdout
(Add section: Get detailed Sync logs) |
(Add how to capture logs from stdout) |
||
| Line 24: | Line 24: | ||
We’re hoping to automate much of this in upcoming versions of Firefox, so that a Sync problem can automatically be reported to us, or at least with just a few clicks. In the meantime, the [https://addons.mozilla.org/en-US/firefox/addon/about-sync/ about-sync addon] offers a facility for creating a .zip file with all your Sync logs which might be helpful. | We’re hoping to automate much of this in upcoming versions of Firefox, so that a Sync problem can automatically be reported to us, or at least with just a few clicks. In the meantime, the [https://addons.mozilla.org/en-US/firefox/addon/about-sync/ about-sync addon] offers a facility for creating a .zip file with all your Sync logs which might be helpful. | ||
=== Other/Advanced information === | |||
==== Capturing logs from stdout ==== | |||
In unusual cases, such as Firefox crashing during a sync, Firefox may not manage to save the logs to a file, so it may be necessary to grab logs from stdout. This is a fairly advanced operation, so please don't feel bad if you are unable to grab these logs. The steps you should follow are: | |||
* Use <code>about:config</code> to set the following properties: | |||
** <code>browser.dom.window.dump.enabled = true</code> | |||
** <code>services.sync.log.appender.dump = Trace</code> | |||
** <code>services.sync.log.logger.engine = Trace</code> | |||
** <code>services.sync.log.logger = Trace</code><br>Note that all the above preferences should already exist - they just have different default values. | |||
* Quit Firefox and ensure no other Firefox instances are running. | |||
* Determine where Firefox is installed on your system. On Mac's, it's probably in <code>/Applications/Firefox</code> and on Windows it's probably in <code>C:\Program Files\Mozilla Firefox</code> or similar. If you are running Linux, hopefully you already know how to locate this. | |||
* Open a "terminal/command prompt". On a Mac there's probably a terminal icon in your dock. On Windows, you should be able to find a <code>Command Prompt</code> icon in your start menu. | |||
* Execute the following command: | |||
** On Windows: <code>"c:\Program Files\Mozilla Firefox\Firefox.exe" -console 2>&1 > c:\temp\firefox-log.txt</code> | |||
** On Mac: <code>/Applications/Firefox.app/Contents/MacOS/firefox-bin 2>&1 > /tmp/firefox-log.txt</code><br>Note that in both cases you may need to adjust some paths accordingly - both the path to the binary and the path where you want the log file written. | |||
* Reproduce your problem, then exit Firefox. | |||
* The log file specified above (ie, <code>c:\temp\firefox-log.txt</code> or <code>/tmp/firefox-log.txt</code> in the above examples) should contain the log output. | |||
=== Credits === | |||
This page was unashamedly stolen from https://philikon.wordpress.com/2011/06/13/how-to-file-a-good-sync-bug/ - thanks to Philikon for his earlier work on Sync itself and for the initial version of this text. | This page was unashamedly stolen from https://philikon.wordpress.com/2011/06/13/how-to-file-a-good-sync-bug/ - thanks to Philikon for his earlier work on Sync itself and for the initial version of this text. | ||