Reporting bugs: Difference between revisions
(fields) |
(cat) |
||
| Line 5: | Line 5: | ||
The easy way: write an email to "help AT laptop.org". |
The easy way: write an email to "help AT laptop.org". |
||
The harder-but-more-helpful way: First search the 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 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. |
||
| Line 16: | Line 16: | ||
* 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 the subfolders of /home/olpc/.sugar/default/logs) |
* 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 the subfolders of /home/olpc/.sugar/default/logs) |
||
[[Category:Developers]] |
|||
[[Category:Software]] |
|||
Revision as of 22:04, 7 February 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
The easy way: write an email to "help AT laptop.org".
The harder-but-more-helpful way: First search the trac bug database at [1] 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.
- if you have updated the system software, you can find the version you're running by typing
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 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 the subfolders of /home/olpc/.sugar/default/logs)