Attaching Sugar logs to tickets: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
No edit summary
Line 12: Line 12:
* '''The relevant logs are in /home/olpc/.sugar/default/logs''', copy them to an usb stick and attach to the ticket from some other computer.
* '''The relevant logs are in /home/olpc/.sugar/default/logs''', copy them to an usb stick and attach to the ticket from some other computer.
* Another interesting file to attach to the ticket is /var/log/messages.
* Another interesting file to attach to the ticket is /var/log/messages.
* You may also use <code>olpc-netlog</code> to gather all logs and XO info to a single file.


If your bug involves the presence service, you might also want to follow the [[Telepathy-debug|steps outlined for debugging Telepathy]].
If your bug involves the presence service, you might also want to follow the [[Telepathy-debug|steps outlined for debugging Telepathy]].

Revision as of 01:18, 25 January 2008

If you provide debugging logs to a ticket, you'll be making it much easier to developers to fix the issue.

These are general steps to follow when providing logs for some bug:

  • Open the terminal activity.
  • Type the following:
echo 'export SUGAR_LOGGER_LEVEL=debug' >> /home/olpc/.xsession
  • Reboot
  • Do the minimal steps to reproduce the bug.
  • The relevant logs are in /home/olpc/.sugar/default/logs, copy them to an usb stick and attach to the ticket from some other computer.
  • Another interesting file to attach to the ticket is /var/log/messages.
  • You may also use olpc-netlog to gather all logs and XO info to a single file.

If your bug involves the presence service, you might also want to follow the steps outlined for debugging Telepathy.

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 a removable memory (SD or USB) before using the XO or another computer to attach them to the bug.