File Bugs

From ReactOS
Jump to: navigation, search
This page is probably outdated

The information on this page might not be valid for the current state of ReactOS.
A Wiki Administrator should look at this page and decide or discuss what to do with it.


This page is outdated and needs to be modified. In September 2012, Bugzilla was replaced by JIRA. You can login, using your ROS website credentials. Several fields are the same as before, if you have questions regarding filing bugs, please use forum.

Contents

Outdated

This page describes how to file bugs in our Bugzilla Bug-Tracking Software. Bugzilla is used in this project to gather information about failing or misbehaving components and allows us to coordinate bug fixing efforts.

First Steps

If you think you found a bug in ReactOS:

  • Make sure you can replicate your bug. Restart ReactOS and try again to make sure.
  • Check that it hasn't been reported already. The bugzilla search will help you confirm this.
  • Make sure you are testing a recent and official ReactOS build. New nightly builds (preferred testing source) can be obtained here.
  • If you are running ReactOS on a virtual machine, please mind that we support QEMU, VMware and VirtualBox. Others are not supported.

Since certain bug types are out of the scope of the project, please:

  • Do not report build breakages on common platforms (Windows, Linux). Please report these on IRC or to the ros-dev mailing list.
  • Do not report features announced for the next version of Windows (WinFS, etc.).
  • Do not report bugs in external components (Freetype, Wine, Mesa, etc.). Please use the other projects bug trackers for this purpose.

Important Information to Include

To make sure we can reproduce and fix your bug, certain information has to be present. Important data you should include in your report includes:

  • Reproduction method using step by step instructions.
  • Hardware or virtual machine configuration.
  • Tested ReactOS version (verify also that it does happen on nightly builds.
  • The version of the application tested (if any) and a download link (URL).
  • Screenshot of the problem if it's a graphical bug (add the attachment in Bugzilla).
  • Debug log for crashes, freezes and application errors. See Debugging to see how to obtain a high quality debug output.

Reporting Guidelines

To help you reporting and ease the bug fixing process please follow these guidelines:

  • Choose a concise bug title.
  • Try not to paste the debug log directly into the bug report, attach it instead. It helps readability.
  • Attach pictures to bugzilla directly instead of using external hosting services.
  • Use Bugzilla to file bugs, not to ask for support or discuss things not related to the bug.
  • The bug report should cover a single problem, no matter if it happens in multiple applications or has multiple ways of replicating it.
  • Do not post more than one issue in a single bug report.

Bugs that do not follow the guidelines will be closed as invalid and the reporter will be asked to report the bug properly.

In case any questions or problems regarding the bug reporting process arise, consult AmineKhaldi, Caemyr or gabriel_it on IRC.

Personal tools
Namespaces

Variants
Actions
Navigation
Tools