openSUSE:Indienen van bugrapporten
- Ontwikkelaars en ervaren gebruikers: U kunt direct naar http://bugzilla.novell.com gaan en een bug rapporteren.
- Niet-technische gebruikers: U zou eerst http://forums.opensuse.org kunnen proberen.
- Wilt u iets leren: Het is niet het gemakkelijkste dat u ooit deed, maar het is ook geen hemelhoge wetenschap. Lees de onderstaande tekst die de basisinstructies bevatten over hoe een bug te rapporteren.
In het algemeen: Het openSUSE project bevat een groeiend netwerk van vrijwilligers van Linux gebruikers en ontwikkelaars die participeren in de doorgaande creatie en verbetering van openSUSE door het testen van vrijgaven voor ontwikkeling. Dit team van testers heeft een gemeenschappelijke missie: zij verbeteren 's werelds meest bruikbare Linux distributie door het vinden en constructief rapporteren van relevante bugs.
We rapporteren bugs, dienen verbeteringsrapporten in of publiceren patches in Bugzilla, de openSUSE bug tracking system. Door het systeem goed te doorzoeken en door duidelijke en accurate details te verstrekken, kunnen ontwikkelaars de fout beter reproduceren en snel oplossingen vinden.
Als je wilt deelnemen aan het team van bug reporters, bekijk dan de openSUSE bug reporting FAQ voor informatie, lees over severities and priorities. Lees ook onze testing informatie voor nieuwe testers.
Ook wordt je uitgenodigd om de bug direct op te lossen, zoals uitgelegd in the fixing bugs documentation.
Inhoud
Bezoek Bugzilla
Om een bug te rapporteren op Bugzilla, bezoek je de versie pagina die in deze lijst staat.
First you will see the login page. Bugzilla and openSUSE wiki logins are the same.
- openSUSE 12.1
- openSUSE 11.4
- openSUSE 11.3
- openSUSE 11.2
- openSUSE 11.1 Opmerking: De 11.1 versie is nu Evergreen en ontvangt alleen beveiligings patches van leden uit de gemeenschap. Andere bugs kunnen dan ook niet worden verwerkt.
Hier is de lijst van bugs die horen bij openSUSE projecten:
Dit artikel is nog maar gedeeltelijk vertaald. Als u mee wilt helpen met vertalen lees dan Wiki vertalen naar het Nederlands. |
You may use helper javascripts in your Opera or Firefox (with Greasemonkey extension) to make your work with Novell Bugzilla more comfortable.
Searching for bugs
Before you begin, check to see if the bug has already been reported, especially in the list of most annoying bugs.
You can also search for:
and look through the list.
Reporting a bug
All openSUSE bugs should go into the product openSUSE. Always choose the right product when reporting a bug. At this time, the public Bugzilla is not intended for the enterprise products.
Some software components have special instructions for bug reporting, which you can find here:
- How to attach an error log when an application crashes
- How to attach a log for bugs related to YaST or the installation
- How to attach a log for bugs related to Zypper or OpenSUSE Updater Applet
- How to attach a log for bugs related to ZENworks/rug
- How to report Factory bug
- How to report a GCC bug
- How to report a kernel bug
- How to report a mkinitrd bug
- How to report a KDE bug
- How to report a X11-related bug
- How to report a printing-related bug
- How to report a sound-related bug
- How to report a GNOME bug
- How to report a bug in Kontact's Novell GroupWise support
- How to report SaX2 bugs
- How to report suspend bugs
- How to report AppArmor bugs
- How to report a Mozilla / Firefox bug
- How to report LibreOffice bug
- How to report OpenOffice.org bug
- How to report a boot loader (grub) bug
- How to report a Samba bug
- How to report a Security bug
- How to report a HAL bug
- How to report a Wireless connectivity bug
Selecting the correct component and version number when reporting a bug
Choosing the wrong product or component causes inefficient handling of your report, because it is initially assigned to the wrong people. Or it makes us wonder whether an already-fixed bug could possibly reappear in certain cases, which also creates unnecessary work. Choosing the correct product, component, and version is vital for us to quickly reproduce (and finally solve) your problem. So please be careful here.
- All openSUSE versions you can download here are handled in the component 'openSUSE X.X' (X.X is the version you found the bug in, e.g. 11.0). If you are milestone and release candidate versions, it is very important to specify this in the version field of Bugzilla. Providing just the product version is not enough here.
- The product 'openSUSE.org' is for bugs in this Wiki system on opensuse.org and bugs in bugzilla.novell.com itself only.
- If you know project and package, you can look it up in build.opensuse.org and click the little beatle icon []</> there to get a prefilled bugzilla entry:
- product=openSUSE.org
- classification=7340
- component=3rd party software
- assigned_to=bugowner of the package
- short_desc=project:name/package_name: what happened
Voting in Bugzilla
Voting in Bugzilla is intended for orientation purposes only--not for specific prioritization or resource allocation.
- For further information about voting, refer to voting page.
- List Bugzilla reports with votes
Reporting documentation defects
Please report openSUSE documentation defects in Bugzilla (component: "Documentation").
The man pages are maintained upstream as part of a corresponding source package or the global package called "man-pages"; the openSUSE documentation department is not responsible for these documents. If you find an inaccuracy in these man pages, take the time to report the issue upstream. At the end of the man page, find the bug reporting address.
Fixing bugs
You can also participate in fixing bugs as explained on the fixing bugs documentation. The easiest way to start with fixing bugs are junior jobs. These are manually selected easy to fix examples on which you can learn how to contribute and start contributing.