Mercurial > mplayer.hg
annotate DOCS/xml/en/bugreports.xml @ 12241:bcb8260d93e4
Common -vo driver problem solution explained by Lukasz Proszek.
author | diego |
---|---|
date | Tue, 20 Apr 2004 22:10:11 +0000 |
parents | d480f7e36b74 |
children | 3860159f1591 |
rev | line source |
---|---|
9675 | 1 <?xml version="1.0" encoding="iso-8859-1"?> |
10913
49b1a67e7381
Add revision keyword to english xml files, to ease translation synchronization
lumag
parents:
10111
diff
changeset
|
2 <!-- $Revision$ --> |
9675 | 3 <appendix id="bugreports"> |
4 <title>How to report bugs</title> | |
5 <para> | |
6 Good bug reports are a very valuable contribution to the development of any | |
7 software project. But just like writing good software, good problem reports | |
8 involve some work. Please realize that most developers are extremely busy and | |
9 receive obscene amounts of email. So while your feedback is crucial in improving | |
11540 | 10 <application>MPlayer</application> and very much appreciated, please understand |
11 that you have to provide <emphasis role="bold">all</emphasis> of the information | |
12 we request and follow the instructions in this document closely. | |
9675 | 13 </para> |
14 <sect1 id="bugreports_fix"> | |
15 <title>How to fix bugs</title> | |
16 <para> | |
17 If you feel have the necessary skills you are invited to have a go at fixing the | |
18 bug yourself. Or maybe you already did that? Please read | |
19 <ulink url="../../tech/patches.txt">this short document</ulink> to find out how to | |
11540 | 20 get your code included in <application>MPlayer</application>. The people on the |
9675 | 21 <ulink url="http://mplayerhq.hu/mailman/listinfo/mplayer-dev-eng">mplayer-dev-eng</ulink> |
22 mailing list will assist you if you have questions. | |
23 </para> | |
24 </sect1> | |
25 <sect1 id="bugreports_report"> | |
26 <title>How to report bugs</title> | |
27 <para> | |
11540 | 28 First of all please try the latest CVS version of <application>MPlayer</application> |
29 as your bug might already be fixed there. Development moves extremely fast, | |
30 most problems in official releases are reported within days or even hours, so | |
31 please use <emphasis role="bold">only CVS</emphasis> to report bugs. This | |
32 includes binary packages of <application>MPlayer</application>. CVS | |
33 instructions can be found at the bottom of | |
9675 | 34 <ulink url="http://www.mplayerhq.hu/homepage/dload.html">this page</ulink> or in |
35 the README. If this did not help please refer to the list of | |
36 <link linkend="bugs">known bugs</link> and the rest of the documentation. If your | |
37 problem is not known or not solvable by our instructions, then please report the bug. | |
38 </para> | |
39 | |
40 <para> | |
41 Please do not send bug reports privately to individual developers. This is | |
42 community work and thus there might be several people interested in it. Sometimes | |
43 other users already experienced your troubles and know how to circumvent a problem | |
11540 | 44 even if it is a bug in <application>MPlayer</application> code. |
9675 | 45 </para> |
46 | |
47 <para> | |
48 Please describe your problem in as much detail as possible. Do a little detective | |
49 work to narrow down the circumstances under which the problem occurs. Does the bug | |
50 only show up in certain situations? Is it specific to certain files or file types? | |
51 Does it occur with only one codec or is it codec independent? Can you reproduce it | |
52 with all output drivers? The more information you provide the better are our | |
53 chances at fixing your problem. Please do not forget to also include the valuable | |
54 information requested below, we will be unable to properly diagnose your problem | |
55 otherwise. | |
56 </para> | |
57 | |
58 <para> | |
59 An excellent and well written guide to asking questions in public forums is | |
9740 | 60 <ulink url="http://www.catb.org/~esr/faqs/smart-questions.html">How To Ask |
61 Questions The Smart Way</ulink> by <ulink url="http://www.catb.org/~esr/">Eric S. Raymond</ulink>. | |
9675 | 62 There is another called |
63 <ulink url="http://www.chiark.greenend.org.uk/~sgtatham/bugs.html">How to Report | |
64 Bugs Effectively</ulink> by <ulink url="http://www.chiark.greenend.org.uk/~sgtatham/">Simon Tatham</ulink>. | |
65 If you follow these guidelines you should be able to get help. But please | |
66 understand that we all follow the mailing lists voluntarily in our free time. We | |
67 are very busy and cannot guarantee that you will get a solution for your problem | |
68 or even an answer. | |
69 </para> | |
70 | |
71 </sect1> | |
72 | |
73 <sect1 id="bugreports_where"> | |
74 <title>Where to report bugs</title> | |
75 <para> | |
76 Subscribe to the mplayer-users mailing list: | |
77 <ulink url="http://mplayerhq.hu/mailman/listinfo/mplayer-users"/> | |
78 and send your bug report to: | |
79 <ulink url="mailto:mplayer-users@mplayerhq.hu"/> | |
80 </para> | |
81 <para> | |
10111 | 82 The language of this list is <emphasis role="bold">English</emphasis>. Please follow the standard |
9675 | 83 <ulink url="http://www.ietf.org/rfc/rfc1855.txt">Netiquette Guidelines</ulink> and |
10111 | 84 <emphasis role="bold">do not send HTML mail</emphasis> to any of our mailing lists. You will only get ignored or |
9675 | 85 banned. If you do not know what HTML mail is or why it is evil, read this |
86 <ulink url="http://expita.com/nomime.html">fine document</ulink>. It explains all | |
87 the details and has instructions for turning HTML off. Also note that we will not | |
88 individually CC (carbon-copy) people so it is a good idea to subscribe to actually | |
89 receive your answer. | |
90 </para> | |
91 </sect1> | |
92 | |
93 <sect1 id="bugreports_what"> | |
94 <title>What to report</title> | |
95 <para> | |
96 You may need to include log, configuration or sample files in your bug report. | |
97 If some of them are quite big then it is better to upload them to our | |
98 <ulink url="ftp://mplayerhq.hu/MPlayer/incoming/">FTP server</ulink> in a | |
99 compressed format (gzip and bzip2 preferred) and include only the path and file | |
100 name in your bug report. Our mailing lists have a message size limit of 80k, if | |
101 you have something bigger you have to compress or upload it. | |
102 </para> | |
103 | |
104 <sect2 id="bugreports_system"> | |
105 <title>System Information</title> | |
106 <para> | |
107 <itemizedlist> | |
108 <listitem><para> | |
109 Your Linux distribution or operating system and version e.g.: | |
110 <itemizedlist> | |
111 <listitem><para>Red Hat 7.1</para></listitem> | |
112 <listitem><para>Slackware 7.0 + devel packs from 7.1 ...</para></listitem> | |
113 </itemizedlist> | |
114 </para></listitem> | |
115 <listitem><para> | |
116 kernel version: | |
117 <screen>uname -a</screen> | |
118 </para></listitem> | |
119 <listitem><para> | |
120 libc version: | |
121 <screen>ls -l /lib/libc[.-]*</screen> | |
122 </para></listitem> | |
123 <listitem><para> | |
124 gcc and ld versions: | |
125 <screen> | |
126 gcc -v | |
127 ld -v | |
128 </screen> | |
129 </para></listitem> | |
130 <listitem><para> | |
10111 | 131 binutils version: |
132 <screen> | |
133 as --version | |
134 </screen> | |
135 </para></listitem> | |
136 <listitem><para> | |
9675 | 137 If you have problems with fullscreen mode: |
138 <itemizedlist> | |
139 <listitem><para>Window manager type and version</para></listitem> | |
140 </itemizedlist> | |
141 </para></listitem> | |
142 <listitem><para> | |
143 If you have problems with XVIDIX: | |
144 <itemizedlist> | |
145 <listitem><para>X colour depth: | |
146 <screen>xdpyinfo | grep "depth of root"</screen> | |
147 </para></listitem> | |
148 </itemizedlist> | |
149 </para></listitem> | |
150 <listitem><para> | |
151 If only the GUI is buggy: | |
152 <itemizedlist> | |
153 <listitem><para>GTK version</para></listitem> | |
154 <listitem><para>GLIB version</para></listitem> | |
155 <listitem><para>libpng version</para></listitem> | |
156 <listitem><para>GUI situation in which the bug occurs</para></listitem> | |
157 </itemizedlist> | |
158 </para></listitem> | |
159 </itemizedlist> | |
160 </para> | |
161 </sect2> | |
162 | |
163 <sect2 id="bugreports_hardware"> | |
164 <title>Hardware and drivers</title> | |
165 <para> | |
166 <itemizedlist> | |
167 <listitem><para> | |
168 CPU info (this works on Linux only): | |
169 <screen>cat /proc/cpuinfo</screen> | |
170 </para></listitem> | |
171 <listitem><para> | |
172 Video card manufacturer and model, e.g.: | |
173 <itemizedlist> | |
174 <listitem><para>ASUS V3800U chip: nVidia TNT2 Ultra pro 32MB SDRAM</para></listitem> | |
175 <listitem><para>Matrox G400 DH 32MB SGRAM</para></listitem> | |
176 </itemizedlist> | |
177 </para></listitem> | |
178 <listitem><para> | |
179 Video driver type & version, e.g.: | |
180 <itemizedlist> | |
181 <listitem><para>X built-in driver</para></listitem> | |
182 <listitem><para>nVidia 0.9.623</para></listitem> | |
183 <listitem><para>Utah-GLX CVS 2001-02-17</para></listitem> | |
184 <listitem><para>DRI from X 4.0.3</para></listitem> | |
185 </itemizedlist> | |
186 </para></listitem> | |
187 <listitem><para> | |
188 Sound card type & driver, e.g.: | |
189 <itemizedlist> | |
190 <listitem><para>Creative SBLive! Gold with OSS driver from oss.creative.com</para></listitem> | |
191 <listitem><para>Creative SB16 with kernel OSS drivers</para></listitem> | |
192 <listitem><para>GUS PnP with ALSA OSS emulation</para></listitem> | |
193 </itemizedlist> | |
194 </para></listitem> | |
195 <listitem><para> | |
196 If in doubt include <command>lspci -vv</command> output on Linux systems. | |
197 </para></listitem> | |
198 </itemizedlist> | |
199 </para> | |
200 </sect2> | |
201 | |
202 <sect2 id="bugreports_configure"> | |
203 <title>Configure problems</title> | |
204 <para> | |
205 If you get errors while running <command>./configure</command>, or autodetection | |
206 of something fails, read <filename>configure.log</filename>. You may find the | |
207 answer there, for example multiple versions of the same library mixed on your | |
208 system, or you forgot to install the development package (those with the -dev | |
209 suffix). If you think there is a bug, include <filename>configure.log</filename> | |
210 in your bug report. | |
211 </para> | |
212 </sect2> | |
213 | |
214 <sect2 id="bugreports_conpilation"> | |
215 <title>Compilation problems</title> | |
216 <para> | |
217 Please include these files: | |
218 <itemizedlist> | |
219 <listitem><para>config.h</para></listitem> | |
220 <listitem><para>config.mak</para></listitem> | |
221 </itemizedlist> | |
222 Only if compilation fails below one of these directories, include these files: | |
223 <itemizedlist> | |
224 <listitem><para>Gui/config.mak</para></listitem> | |
225 <listitem><para>libvo/config.mak</para></listitem> | |
226 <listitem><para>libao2/config.mak</para></listitem> | |
227 </itemizedlist> | |
228 </para> | |
229 </sect2> | |
230 | |
231 <sect2 id="bugreports_playback"> | |
232 <title>Playback problems</title> | |
233 <para> | |
234 Please include the output of <application>MPlayer</application> at verbosity level | |
235 1, but remember to <emphasis role="bold">not truncate the output</emphasis> when | |
236 you paste it into your mail. The developers need all of the messages to properly | |
237 diagnose a problem. You can direct the output into a file like this: | |
238 <screen>mplayer -v <replaceable>options</replaceable> <replaceable>filename</replaceable> > mplayer.log 2>&1</screen> | |
239 </para> | |
240 | |
241 <para> | |
242 If your problem is specific to one or more files, then please upload the offender(s) to: | |
243 <ulink url="ftp://mplayerhq.hu/MPlayer/incoming/"/> | |
244 </para> | |
245 | |
246 <para> | |
247 Also upload a small text file having the same base name as your file with a .txt | |
248 extension. Describe the problem you are having with the particular file there and | |
11540 | 249 include your email address as well as the output of <application>MPlayer</application> |
250 at verbosity level 1. Usually the first 1-5 MB of a file are enough to reproduce | |
251 the problem, but to be sure we ask you to: | |
9675 | 252 <screen>dd if=<replaceable>yourfile</replaceable> of=<replaceable>smallfile</replaceable> bs=1024k count=5</screen> |
253 It will take the first five megabytes of '<emphasis role="bold">your-file</emphasis>' | |
254 and write it to '<emphasis role="bold">small-file</emphasis>'. Then try again on | |
255 this small file and if the bug still shows up your sample is sufficient for us. | |
256 Please <emphasis role="bold">do not ever</emphasis> send such files via mail! | |
257 Upload it, and send only the path/filename of the file on the FTP-server. If the | |
258 file is accessible on the net, then sending the <emphasis role="bold">exact</emphasis> | |
259 URL is sufficient. | |
260 </para> | |
261 </sect2> | |
262 | |
263 <sect2 id="bugreports_crash"> | |
264 <title>Crashes</title> | |
265 <para> | |
266 You have to run <application>MPlayer</application> inside <command>gdb</command> | |
267 and send us the complete output or if you have a <filename>core</filename> dump of | |
268 the crash you can extract useful information from the Core file. Here's how: | |
269 </para> | |
270 | |
271 <sect3 id="bugreports_debug"> | |
272 <title>How to conserve information about a reproducible crash</title> | |
273 <para> | |
11540 | 274 Recompile <application>MPlayer</application> with debugging code enabled: |
9675 | 275 <screen> |
276 ./configure --enable-debug=3 | |
277 make | |
278 </screen> | |
11540 | 279 and then run <application>MPlayer</application> within gdb using: |
9675 | 280 <screen>gdb ./mplayer</screen> |
281 You are now within gdb. Type: | |
282 <screen>run -v <replaceable>options-to-mplayer</replaceable> <replaceable>filename</replaceable></screen> | |
283 and reproduce your crash. As soon as you did it, gdb will return you to the command | |
284 line prompt where you have to enter | |
285 <screen> | |
286 bt | |
287 disass $pc-32 $pc+32 | |
288 info all-registers | |
289 </screen> | |
290 </para> | |
291 </sect3> | |
292 | |
293 <sect3 id="bugreports_core"> | |
294 <title>How to extract meaningful information from a core dump</title> | |
295 <para> | |
11049 | 296 Create the following command file: |
9675 | 297 <screen> |
298 bt | |
299 disass $pc-32 $pc+32 | |
300 info all-registers | |
301 </screen> | |
11049 | 302 Then simply execute this command: |
9675 | 303 <screen>gdb mplayer --core=core -batch --command=<replaceable>command_file</replaceable> > mplayer.bug</screen> |
304 </para> | |
305 </sect3> | |
306 </sect2> | |
307 </sect1> | |
308 | |
309 <sect1 id="bugreports_advusers"> | |
310 <title>I know what I am doing...</title> | |
311 <para> | |
312 If you created a proper bug report following the steps above and you are confident | |
11540 | 313 it is a bug in <application>MPlayer</application>, not a compiler problem or broken |
314 file, you have already read the documentation and you could not find a solution, | |
315 your sound drivers are OK, then you might want to subscribe to the mplayer-advusers | |
316 list and send your bug report there to get a better and faster answer. | |
9675 | 317 </para> |
318 | |
319 <para> | |
320 Please be advised that if you post newbie questions or questions answered in the | |
321 manual there, you will be ignored or flamed instead of getting an appropriate answer. | |
322 So do not flame us and subscribe to -advusers only if you really know what you are | |
11540 | 323 doing and feel like being an advanced <application>MPlayer</application> user or |
324 developer. If you meet these criteria it should not be difficult to find out how to subscribe... | |
9675 | 325 </para> |
326 | |
327 </sect1> | |
328 | |
329 </appendix> |