Module: docs Branch: master Commit: 2fc58262f9a0e55f7899e013942cde1ad2929d9f URL: http://source.winehq.org/git/docs.git/?a=commit;h=2fc58262f9a0e55f7899e01394...
Author: André Hentschel nerv@dawncrow.de Date: Mon Feb 3 21:40:40 2014 +0100
wineusr: Remove bug reporting guide.
---
en/wineusr-bugs.sgml | 108 +------------------------------------------------- 1 file changed, 2 insertions(+), 106 deletions(-)
diff --git a/en/wineusr-bugs.sgml b/en/wineusr-bugs.sgml index c13cb17..a554e1b 100644 --- a/en/wineusr-bugs.sgml +++ b/en/wineusr-bugs.sgml @@ -219,112 +219,8 @@ <title>How To Report A Bug</title>
<para> - Please report all bugs along any relevant information to - <ulink url="http://bugs.winehq.org/">Wine Bugzilla</ulink>. - Please, search the Bugzilla database to check whether your problem - is already reported. If it is already reported please add - any relevant information to the original bug report. + Please find all information about reporting a bug + on the main page of <ulink url="http://bugs.winehq.org/">Wine Bugzilla</ulink>. </para> - - <sect2> - <title>All Bug Reports</title> - <para> - Some simple advice on making your bug report more useful - (and thus more likely to get answered and fixed): - </para> - <orderedlist> - <listitem> - <para> - Post as much relevant information as possible. - </para> - <para> - This means we need more information than a simple <quote>MS - Word crashes whenever I run it. Do you know why?</quote>. - Include at least the following information: - </para> - <itemizedlist spacing="compact"> - <listitem> - <para> - Which version of Wine you're using (run <userinput>wine --version</userinput>) - </para> - </listitem> - <listitem> - <para> - The name of the Operating system you're using, what distribution (if - any), and what version (e.g. Linux Red Hat 7.2). - </para> - </listitem> - <listitem> - <para> - Which compiler and version (run <userinput>gcc -v</userinput>). - If you didn't compile Wine then the name of the package and - where you got it from. - </para> - </listitem> - <listitem> - <para> - 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). - </para> - </listitem> - <listitem> - <para> - The exact command line you used to start Wine - (e.g. <userinput>wine "C:\Program Files<replaceable>Test</replaceable><replaceable>program.exe</replaceable>"</userinput>). - </para> - </listitem> - <listitem> - <para> - If there is a crash dialog on the screen acknowledge it so ensure - all information is printed to the terminal. - </para> - </listitem> - <listitem> - <para> - Useful terminal output - contains a backtrace with debug symbols, see the - <ulink url="http://wiki.winehq.org/Backtraces">Backtraces wiki entry</ulink>. - </para> - </listitem> - <listitem> - <para> - Create an attachment with full terminal output in a text file. -<screen> -cd ~/.wine/drive_c/Games/Tron -wine tron.exe &> log.txt -</screen> - </para> - </listitem> - <listitem> - <para> - The exact steps required to reproduce the bug. - </para> - </listitem> - <listitem> - <para> - Any other information you think may be relevant or - helpful, such as X server version in case of X - problems, libc version etc. - </para> - </listitem> - </itemizedlist> - </listitem> - <listitem> - <para> - You may be asked to re-run the program using a custom <envar>WINEBUG</envar> environment - variable value, e.g. <userinput><envar>WINEDEBUG</envar>=+relay,+seh,+tid - wine sol.exe &> log.txt</userinput>. - </para> - <para> - 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 <literal>+relay</literal> is used. - Please mention that in the bug report. - </para> - </listitem> - </orderedlist> - </sect2> </sect1> </chapter>