Moblin Bugzilla
Submitted by pingyu, updated on 21 May 2009
Create account
Bugzilla uses the same account as moblin.org. Open a new Moblin Bugzilla account to register a bugzilla account.
Where my bug should go
Moblin distribution
If you find a bug when you are trying the Moblin distribution downloaded from this website or the image you created with Moblin Image Creator 2.0, please submit a Moblin distribution bug.
Projects related bug
There are some Moblin related open projects hosted on this website. If you're working those projects and find a bug related to a specific project, you can go to that project's home page, where you will find a link to report bugs.
Issues related Bugzilla itself
You can submit bugzilla's bugs here.
Bug Reporting Guidelines
- Each bug report is for only one issue. If you find several issues in one test, please separate them into several bugs.
- Write a precise summary (bug title). A good summary should be straightforward and precise, clearly identifying the issue.
- List the exact steps to reproduce the bug (bash commands, results after executing the commands, etc, instead of only paraphrasing), that is, instead of paraphrasing commands by saying:
" suspend the system or put system to S3"
we prefer to see the following exact commands as steps to reproduce the bug:
# echo mem >/sys/power/state
- Reproducibility. For bugs which are not 100% reproducible, please provide the steps to reproduce the bug, along with an estimate of the probability of reproduction.
- Impact to system or user. Provide a description of the impact to the user or system.
- The "Vertical" field is one of the most important fields for bug reporting because we use one bugzilla product to track Moblin distribution bugs for all verticals. Please select the vertical where you found the bug, such as MID, netbook, or IVI.