Reporting bugs: Difference between revisions
mNo edit summary |
(→Harder but more helpful: Trac: fix links, replace text with link to How to check the OS and firmware versions) |
||
| Line 9: | Line 9: | ||
== Harder but more helpful: Trac == |
== Harder but more helpful: Trac == |
||
The harder-but-more-helpful way: First search the [[ |
The harder-but-more-helpful way: First search the [[Trac]] bug database at http://dev.laptop.org/query to see if the bug has already been reported. If it has not, register yourself on that site and submit the bug. Some useful hints: |
||
* The only fields you have to fill out are '''summary''', '''description''', '''type''' (''defect'' if it does the wrong thing, ''enhancement'' if it doesn't let you try to do a thing), and '''component'''. If you want to, you can put yourself in the cc field. We'll do the rest. |
* The only fields you have to fill out are '''summary''', '''description''', '''type''' (''defect'' if it does the wrong thing, ''enhancement'' if it doesn't let you try to do a thing), and '''component'''. If you want to, you can put yourself in the cc field. We'll do the rest. |
||
* |
* Follow [[How to check the OS and firmware versions]] to determine the version you're running. Post this version number with your bug. |
||
| ⚫ | * If an activity crashed, you can often find a log file, and we would love it if you'd post the important parts of that with your bug. You can use the [[Log]] viewer activity. Find the log that corresponds to your application and look for sections that start with "Traceback (most recent call last):" and end with an unindented error name and details. (For older logs, you can use the [[Terminal activity]] to browse subfolders of <tt>/home/olpc/.sugar/default/logs</tt>) |
||
cat /boot/olpc_build |
|||
into the terminal activity. Post this version number with your bug. |
|||
| ⚫ | * If an activity crashed, you can often find a log file, and we would love it if you'd post the important parts of that with your bug. You can use the |
||
== Hardest but most useful: Fix it yourself. == |
== Hardest but most useful: Fix it yourself. == |
||
Revision as of 02:58, 3 August 2008
Like all open software, the software on the XO is constantly ready for improvement. While the basic functionality is now good, the truth is that many components are only at a beta-testing quality level. That means that we appreciate all bug reports from our users. (In fact, we hope that you will think of the bugs you find as opportunities to help us improve, rather than just nuisances.)
There are two ways to let us know about a bug
Quick and easy way: tell somebody
The easy way: write an email to "help AT laptop.org".
Harder but more helpful: Trac
The harder-but-more-helpful way: First search the Trac bug database at http://dev.laptop.org/query to see if the bug has already been reported. If it has not, register yourself on that site and submit the bug. Some useful hints:
- The only fields you have to fill out are summary, description, type (defect if it does the wrong thing, enhancement if it doesn't let you try to do a thing), and component. If you want to, you can put yourself in the cc field. We'll do the rest.
- Follow How to check the OS and firmware versions to determine the version you're running. Post this version number with your bug.
- If an activity crashed, you can often find a log file, and we would love it if you'd post the important parts of that with your bug. You can use the Log viewer activity. Find the log that corresponds to your application and look for sections that start with "Traceback (most recent call last):" and end with an unindented error name and details. (For older logs, you can use the Terminal activity to browse subfolders of /home/olpc/.sugar/default/logs)
Hardest but most useful: Fix it yourself.
Much of our software is designed to be hacked and debugged directly on the XO. If you discover a problem and feel like contributing directly to its diagnosis and solution, please, step right up!
Source code is readily available on the XO (for most of Sugar) and from places like http://dev.laptop.org and http://cvs.fedoraproject.org (everything else).
http://www.sugarlabs.org/go/DevelopmentTeam/CodeReview gives some great hints on how to submit improvements to Sugar. In general, all patches are welcome on our mailing lists. Finally, patches can be contributed directly to Fedora or to the actual upstream projects included in Fedora.