BugSquad/Get Logs

What are the logs useful for

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 Sugar debug logging

In the latest 0.83 development releases (that will lead to 0.84) we created the file text file ~/.sugar/debug which gets read at sugar startup. All the logging options are commented by default. Use your editor of choice and remove the '#' before the line 'export SUGAR_LOGGER_LEVEL=debug' to enable Sugar debug logging.

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/Telepathy Debugging.

On the XO (using Sugar 0.82.x)

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

• Start the Terminal activity.
• Type the following:

 echo 'export SUGAR_LOGGER_LEVEL=debug' >> /home/olpc/.xsession

• Reboot, or just restart X using ctrl+alt+erase

The file ~/.xsession-example contains other settings useful for debugging. You can copy individual lines from this or copy the entire file to ~/.xsession.

On other machines (Sugar.84)

Sugar activities have logs

~/.sugar/default/logs/  

so go to

someuser

type

 ls -al 

then drill down to

 ~/.sugar/default/logs/

for the error messages.

Another useful command is:

dmesg 

It prints out all of the kernel's messages and warnings for this session, with any new stuff at the end.