Posts tagged Guide

A part of life is living with bugs of all sorts. As the fall season moves into colder weather the bug population is getting lesser.  Unfortunately, bugs in software reside year round.  You fix one bug and another bug pops up.  Developers need help in fixing bugs so the users can have better software.  Developers depend on it’s users to use, test and report bugs.  Users seem to handle the using and testing part fine, but struggle with reporting.  For example, filing a bug report simply stating ” I get an error starting my program, please fix it ” is only going to waste everyone’s time.  Yes, we really get such reports as above.  People will even post to the wrong bugzilla.  So a quick guide to submitting a bug at Sabayon Bugzilla.

1.  We need to know name and version of the software that is having the issue.   An example would be gdm-3.0.4-r2 or better yet, gnome-base/gdm-3.0.4-r2

2.  We need to know about the Operating System you have installed since we offer many different versions to install. An example would be Sabayon Linux 6 amd64 G.  Along with this, we need to know if you are fully updated with the updates and which repositories are you using.

3.  We need to know how to replicate the issue you are having.  This is critical!  It could be as simple as when I click on the program to start, I get this error.  It could be while using the program and trying to use a particular feature of the software and something bad happens.  Be informative and clear with directions on how we can get the same problem.  This will help us confirm the bug.

4.  We need log files of some sort.  A log file could simply be an error report that the program itself makes or some output from a terminal window leading up to the issue.  Attach the log file to the bug report.  Do not use a pastebin site as they delete information and we can no longer access your log.  So just attach a text file with the information of the error.  If it’s a short message, just put it into the report directly.  Attaching a file of a one line error message is not necessary, just include it in the Description.

5.  Before submitting a bug, use the handy dandy search on the Bugzilla page and make sure someone hasn’t already filed the same bug.  20 people submitting the same bug just bogs the bug wranglers down.  You may just find the same bug and the fix and save everybody time.

So be assertive, informative and pay attention to help submit a bug properly so it can get fixed.  A developer may ask for more information or have you try something and you should be responsive to report back such needed information.  It’s hard and frustrating to try and solve a bug without the proper information.  Developers don’t have a magic crystal ball that will give them all the information needed.  Don’t let your bug report become INVALID.

Happy bug submitting!