3,267
edits
Changes
no edit summary
If you provide debugging logs to a ticket, you'll be making it much easier to developers to fix the issue. In most of the cases it will be easiest for you to reproduce the bug.
If you provide debugging logs to a ticket, you'll be making it much easier to developers to fix the issue. In most of the cases it will be easiest for you to reproduce the bug.
== Enabling debugging ==
== Enabling Sugar debug logging ==
In the latest 0.83 development releases (that will lead to 0.84) we created the file ~/.sugar/debug All the logging options are uncommented by default. Just remove the '#' before the line 'export SUGAR_LOGGER_LEVEL=debug' to enable Sugar debug logging.
=== On the XO ===
=== Where are the logs placed ===
* Perform the minimal steps to reproduce the bug.
* The relevant logs are in '''~/.sugar/default/logs''', (e.g org.laptop.WebActivity-1.log for the log of the first Browse instance).
=== Using the sugar-emulator ===
If you are using a version older than the latest development release (0.83) run the emulator with the following command:
SUGAR_LOGGER_LEVEL=debug sugar-emulator
=== Presence service ===
If your bug involves the presence service, you might also want to follow the steps for [[BugSquad/TelepathyDebugging]].
== On the XO (using Sugar 0.82.x)==
These are general steps to follow when providing logs for some bug:
These are general steps to follow when providing logs for some bug:
The file <tt>~/.xsession-example</tt> contains other settings useful for debugging. You can copy individual lines from this or copy the entire file to <tt>~/.xsession</tt>.
The file <tt>~/.xsession-example</tt> contains other settings useful for debugging. You can copy individual lines from this or copy the entire file to <tt>~/.xsession</tt>.
[[category:BugSquad]]
[[category:BugSquad]]