5.2. How To Report A Bug

5.2.1. All Bug Reports

Some simple advice on making your bug report more useful (and thus more likely to get answered and fixed):

1. Post as much relevant information as possible.

   This means we need more information than a simple "MS Word crashes whenever I run it. Do you know why?" Include at least the following information:

   • Which version of Wine you're using (run wine --version)

   • The name of the Operating system you're using, what distribution (if any), and what version. (i.e., Linux Red Hat 7.2)

   • Which compiler and version, (run gcc -v). If you didn't compile wine then the name of the package and where you got it from.

   • The name of the program you're trying to run, its version number, and a URL for where the program can be obtained (if available).

   • The exact command line you used to start wine. (i.e., wine "C:\Program Files\Test\program.exe").

   • If there is a crash dialog on the screen acknowledge it so ensure all information is printed to the terminal.

   • Useful terminal output contains a backtrace with debug symbols, see the Backtraces wiki entry

   • Create an attachment with full terminal output in a text file.

                   cd ~/.wine/drive_c/Games/Tron
                   wine tron.exe &> log.txt
           

   • The exact steps required to reproduce the bug.

   • Any other information you think may be relevant or helpful, such as X server version in case of X problems, libc version etc.

2. You may be asked to re-run the program with the WINEDEBUG environment variable WINEDEBUG=+relay,+seh,+tid option (i.e., WINEDEBUG=+relay,+seh,+tid wine sol.exe &> log.txt).

   This will produce additional information which may include the cause for a crash or may be helpful in debugging the program. It also slows the execution of program. There are some cases where the bug seems to disappear when +relay is used. Please mention that in the bug report.