-
Notifications
You must be signed in to change notification settings - Fork 3
Bug Reporting
Opening a bug reports is a way of helping the community and improving the repository, good bug reports are crucial for developpers. This wiki will teach you how to debug and report a good bug report.
Before reporting a bug, you should check the bugtracker if there isn’t already an bug report for your problem.
Secondly update your system, the package might be build against a new lib, so be sure you have the latest updates installed.
Once you know nobody reported the bug either at the bugtracker or Upstream, you have to ask yourself whether your problem is a bug or a feature
- A bug is something that should work but does not work as intended by the developer.
- A feature is something a software does or would do if somebody coded it.
Here is a list of usefull info to report:
- Version of the related package.
- Version of the related libary ( dependencies ).
- The architecture of your sytem ( 64 bit or 32bit ).
- The Whole output of of the crash, run the program from a command line to view this info.
- Report any related logs.
Choosing a critical severity will not help to solve the bug faster. It will only make truely critical problems less visible and probably make the developer assigned to your bug a bit less open to fixing it.
Here is a general usage of severities
- Critical- System crash, severe boot failure that is likely to affect more than just you, or an exploitable security issue in either a core or outward-facing service package.
- High- The main functionality of the application does not work, less critical security issues, etc.
- Medium- A non-essential functionality does not work, UNIX standards not respected, etc.
- Low- An optional functionality (plugin or compilation activated) does not work.
- Very Low- Translation or documentation mistake. Something that really does not matter much but should be noticed for a future release.
When the developer thinks he fixed the bug, check if it works for you and report it back. When confirmed the bug can be closed.