The file <tt>/home/olpc/.xsession-example</tt> contains other settings useful for debugging. You can copy individual lines from this or copy the entire file to <tt>/home/olpc/.xsession</tt>.
+
+
=== Presence service ===
+
If your bug involves the presence service, you might also want to follow the steps for [[BugSquad/TelepathyDebugging]].
== Where are the logs placed ==
== Where are the logs placed ==
Line 23:
Line 29:
* You may also use <code>olpc-netlog</code> to gather all logs and XO info into a single file.
* You may also use <code>olpc-netlog</code> to gather all logs and XO info into a single file.
* Log is an activity for viewing log files
* Log is an activity for viewing log files
−
−
=== Other debugging settings ===
−
The file <tt>/home/olpc/.xsession-example</tt> contains other settings useful for debugging. You can copy individual lines from this or copy the entire file to <tt>/home/olpc/.xsession</tt>.
−
−
=== Presence service ===
−
−
If your bug involves the presence service, you might also want to follow the steps for [[BugSquad/TelepathyDebugging]].
−
−
== If you can't reproduce the bug ==
−
−
Python-based activities automatically make logs in /home/olpc/.sugar/default/logs. These logs seem to be moved into subfolders on restart and deleted after a certain period of time. The python stack trace is recorded here on crashes. This is also a good thing to attach to a bug. As above, you will have to use the Terminal activity to copy them to removable memory (SD or USB) before using the XO or another computer to attach them to the bug.