Mercurial > mplayer.hg
annotate DOCS/xml/en/bugreports.xml @ 28558:80ecd60e6808
Remove trailing whitespaces.
author | bircoph |
---|---|
date | Sun, 15 Feb 2009 14:48:30 +0000 |
parents | 203b81111882 |
children | 61e9c93193bc |
rev | line source |
---|---|
20535 | 1 <?xml version="1.0" encoding="utf-8"?> |
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> | |
21521 | 5 |
9675 | 6 <para> |
7 Good bug reports are a very valuable contribution to the development of any | |
8 software project. But just like writing good software, good problem reports | |
9 involve some work. Please realize that most developers are extremely busy and | |
10 receive obscene amounts of email. So while your feedback is crucial in improving | |
11540 | 11 <application>MPlayer</application> and very much appreciated, please understand |
12 that you have to provide <emphasis role="bold">all</emphasis> of the information | |
13 we request and follow the instructions in this document closely. | |
9675 | 14 </para> |
21521 | 15 |
16 | |
17 <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --> | |
18 | |
19 | |
18061
38e5974fa140
Explain how security issues should be reported, based on a patch by Ivann, featuring Reimar's suggestions
gpoirier
parents:
18059
diff
changeset
|
20 <sect1 id="bugreports_security"> |
26958 | 21 <title>Report security related bugs</title> |
21521 | 22 |
18061
38e5974fa140
Explain how security issues should be reported, based on a patch by Ivann, featuring Reimar's suggestions
gpoirier
parents:
18059
diff
changeset
|
23 <para> |
38e5974fa140
Explain how security issues should be reported, based on a patch by Ivann, featuring Reimar's suggestions
gpoirier
parents:
18059
diff
changeset
|
24 In case you have found an exploitable bug and you would like to do the |
38e5974fa140
Explain how security issues should be reported, based on a patch by Ivann, featuring Reimar's suggestions
gpoirier
parents:
18059
diff
changeset
|
25 right thing and let us fix it before you disclose it, we would be happy |
38e5974fa140
Explain how security issues should be reported, based on a patch by Ivann, featuring Reimar's suggestions
gpoirier
parents:
18059
diff
changeset
|
26 to get your security advisory at |
38e5974fa140
Explain how security issues should be reported, based on a patch by Ivann, featuring Reimar's suggestions
gpoirier
parents:
18059
diff
changeset
|
27 <ulink url="mailto:security@mplayerhq.hu">security@mplayerhq.hu</ulink>. |
38e5974fa140
Explain how security issues should be reported, based on a patch by Ivann, featuring Reimar's suggestions
gpoirier
parents:
18059
diff
changeset
|
28 Please add [SECURITY] or [ADVISORY] in the subject. |
38e5974fa140
Explain how security issues should be reported, based on a patch by Ivann, featuring Reimar's suggestions
gpoirier
parents:
18059
diff
changeset
|
29 Be sure that your report contains complete and detailed analysis of the bug. |
38e5974fa140
Explain how security issues should be reported, based on a patch by Ivann, featuring Reimar's suggestions
gpoirier
parents:
18059
diff
changeset
|
30 Sending a fix is highly appreciated. |
38e5974fa140
Explain how security issues should be reported, based on a patch by Ivann, featuring Reimar's suggestions
gpoirier
parents:
18059
diff
changeset
|
31 Please don't delay your report to write proof-of-concept exploit, you can |
38e5974fa140
Explain how security issues should be reported, based on a patch by Ivann, featuring Reimar's suggestions
gpoirier
parents:
18059
diff
changeset
|
32 send that one with another mail. |
38e5974fa140
Explain how security issues should be reported, based on a patch by Ivann, featuring Reimar's suggestions
gpoirier
parents:
18059
diff
changeset
|
33 </para> |
38e5974fa140
Explain how security issues should be reported, based on a patch by Ivann, featuring Reimar's suggestions
gpoirier
parents:
18059
diff
changeset
|
34 </sect1> |
21521 | 35 |
36 | |
37 <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --> | |
38 | |
39 | |
9675 | 40 <sect1 id="bugreports_fix"> |
41 <title>How to fix bugs</title> | |
21521 | 42 |
9675 | 43 <para> |
44 If you feel have the necessary skills you are invited to have a go at fixing the | |
45 bug yourself. Or maybe you already did that? Please read | |
21521 | 46 <ulink url="../../tech/patches.txt">this short document</ulink> to find out how |
47 to get your code included in <application>MPlayer</application>. The people on | |
48 the | |
19709 | 49 <ulink url="http://lists.mplayerhq.hu/mailman/listinfo/mplayer-dev-eng">MPlayer-dev-eng</ulink> |
9675 | 50 mailing list will assist you if you have questions. |
51 </para> | |
52 </sect1> | |
21521 | 53 |
54 | |
55 <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --> | |
56 | |
57 | |
17055 | 58 <sect1 id="bugreports_regression_test"> |
18599 | 59 <title>How to do regression testing using Subversion</title> |
21521 | 60 |
17055 | 61 <para> |
62 A problem that can happen sometimes is 'it used to work before, now it | |
63 doesn't anymore...'. | |
64 Here is a step by step procedure to try to pinpoint when the problem | |
65 occurred. This is <emphasis role="bold">not</emphasis> for casual users. | |
66 </para> | |
21521 | 67 |
17055 | 68 <para> |
18599 | 69 First, you'd need to fetch MPlayer's source tree from Subversion. |
21744 | 70 Instructions can be found in the |
71 <ulink url="http://www.mplayerhq.hu/design7/dload.html#svn">Subversion section of the download page</ulink>. | |
17055 | 72 </para> |
21521 | 73 |
17055 | 74 <para> |
21521 | 75 You will have now in the mplayer/ directory an image of the Subversion tree, on |
76 the client side. | |
17055 | 77 Now update this image to the date you want: |
78 <screen> | |
18599 | 79 cd mplayer/ |
80 svn update -r {"2004-08-23"} | |
17055 | 81 </screen> |
82 The date format is YYYY-MM-DD HH:MM:SS. | |
83 Using this date format ensure that you will be able to extract patches | |
84 according to the date at which they were committed, as in the | |
19679 | 85 <ulink url="http://lists.mplayerhq.hu/pipermail/mplayer-cvslog/">MPlayer-cvslog archive</ulink>. |
17055 | 86 </para> |
21521 | 87 |
17055 | 88 <para> |
89 Now proceed as for a normal update: | |
90 <screen> | |
91 ./configure | |
92 make | |
93 </screen> | |
94 </para> | |
21521 | 95 |
17055 | 96 <para> |
97 If any non-programmer reads this, the fastest method to get at the point | |
98 where the problem occurred is to use a binary search — that is, | |
18599 | 99 search the date of the breakage by repeatedly dividing the search |
17055 | 100 interval in half. |
101 For example, if the problem occurred in 2003, start at mid-year, then ask | |
102 "Is the problem already here?". | |
103 If yes, go back to the first of April; if not, go to the first of October, | |
104 and so on. | |
105 </para> | |
21521 | 106 |
17055 | 107 <para> |
108 If you have lot of free hard disk space (a full compile currently takes | |
109 100 MB, and around 300-350 MB if debugging symbols are enabled), copy the | |
110 oldest known working version before updating it; this will save time if | |
111 you need to go back. | |
112 (It is usually necessary to run 'make distclean' before recompiling an | |
113 earlier version, so if you do not make a backup copy of your original | |
114 source tree, you will have to recompile everything in it when you come | |
115 back to the present.) | |
116 </para> | |
21521 | 117 |
17055 | 118 <para> |
119 When you have found the day where the problem happened, continue the search | |
18599 | 120 using the mplayer-cvslog archive (sorted by date) and a more precise svn |
17055 | 121 update including hour, minute and second: |
122 <screen> | |
18599 | 123 svn update -r {"2004-08-23 15:17:25"} |
17055 | 124 </screen> |
125 This will allow you to easily find the exact patch that did it. | |
126 </para> | |
21521 | 127 |
17055 | 128 <para> |
129 If you find the patch that is the cause of the problem, you have almost won; | |
130 report about it to the | |
131 <ulink url="http://bugzilla.mplayerhq.hu/">MPlayer Bugzilla</ulink> or | |
28558 | 132 subscribe to |
19709 | 133 <ulink url="http://lists.mplayerhq.hu/mailman/listinfo/mplayer-users">MPlayer-users</ulink> |
17055 | 134 and post it there. |
135 There is a chance that the author will jump in to suggest a fix. | |
136 You may also look hard at the patch until it is coerced to reveal where | |
137 the bug is :-). | |
138 </para> | |
139 </sect1> | |
21521 | 140 |
141 | |
142 <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --> | |
143 | |
144 | |
9675 | 145 <sect1 id="bugreports_report"> |
146 <title>How to report bugs</title> | |
21521 | 147 |
9675 | 148 <para> |
21521 | 149 First of all please try the latest Subversion version of |
150 <application>MPlayer</application> | |
11540 | 151 as your bug might already be fixed there. Development moves extremely fast, |
21521 | 152 most problems in official releases are reported within days or even hours, |
153 so please use <emphasis role="bold">only Subversion</emphasis> to report bugs. | |
154 This includes binary packages of <application>MPlayer</application>. | |
155 Subversion instructions can be found at the bottom of | |
17706
83c1acef76d5
New website structure, the /homepage subdirectory is gone.
diego
parents:
17055
diff
changeset
|
156 <ulink url="http://www.mplayerhq.hu/dload.html">this page</ulink> or in |
28166
203b81111882
Remove known bugs section, it contains little useful information.
diego
parents:
26958
diff
changeset
|
157 the README. If this did not help please refer to the rest of the documentation. |
21521 | 158 If your problem is not known or not solvable by our instructions, |
159 then please report the bug. | |
9675 | 160 </para> |
161 | |
162 <para> | |
163 Please do not send bug reports privately to individual developers. This is | |
21521 | 164 community work and thus there might be several people interested in it. |
165 Sometimes other users already experienced your troubles and know how to | |
166 circumvent a problem even if it is a bug in <application>MPlayer</application> | |
167 code. | |
9675 | 168 </para> |
169 | |
170 <para> | |
21521 | 171 Please describe your problem in as much detail as possible. Do a little |
172 detective work to narrow down the circumstances under which the problem occurs. | |
173 Does the bug only show up in certain situations? Is it specific to certain | |
174 files or file types? Does it occur with only one codec or is it codec | |
175 independent? Can you reproduce it with all output drivers? The more information | |
176 you provide the better are our chances at fixing your problem. Please do not | |
177 forget to also include the valuable information requested below, we will be | |
178 unable to properly diagnose your problem otherwise. | |
9675 | 179 </para> |
180 | |
181 <para> | |
182 An excellent and well written guide to asking questions in public forums is | |
21521 | 183 <ulink url="http://www.catb.org/~esr/faqs/smart-questions.html">How To Ask Questions The Smart Way</ulink> |
184 by <ulink url="http://www.catb.org/~esr/">Eric S. Raymond</ulink>. | |
9675 | 185 There is another called |
21521 | 186 <ulink url="http://www.chiark.greenend.org.uk/~sgtatham/bugs.html">How to Report Bugs Effectively</ulink> |
187 by <ulink url="http://www.chiark.greenend.org.uk/~sgtatham/">Simon Tatham</ulink>. | |
9675 | 188 If you follow these guidelines you should be able to get help. But please |
189 understand that we all follow the mailing lists voluntarily in our free time. We | |
190 are very busy and cannot guarantee that you will get a solution for your problem | |
191 or even an answer. | |
192 </para> | |
21521 | 193 </sect1> |
9675 | 194 |
21521 | 195 |
196 <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --> | |
197 | |
9675 | 198 |
199 <sect1 id="bugreports_where"> | |
200 <title>Where to report bugs</title> | |
21521 | 201 |
9675 | 202 <para> |
15029 | 203 Subscribe to the MPlayer-users mailing list: |
19709 | 204 <ulink url="http://lists.mplayerhq.hu/mailman/listinfo/mplayer-users"/> |
12622 | 205 and send your bug report to |
206 <ulink url="mailto:mplayer-users@mplayerhq.hu"/> where you can discuss it. | |
207 </para> | |
21521 | 208 |
12622 | 209 <para> |
12695 | 210 If you prefer, you can use our brand-new |
12664 | 211 <ulink url="http://bugzilla.mplayerhq.hu/">Bugzilla</ulink> instead. |
9675 | 212 </para> |
21521 | 213 |
9675 | 214 <para> |
21521 | 215 The language of this list is <emphasis role="bold">English</emphasis>. |
216 Please follow the standard | |
217 <ulink url="http://www.ietf.org/rfc/rfc1855.txt">Netiquette Guidelines</ulink> | |
218 and <emphasis role="bold">do not send HTML mail</emphasis> to any of our | |
219 mailing lists. You will only get ignored or | |
9675 | 220 banned. If you do not know what HTML mail is or why it is evil, read this |
21521 | 221 <ulink url="http://expita.com/nomime.html">fine document</ulink>. |
222 It explains all the details and has instructions for turning HTML off. Also | |
223 note that we will not individually CC (carbon-copy) people so it is a good idea | |
224 to subscribe to actually receive your answer. | |
9675 | 225 </para> |
226 </sect1> | |
227 | |
21521 | 228 |
229 <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --> | |
230 | |
231 | |
9675 | 232 <sect1 id="bugreports_what"> |
233 <title>What to report</title> | |
21521 | 234 |
9675 | 235 <para> |
236 You may need to include log, configuration or sample files in your bug report. | |
237 If some of them are quite big then it is better to upload them to our | |
19581 | 238 <ulink url="ftp://upload.mplayerhq.hu/MPlayer/incoming/">FTP server</ulink> in a |
9675 | 239 compressed format (gzip and bzip2 preferred) and include only the path and file |
240 name in your bug report. Our mailing lists have a message size limit of 80k, if | |
241 you have something bigger you have to compress or upload it. | |
242 </para> | |
243 | |
21521 | 244 <!-- ********** --> |
245 | |
9675 | 246 <sect2 id="bugreports_system"> |
247 <title>System Information</title> | |
21521 | 248 |
9675 | 249 <para> |
250 <itemizedlist> | |
251 <listitem><para> | |
21521 | 252 Your Linux distribution or operating system and version e.g.: |
9675 | 253 <itemizedlist> |
254 <listitem><para>Red Hat 7.1</para></listitem> | |
255 <listitem><para>Slackware 7.0 + devel packs from 7.1 ...</para></listitem> | |
256 </itemizedlist> | |
257 </para></listitem> | |
258 <listitem><para> | |
21521 | 259 kernel version: |
260 <screen>uname -a</screen> | |
9675 | 261 </para></listitem> |
262 <listitem><para> | |
21521 | 263 libc version: |
264 <screen>ls -l /lib/libc[.-]*</screen> | |
9675 | 265 </para></listitem> |
266 <listitem><para> | |
21521 | 267 gcc and ld versions: |
268 <screen> | |
9675 | 269 gcc -v |
21521 | 270 ld -v<!-- |
271 --></screen> | |
9675 | 272 </para></listitem> |
273 <listitem><para> | |
21521 | 274 binutils version: |
275 <screen>as --version</screen> | |
10111 | 276 </para></listitem> |
277 <listitem><para> | |
21521 | 278 If you have problems with fullscreen mode: |
9675 | 279 <itemizedlist> |
280 <listitem><para>Window manager type and version</para></listitem> | |
281 </itemizedlist> | |
282 </para></listitem> | |
283 <listitem><para> | |
21521 | 284 If you have problems with XVIDIX: |
9675 | 285 <itemizedlist> |
21521 | 286 <listitem><para> |
287 X colour depth: | |
21596 | 288 <screen>xdpyinfo | grep "depth of root"</screen> |
21521 | 289 </para></listitem> |
9675 | 290 </itemizedlist> |
291 </para></listitem> | |
292 <listitem><para> | |
21521 | 293 If only the GUI is buggy: |
9675 | 294 <itemizedlist> |
295 <listitem><para>GTK version</para></listitem> | |
296 <listitem><para>GLIB version</para></listitem> | |
297 <listitem><para>GUI situation in which the bug occurs</para></listitem> | |
298 </itemizedlist> | |
299 </para></listitem> | |
300 </itemizedlist> | |
301 </para> | |
302 </sect2> | |
303 | |
21521 | 304 <!-- ********** --> |
305 | |
9675 | 306 <sect2 id="bugreports_hardware"> |
307 <title>Hardware and drivers</title> | |
21521 | 308 |
9675 | 309 <para> |
310 <itemizedlist> | |
311 <listitem><para> | |
21521 | 312 CPU info (this works on Linux only): |
313 <screen>cat /proc/cpuinfo</screen> | |
9675 | 314 </para></listitem> |
315 <listitem><para> | |
21521 | 316 Video card manufacturer and model, e.g.: |
9675 | 317 <itemizedlist> |
318 <listitem><para>ASUS V3800U chip: nVidia TNT2 Ultra pro 32MB SDRAM</para></listitem> | |
319 <listitem><para>Matrox G400 DH 32MB SGRAM</para></listitem> | |
320 </itemizedlist> | |
321 </para></listitem> | |
322 <listitem><para> | |
21521 | 323 Video driver type & version, e.g.: |
9675 | 324 <itemizedlist> |
325 <listitem><para>X built-in driver</para></listitem> | |
326 <listitem><para>nVidia 0.9.623</para></listitem> | |
327 <listitem><para>Utah-GLX CVS 2001-02-17</para></listitem> | |
328 <listitem><para>DRI from X 4.0.3</para></listitem> | |
329 </itemizedlist> | |
330 </para></listitem> | |
331 <listitem><para> | |
21521 | 332 Sound card type & driver, e.g.: |
9675 | 333 <itemizedlist> |
334 <listitem><para>Creative SBLive! Gold with OSS driver from oss.creative.com</para></listitem> | |
335 <listitem><para>Creative SB16 with kernel OSS drivers</para></listitem> | |
336 <listitem><para>GUS PnP with ALSA OSS emulation</para></listitem> | |
337 </itemizedlist> | |
338 </para></listitem> | |
339 <listitem><para> | |
21521 | 340 If in doubt include <command>lspci -vv</command> output on Linux systems. |
9675 | 341 </para></listitem> |
342 </itemizedlist> | |
343 </para> | |
344 </sect2> | |
345 | |
21521 | 346 <!-- ********** --> |
347 | |
9675 | 348 <sect2 id="bugreports_configure"> |
349 <title>Configure problems</title> | |
21521 | 350 |
9675 | 351 <para> |
352 If you get errors while running <command>./configure</command>, or autodetection | |
353 of something fails, read <filename>configure.log</filename>. You may find the | |
354 answer there, for example multiple versions of the same library mixed on your | |
355 system, or you forgot to install the development package (those with the -dev | |
356 suffix). If you think there is a bug, include <filename>configure.log</filename> | |
357 in your bug report. | |
358 </para> | |
359 </sect2> | |
360 | |
18059 | 361 <sect2 id="bugreports_compilation"> |
9675 | 362 <title>Compilation problems</title> |
21521 | 363 |
9675 | 364 <para> |
365 Please include these files: | |
366 <itemizedlist> | |
21521 | 367 <listitem><para>config.h</para></listitem> |
368 <listitem><para>config.mak</para></listitem> | |
9675 | 369 </itemizedlist> |
370 </para> | |
371 </sect2> | |
372 | |
21521 | 373 <!-- ********** --> |
374 | |
9675 | 375 <sect2 id="bugreports_playback"> |
376 <title>Playback problems</title> | |
21521 | 377 |
9675 | 378 <para> |
21521 | 379 Please include the output of <application>MPlayer</application> at verbosity |
380 level 1, but remember to | |
381 <emphasis role="bold">not truncate the output</emphasis> when | |
9675 | 382 you paste it into your mail. The developers need all of the messages to properly |
383 diagnose a problem. You can direct the output into a file like this: | |
21521 | 384 <screen> |
385 mplayer -v <replaceable>options</replaceable> <replaceable>filename</replaceable> > mplayer.log 2>&1 | |
386 </screen> | |
9675 | 387 </para> |
388 | |
389 <para> | |
21521 | 390 If your problem is specific to one or more files, |
391 then please upload the offender(s) to: | |
19581 | 392 <ulink url="ftp://upload.mplayerhq.hu/MPlayer/incoming/"/> |
9675 | 393 </para> |
394 | |
395 <para> | |
396 Also upload a small text file having the same base name as your file with a .txt | |
21521 | 397 extension. Describe the problem you are having with the particular file there |
398 and include your email address as well as the output of | |
399 <application>MPlayer</application> at verbosity level 1. | |
400 Usually the first 1-5 MB of a file are enough to reproduce | |
11540 | 401 the problem, but to be sure we ask you to: |
21521 | 402 <screen> |
403 dd if=<replaceable>yourfile</replaceable> of=<replaceable>smallfile</replaceable> bs=1024k count=5 | |
404 </screen> | |
405 It will take the first five megabytes of | |
406 '<emphasis role="bold">your-file</emphasis>' and write it to | |
407 '<emphasis role="bold">small-file</emphasis>'. Then try again on | |
9675 | 408 this small file and if the bug still shows up your sample is sufficient for us. |
409 Please <emphasis role="bold">do not ever</emphasis> send such files via mail! | |
410 Upload it, and send only the path/filename of the file on the FTP-server. If the | |
21521 | 411 file is accessible on the net, then sending the |
412 <emphasis role="bold">exact</emphasis> URL is sufficient. | |
9675 | 413 </para> |
414 </sect2> | |
415 | |
21521 | 416 <!-- ********** --> |
417 | |
9675 | 418 <sect2 id="bugreports_crash"> |
419 <title>Crashes</title> | |
21521 | 420 |
9675 | 421 <para> |
422 You have to run <application>MPlayer</application> inside <command>gdb</command> | |
21521 | 423 and send us the complete output or if you have a <filename>core</filename> dump |
424 of the crash you can extract useful information from the Core file. Here's how: | |
9675 | 425 </para> |
426 | |
21521 | 427 |
9675 | 428 <sect3 id="bugreports_debug"> |
429 <title>How to conserve information about a reproducible crash</title> | |
21521 | 430 |
9675 | 431 <para> |
11540 | 432 Recompile <application>MPlayer</application> with debugging code enabled: |
9675 | 433 <screen> |
434 ./configure --enable-debug=3 | |
435 make | |
436 </screen> | |
11540 | 437 and then run <application>MPlayer</application> within gdb using: |
9675 | 438 <screen>gdb ./mplayer</screen> |
439 You are now within gdb. Type: | |
21521 | 440 <screen> |
441 run -v <replaceable>options-to-mplayer</replaceable> <replaceable>filename</replaceable> | |
442 </screen> | |
443 and reproduce your crash. As soon as you did it, gdb will return you to the | |
444 command line prompt where you have to enter | |
9675 | 445 <screen> |
446 bt | |
447 disass $pc-32 $pc+32 | |
448 info all-registers | |
449 </screen> | |
450 </para> | |
451 </sect3> | |
452 | |
21521 | 453 |
9675 | 454 <sect3 id="bugreports_core"> |
455 <title>How to extract meaningful information from a core dump</title> | |
21521 | 456 |
9675 | 457 <para> |
11049 | 458 Create the following command file: |
9675 | 459 <screen> |
460 bt | |
461 disass $pc-32 $pc+32 | |
462 info all-registers | |
463 </screen> | |
11049 | 464 Then simply execute this command: |
21521 | 465 <screen> |
466 gdb mplayer --core=core -batch --command=command_file > mplayer.bug | |
467 </screen> | |
9675 | 468 </para> |
469 </sect3> | |
470 </sect2> | |
471 </sect1> | |
472 | |
21521 | 473 |
474 <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --> | |
475 | |
476 | |
9675 | 477 <sect1 id="bugreports_advusers"> |
478 <title>I know what I am doing...</title> | |
21521 | 479 |
9675 | 480 <para> |
21521 | 481 If you created a proper bug report following the steps above and you are |
482 confident it is a bug in <application>MPlayer</application>, not a compiler | |
483 problem or broken file, you have already read the documentation and you could | |
484 not find a solution, your sound drivers are OK, then you might want to | |
485 subscribe to the MPlayer-advusers list and send your bug report there to get | |
486 a better and faster answer. | |
9675 | 487 </para> |
488 | |
489 <para> | |
490 Please be advised that if you post newbie questions or questions answered in the | |
21521 | 491 manual there, you will be ignored or flamed instead of getting an appropriate |
492 answer. So do not flame us and subscribe to -advusers only if you really know | |
493 what you are doing and feel like being an advanced | |
494 <application>MPlayer</application> user or developer. If you meet these | |
495 criteria it should not be difficult to find out how to subscribe... | |
9675 | 496 </para> |
497 </sect1> | |
498 | |
499 </appendix> |