Bugzilla and Bugs

This page is for notes on how to use Bugzilla to report and triage bugs. DanKegel has a similar page, and there's some information in the Wine User's Guide. There is also some generic information on writing good bug reports.

When to report a bug

When : You should report a bug when:

• Wine doesn't run a program the same way as Windows does (eg. crash) with the default Wine configuration (ie. no dlls from Windows, or DllOverrides set).

• You are using the latest version of Wine (See downloads for information on how to get the latest).

• You tested with a clean Wine directory (default location: "~/.wine")

  • Your system isn't at fault (system hangs/lockups that require a system reboot are usually driver problems)

• Your system has all the libraries that Wine needs (see Recommended Packages)

• You haven't modified Wine in any way (ie. you are using a prepackaged binary or built from source by doing: "./configure ; make depend ; make")

• You have searched bugzilla, and the problem hasn't been reported already. Check KnownIssues as well.

  • Also search for the application in the AppDB and look at the bug links for that application, it could be already reported.

How to report

How : Go to http://bugs.winehq.org, login and click Enter bug, then Wine.

• Put the name of the application in the Summary field, followed by a short description of the error. eg

  • WinZip: crashes when extracting a zip archive
         

    Use a summary explaining the bug symptoms and the name of the program that displays them, not what you think the problem is, so that:
  • Users can find duplicates
  • The problem can be marked as solved by checking that the symptom is gone
  • The bug remains valid even if your analysis is incorrect

• Describe the crash in the Comments field, specifically, how to make the crash happen. eg.

  • Wine crashes when I click on the Extract button on the toolbar in WinZip 10.
         

    If you have any clues as to what the problem is, write them in here. Don't paste too much information in the comments field, just what looks relevant. Do not paste backtraces or error logs in the comments field. (attach them instead) For bugs related to graphics, sound, and hardware devices, be sure to write down what hardware and drivers you're using.

    Here is an example of what NOT to do

• Provide a download link to a free version of the program that shows the bug if possible. eg.

  • http://www.winzip.com/downwz.htm
         

• Attach any backtraces or error logs to the bug. You have to Submit the bug first before you're given the option to attach files. Again, please Do not paste backtraces or error logs in the comments field.

• Set the severity to

  • Trivial for a UI glitch that doesn't affect running of a program

  • Minor for minor loss of functionality, or other problem where an easy workaround is present

  • Normal for an application crash

  • Major for a problem that is affecting most applications you run in Wine

  • Critical when Wine won't start at all for any application, but there's a work around

  • Blocker when Wine won't start at all for any application, and there's no work around

  • For the above example, the severity is Normal. In 99% of the cases, the severity should be set to Normal or Minor. Please remember blocker does not mean "it blocks you from running a single app" and not being able to play a game does not count as critical.

• After you submitted the bug, please add it to the appropriate AppDB page(s). If there is no entry in the AppDB for an application, it might be helpful to add one (though that is not required for the bug report).

See Also

• KnownIssues