2003-02-01 14:11:21 +00:00
|
|
|
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
|
|
|
|
|
|
2001-12-16 11:51:02 +00:00
|
|
|
|
<HTML>
|
2003-02-01 14:11:21 +00:00
|
|
|
|
<HEAD>
|
|
|
|
|
|
<TITLE>Zg<EFBFBD>aszanie b<><62>d<EFBFBD>w - MPlayer - The Movie Player for
|
|
|
|
|
|
Linux</TITLE>
|
|
|
|
|
|
<LINK rel="stylesheet" type="text/css" href="default.css">
|
|
|
|
|
|
<META http-equiv="Content-Type" content=
|
|
|
|
|
|
"text/html; charset=iso-8859-2">
|
|
|
|
|
|
</HEAD>
|
|
|
|
|
|
|
|
|
|
|
|
<BODY>
|
|
|
|
|
|
<H1><A name="appendix_b">Dodatek B - Jak zg<7A>asza<7A>
|
|
|
|
|
|
b<><62>dy</A></H1>
|
|
|
|
|
|
|
|
|
|
|
|
<P>Dobre raporty o b<><62>dach s<> niezwykle cennym wk<77>adem w rozw<7A>j
|
|
|
|
|
|
ka<6B>dego projektu. Ale dok<6F>adnie tak jak pisanie dobrego
|
|
|
|
|
|
oprogramowania, dobre raporty o b<><62>dach wymagaj<61> wysi<73>ku.
|
|
|
|
|
|
Prosimy o zdanie sobie sprawy z faktu i<> wi<77>kszo<7A><6F> programist<73>w
|
|
|
|
|
|
jest ekstremalnie zaj<61>ta i otrzymuje obscenicznie du<64>o list<73>w.
|
|
|
|
|
|
Wi<57>c chocia<69> Twoje informacje zwrotne s<> niezwykle cenne dla
|
|
|
|
|
|
udoskonalenia MPlayera, prosze zrozumie<69> <20>e musisz dostarczy<7A>
|
|
|
|
|
|
<B>wszystkie</B> informacje o kt<6B>re prosimy, oraz dok<6F>adnie
|
|
|
|
|
|
wykona<6E> intrukcje opisane w tym dokumencie.</P>
|
|
|
|
|
|
|
|
|
|
|
|
<H2><A name="fix">B.1 Jak naprawia<69> b<><62>dy</A></H2>
|
|
|
|
|
|
|
|
|
|
|
|
<P>Je<EFBFBD>li uwa<77>asz <20>e posiadasz niezb<7A>dne umiej<65>tno<6E>ci,
|
|
|
|
|
|
zapraszamy by spr<70>bowa<77> naprawi<77> b<><62>d samemu. A je<6A>li ju<6A> tak
|
|
|
|
|
|
zrobi<62>e<EFBFBD>, prosze przeczyta<74> <A href="tech/patches.txt">ten
|
|
|
|
|
|
kr<6B>tki dokument</A> by dowiedzie<69> si<73> jak sprawi<77> by Tw<54>j kod
|
|
|
|
|
|
zosta<74> do<64><6F>czony do MPlayera. Ludzie z listy dyskusyjnej <A
|
|
|
|
|
|
href=
|
|
|
|
|
|
"http://mplayerhq.hu/mailman/listinfo/mplayer-dev-eng">mplayer-dev-eng</A>
|
|
|
|
|
|
pomog<6F> Ci je<6A>li b<>dziesz mia<69> pytania.</P>
|
|
|
|
|
|
|
|
|
|
|
|
<H2><A name="report">B.2 Jak zg<7A>asza<7A> bl<62>dy?</A></H2>
|
|
|
|
|
|
|
|
|
|
|
|
<P>Przede wszystkim prosze spr<70>bowa<77> najnowsz<73> wersj<73> mplayera z
|
|
|
|
|
|
CVS, gdy<64> Tw<54>j problem mo<6D>e by<62> ju<6A> naprawiony. Program rozwija
|
|
|
|
|
|
si<73> niezwykle szybko, wi<77>kszo<7A><6F> problem<65>w zg<7A>aszonych po
|
|
|
|
|
|
wypuszczeniu oficjalnej wersji naprawiana jest w przeci<63>gu dni,
|
|
|
|
|
|
a nawet godzin. Prosimy wi<77>c by u<>ycwa<77> <B>wy<EFBFBD><EFBFBD>cznie wersji
|
|
|
|
|
|
CVS</B> przy zg<7A>aszaniu problem<65>w. Instrukcje dotycz<63>ce CVS
|
|
|
|
|
|
mo<6D>na znale<6C><65> na ko<6B>cu <A href=
|
|
|
|
|
|
"http://www.mplayerhq.hu/homepage/dload.html">tej strony</A>
|
|
|
|
|
|
b<>d<EFBFBD> w dokumencie README. Je<4A>li ta wersja nie rozwi<77><69>e
|
|
|
|
|
|
problem<65>w, prosimy skonsultowa<77> si<73> z <A href=
|
|
|
|
|
|
"documentation.html#known_bugs">lista znanych pluskiew</A> i
|
|
|
|
|
|
pozosta<74><61> cz<63><7A>ci<63> dokumentacji. Je<4A>li problem kt<6B>ry napotka<6B>e<EFBFBD>
|
|
|
|
|
|
nie jest znany b<>d<EFBFBD> nie rozwi<77>zuj<75> go nasze instrukcje, prosimy
|
|
|
|
|
|
o wys<79>anie raportu o b<><62>dzie.</P>
|
|
|
|
|
|
|
|
|
|
|
|
<P>Prosimy nie wysy<73>a<EFBFBD> raportu o b<><62>dach bezpo<70>rednio do
|
|
|
|
|
|
programist<73>w. MPlayer jest produktem rozwijanym przez grup<75>
|
|
|
|
|
|
programist<73>w, wiele os<6F>b mo<6D>e by<62> zainteresowanych raportem.
|
|
|
|
|
|
Czasami inni u<>ytkownicy mogli ju<6A> napotka<6B> b<><62>d z kt<6B>rym si<73>
|
|
|
|
|
|
borykasz, a nawet posiada<64> informacje jak go omin<69><6E>, nawet
|
|
|
|
|
|
je<6A>li to b<><62>d w kodzie MPlayera.</P>
|
|
|
|
|
|
|
|
|
|
|
|
<P>Prosimy o opisanie problemu dok<6F>adnie i z uwzgl<67>dnieniem
|
|
|
|
|
|
mo<6D>liwie najwi<77>kszej ilo<6C>ci szczeg<65><67><EFBFBD>w. Je<4A>li to mo<6D>liwe, pobaw
|
|
|
|
|
|
si<73> w detektywa by zaw<61>zi<7A> okoliczno<6E>ci przy kt<6B>rych wyst<73>puje
|
|
|
|
|
|
problem. Czy pluska daje zna<6E> o sobie tylko w jakich<63>
|
|
|
|
|
|
szczeg<65>lnych okoliczno<6E>ciach? Czy dotyczy tylko niekt<6B>rych
|
|
|
|
|
|
plik<69>w b<>d<EFBFBD> typ<79>w plik<69>w? Czy pojawia si<73> przy jednym kodeku
|
|
|
|
|
|
czy niezale<6C>nie od kodeka? Im wi<77>cej informacji dostarczysz tym
|
|
|
|
|
|
wi<77>ksze szanse na to <20>e naprawimy problem.
|
|
|
|
|
|
<!-- dot<6F>d przet<65>umaczone -->
|
|
|
|
|
|
</P>
|
|
|
|
|
|
|
|
|
|
|
|
<P>Please describe your problem in as much detail as possible.
|
|
|
|
|
|
Do a little detective work to narrow down the circumstances
|
|
|
|
|
|
under which the problem occurs. Does the bug only show up in
|
|
|
|
|
|
certain situations? Is it specific to certain files or file
|
|
|
|
|
|
types? Does it occur with only one codec or is it codec
|
|
|
|
|
|
independent? Can you reproduce it with all output drivers? The
|
|
|
|
|
|
more information you provide the better are our chances at
|
|
|
|
|
|
fixing your problem. Please do not forget to also include the
|
|
|
|
|
|
valuable information requested below, we will be unable to
|
|
|
|
|
|
properly diagnose your problem otherwise.</P>
|
|
|
|
|
|
|
|
|
|
|
|
<P>An excellent and well written guide to asking questions in
|
|
|
|
|
|
public forums is <A href=
|
|
|
|
|
|
"http://www.tuxedo.org/~esr/faqs/smart-questions.html">How To
|
|
|
|
|
|
Ask Questions The Smart Way</A> by <A href=
|
|
|
|
|
|
"http://www.tuxedo.org/~esr/">Eric S. Raymond</A>. There is
|
|
|
|
|
|
another called <A href=
|
|
|
|
|
|
"http://www.chiark.greenend.org.uk/~sgtatham/bugs.html">How to
|
|
|
|
|
|
Report Bugs Effectively</A> by <A href=
|
|
|
|
|
|
"http://www.chiark.greenend.org.uk/~sgtatham/">Simon
|
|
|
|
|
|
Tatham</A>. If you follow these guidelines you should be able
|
|
|
|
|
|
to get help. But please understand that we all follow the
|
|
|
|
|
|
mailing lists voluntarily in our free time. We are very busy
|
|
|
|
|
|
and cannot guarantee that you will get a solution for your
|
|
|
|
|
|
problem or even an answer.</P>
|
|
|
|
|
|
|
|
|
|
|
|
<H2><A name="where">B.3 Where to report bugs</A></H2>
|
|
|
|
|
|
|
|
|
|
|
|
<P>Subscribe to the mplayer-users mailing list:<BR>
|
|
|
|
|
|
<20><><EFBFBD><EFBFBD><A href=
|
|
|
|
|
|
"http://mplayerhq.hu/mailman/listinfo/mplayer-users">http://mplayerhq.hu/mailman/listinfo/mplayer-users</A><BR>
|
|
|
|
|
|
|
|
|
|
|
|
and send your bug report to:<BR>
|
|
|
|
|
|
<20><><EFBFBD><EFBFBD><A href=
|
|
|
|
|
|
"mailto:mplayer-users@mplayerhq.hu">mplayer-users@mplayerhq.hu</A></P>
|
|
|
|
|
|
|
|
|
|
|
|
<P>The language of this list is <B>English</B>. Please follow
|
|
|
|
|
|
the standard <A href=
|
|
|
|
|
|
"http://www.ietf.org/rfc/rfc1855.txt">Netiquette Guidelines</A>
|
|
|
|
|
|
and <B>do not send HTML mail</B> to any of our mailing lists.
|
|
|
|
|
|
You will only get ignored or banned. If you do not know what
|
|
|
|
|
|
HTML mail is or why it is evil, read this <A href=
|
|
|
|
|
|
"http://expita.com/nomime.html">fine document</A>. It explains
|
|
|
|
|
|
all the details and has instructions for turning HTML off. Also
|
|
|
|
|
|
note that we will not individually CC (carbon-copy) people so
|
|
|
|
|
|
it is a good idea to subscribe to actually receive your
|
|
|
|
|
|
answer.</P>
|
|
|
|
|
|
|
|
|
|
|
|
<H2><A name="what">B.4 What to report</A></H2>
|
|
|
|
|
|
|
|
|
|
|
|
<P>You may need to include log, configuration or sample files
|
|
|
|
|
|
in your bug report. If some of them are quite big then it is
|
|
|
|
|
|
better to upload them to our <A href=
|
|
|
|
|
|
"ftp://mplayerhq.hu/MPlayer/incoming/">FTP server</A> in a
|
|
|
|
|
|
compressed format (gzip and bzip2 preferred) and include only
|
|
|
|
|
|
the path and file name in your bug report. Our mailing lists
|
|
|
|
|
|
have a message size limit of 80k, if you have something bigger
|
|
|
|
|
|
you have to compress or upload it.</P>
|
|
|
|
|
|
|
|
|
|
|
|
<H3><A name="system">B.4.1 System Information</A></H3>
|
2002-05-12 05:54:29 +00:00
|
|
|
|
|
|
|
|
|
|
<UL>
|
2003-02-01 14:11:21 +00:00
|
|
|
|
<LI>
|
|
|
|
|
|
Your Linux distribution or operating system and version
|
|
|
|
|
|
e.g.:
|
|
|
|
|
|
|
|
|
|
|
|
<UL>
|
|
|
|
|
|
<LI>Red Hat 7.1</LI>
|
|
|
|
|
|
|
|
|
|
|
|
<LI>Slackware 7.0 + devel packs from 7.1 ...</LI>
|
|
|
|
|
|
</UL>
|
|
|
|
|
|
</LI>
|
|
|
|
|
|
|
|
|
|
|
|
<LI>kernel version:<BR>
|
|
|
|
|
|
<CODE>uname -a</CODE></LI>
|
|
|
|
|
|
|
|
|
|
|
|
<LI>libc version:<BR>
|
|
|
|
|
|
<CODE>ls -l /lib/libc[.-]*</CODE></LI>
|
|
|
|
|
|
|
|
|
|
|
|
<LI>X version:<BR>
|
|
|
|
|
|
<CODE>X -version</CODE></LI>
|
|
|
|
|
|
|
|
|
|
|
|
<LI>gcc and ld versions:<BR>
|
|
|
|
|
|
<CODE>gcc -v<BR>
|
|
|
|
|
|
ld -v</CODE></LI>
|
|
|
|
|
|
|
|
|
|
|
|
<LI>binutils version:<BR>
|
|
|
|
|
|
<CODE>as --version</CODE></LI>
|
|
|
|
|
|
|
|
|
|
|
|
<LI>
|
|
|
|
|
|
If you have problems with fullscreen mode:
|
|
|
|
|
|
|
|
|
|
|
|
<UL>
|
|
|
|
|
|
<LI>Window manager type and version</LI>
|
|
|
|
|
|
</UL>
|
|
|
|
|
|
</LI>
|
|
|
|
|
|
|
|
|
|
|
|
<LI>
|
|
|
|
|
|
If you have problems with XVIDIX:
|
|
|
|
|
|
|
|
|
|
|
|
<UL>
|
|
|
|
|
|
<LI>X colour depth:<BR>
|
|
|
|
|
|
<CODE>xdpyinfo | grep "depth of root"</CODE></LI>
|
|
|
|
|
|
</UL>
|
|
|
|
|
|
</LI>
|
|
|
|
|
|
|
|
|
|
|
|
<LI>
|
|
|
|
|
|
If only the GUI is buggy:
|
|
|
|
|
|
|
|
|
|
|
|
<UL>
|
|
|
|
|
|
<LI>GTK version</LI>
|
|
|
|
|
|
|
|
|
|
|
|
<LI>GLIB version</LI>
|
|
|
|
|
|
|
|
|
|
|
|
<LI>libpng version</LI>
|
|
|
|
|
|
|
|
|
|
|
|
<LI>GUI situation in which the bug occurs</LI>
|
|
|
|
|
|
</UL>
|
|
|
|
|
|
</LI>
|
2002-05-12 05:54:29 +00:00
|
|
|
|
</UL>
|
2003-02-01 14:11:21 +00:00
|
|
|
|
|
|
|
|
|
|
<H3><A name="hardware">B.4.2 Hardware and drivers</A></H3>
|
|
|
|
|
|
|
2002-05-12 05:54:29 +00:00
|
|
|
|
<UL>
|
2003-02-01 14:11:21 +00:00
|
|
|
|
<LI>CPU info (this works on Linux only):<BR>
|
|
|
|
|
|
<CODE>cat /proc/cpuinfo</CODE></LI>
|
|
|
|
|
|
|
|
|
|
|
|
<LI>
|
|
|
|
|
|
Video card manufacturer and model, e.g.:
|
|
|
|
|
|
|
|
|
|
|
|
<UL>
|
|
|
|
|
|
<LI>ASUS V3800U chip: nVidia TNT2 Ultra pro 32MB
|
|
|
|
|
|
SDRAM</LI>
|
|
|
|
|
|
|
|
|
|
|
|
<LI>Matrox G400 DH 32MB SGRAM</LI>
|
|
|
|
|
|
</UL>
|
|
|
|
|
|
</LI>
|
|
|
|
|
|
|
|
|
|
|
|
<LI>
|
|
|
|
|
|
Video driver type & version, e.g.:
|
|
|
|
|
|
|
|
|
|
|
|
<UL>
|
|
|
|
|
|
<LI>X built-in driver</LI>
|
|
|
|
|
|
|
|
|
|
|
|
<LI>nVidia 0.9.623</LI>
|
|
|
|
|
|
|
|
|
|
|
|
<LI>Utah-GLX CVS 2001-02-17</LI>
|
|
|
|
|
|
|
|
|
|
|
|
<LI>DRI from X 4.0.3</LI>
|
|
|
|
|
|
</UL>
|
|
|
|
|
|
</LI>
|
|
|
|
|
|
|
|
|
|
|
|
<LI>
|
|
|
|
|
|
Sound card type & driver, e.g.:
|
|
|
|
|
|
|
|
|
|
|
|
<UL>
|
|
|
|
|
|
<LI>Creative SBLive! Gold with OSS driver from
|
|
|
|
|
|
oss.creative.com</LI>
|
|
|
|
|
|
|
|
|
|
|
|
<LI>Creative SB16 with kernel OSS drivers</LI>
|
|
|
|
|
|
|
|
|
|
|
|
<LI>GUS PnP with ALSA OSS emulation</LI>
|
|
|
|
|
|
</UL>
|
|
|
|
|
|
</LI>
|
|
|
|
|
|
|
|
|
|
|
|
<LI>If in doubt include <CODE>lspci -vv</CODE> output on
|
|
|
|
|
|
Linux systems.</LI>
|
|
|
|
|
|
</UL>
|
|
|
|
|
|
|
|
|
|
|
|
<H3><A name="compilation">B.4.3 Compilation problems</A></H3>
|
|
|
|
|
|
Please include these files:
|
|
|
|
|
|
|
|
|
|
|
|
<UL>
|
|
|
|
|
|
<LI><CODE>config.h</CODE></LI>
|
|
|
|
|
|
|
|
|
|
|
|
<LI><CODE>config.mak</CODE></LI>
|
2002-05-12 05:54:29 +00:00
|
|
|
|
</UL>
|
2003-02-01 14:11:21 +00:00
|
|
|
|
Only if compilation fails below one of these directories,
|
|
|
|
|
|
include these files:
|
|
|
|
|
|
|
2002-05-12 05:54:29 +00:00
|
|
|
|
<UL>
|
2003-02-01 14:11:21 +00:00
|
|
|
|
<LI><CODE>Gui/config.mak</CODE></LI>
|
|
|
|
|
|
|
|
|
|
|
|
<LI><CODE>libvo/config.mak</CODE></LI>
|
|
|
|
|
|
|
|
|
|
|
|
<LI><CODE>libao2/config.mak</CODE></LI>
|
2002-05-12 05:54:29 +00:00
|
|
|
|
</UL>
|
2003-02-01 14:11:21 +00:00
|
|
|
|
|
|
|
|
|
|
<H3><A name="configure">B.4.4 Configure problems</A></H3>
|
|
|
|
|
|
Include <CODE>configure.log</CODE>.
|
|
|
|
|
|
|
|
|
|
|
|
<H3><A name="playback">B.4.5 Playback problems</A></H3>
|
|
|
|
|
|
|
|
|
|
|
|
<P>Please include the output of MPlayer at verbosity level 1,
|
|
|
|
|
|
but remember to <B>not truncate the output</B> when you paste
|
|
|
|
|
|
it into your mail. The developers need all of the messages to
|
|
|
|
|
|
properly diagnose a problem. You can direct the output into a
|
|
|
|
|
|
file like this:</P>
|
|
|
|
|
|
|
|
|
|
|
|
<P><CODE><EFBFBD><EFBFBD><EFBFBD><EFBFBD>mplayer -v [options] [filename] > mplayer.log
|
|
|
|
|
|
2>&1</CODE></P>
|
|
|
|
|
|
|
|
|
|
|
|
<P>If your problem is specific to one or more files, then
|
|
|
|
|
|
please upload the offender(s) to:</P>
|
|
|
|
|
|
|
|
|
|
|
|
<P><EFBFBD><EFBFBD><EFBFBD><EFBFBD><A href=
|
|
|
|
|
|
"ftp://mplayerhq.hu/MPlayer/incoming/">ftp://mplayerhq.hu/MPlayer/incoming/</A></P>
|
|
|
|
|
|
|
|
|
|
|
|
<P>Also upload a small text file having the same base name as
|
|
|
|
|
|
your file with a .txt extension. Describe the problem you are
|
|
|
|
|
|
having with the particular file there and include your email
|
|
|
|
|
|
address as well as the output of MPlayer at verbosity level 1.
|
|
|
|
|
|
Usually the first 1-5 MB of a file are enough to reproduce the
|
|
|
|
|
|
problem, but to be sure we ask you to:</P>
|
|
|
|
|
|
|
|
|
|
|
|
<P><CODE><EFBFBD><EFBFBD><EFBFBD><EFBFBD>dd if=yourfile of=smallfile bs=1024k
|
|
|
|
|
|
count=5</CODE></P>
|
|
|
|
|
|
|
|
|
|
|
|
<P>It will take the first five megabytes of
|
|
|
|
|
|
<STRONG>'your-file'</STRONG> and write it to
|
|
|
|
|
|
<STRONG>'small-file'</STRONG>. Then try again on this small
|
|
|
|
|
|
file and if the bug still shows up your sample is sufficient
|
|
|
|
|
|
for us. Please <STRONG>do not ever</STRONG> send such files via
|
|
|
|
|
|
mail! Upload it, and send only the path/filename of the file on
|
|
|
|
|
|
the FTP-server. If the file is accessible on the net, then
|
|
|
|
|
|
sending the <STRONG>exact</STRONG> URL is sufficient.</P>
|
|
|
|
|
|
|
|
|
|
|
|
<H3><A name="crash">B.4.6 Crashes</A></H3>
|
|
|
|
|
|
|
|
|
|
|
|
<P>You have to run MPlayer inside <CODE>gdb</CODE> and send us
|
|
|
|
|
|
the complete output or if you have a core dump of the crash you
|
|
|
|
|
|
can extract useful information from the <CODE>Core</CODE> file.
|
|
|
|
|
|
Here's how:</P>
|
|
|
|
|
|
|
|
|
|
|
|
<H4><A name="debug">B.4.6.1 How to conserve information about a
|
|
|
|
|
|
reproducible crash</A></H4>
|
|
|
|
|
|
Recompile MPlayer with debugging code enabled:
|
|
|
|
|
|
|
|
|
|
|
|
<P><CODE><EFBFBD><EFBFBD><EFBFBD><EFBFBD>./configure --enable-debug=3<BR>
|
|
|
|
|
|
<20><><EFBFBD><EFBFBD>make</CODE></P>
|
|
|
|
|
|
and then run MPlayer within gdb using:
|
|
|
|
|
|
|
|
|
|
|
|
<P><CODE><EFBFBD><EFBFBD><EFBFBD><EFBFBD>gdb ./mplayer</CODE></P>
|
|
|
|
|
|
You are now within gdb. Type:
|
|
|
|
|
|
|
|
|
|
|
|
<P><CODE><EFBFBD><EFBFBD><EFBFBD><EFBFBD>run -v [options-to-mplayer] filename</CODE></P>
|
|
|
|
|
|
and reproduce your crash. As soon as you did it, gdb will
|
|
|
|
|
|
return you to the command line prompt where you have to enter
|
|
|
|
|
|
|
|
|
|
|
|
<P><CODE><EFBFBD><EFBFBD><EFBFBD><EFBFBD>bt<BR>
|
|
|
|
|
|
<20><><EFBFBD><EFBFBD>disass $pc-32 $pc+32<BR>
|
|
|
|
|
|
<20><><EFBFBD><EFBFBD>info all-registers</CODE></P>
|
|
|
|
|
|
|
|
|
|
|
|
<H4><A name="core">B.4.6.2 How to extract meaningful
|
|
|
|
|
|
information from a core dump</A></H4>
|
|
|
|
|
|
|
|
|
|
|
|
<P>Please create the following command file:</P>
|
|
|
|
|
|
|
|
|
|
|
|
<P><CODE>disass $pc-32 $pc+32<BR>
|
|
|
|
|
|
info all-registers</CODE></P>
|
|
|
|
|
|
|
|
|
|
|
|
<P>Then simply execute the following on your command line:</P>
|
|
|
|
|
|
|
|
|
|
|
|
<P><EFBFBD><EFBFBD><EFBFBD><EFBFBD><CODE>gdb mplayer --core=core -batch
|
|
|
|
|
|
--command=command_file > mplayer.bug</CODE></P>
|
|
|
|
|
|
|
|
|
|
|
|
<H2><A name="advusers">B.5 I know what I am doing...</A></H2>
|
|
|
|
|
|
|
|
|
|
|
|
<P>If you created a proper bug report following the steps above
|
|
|
|
|
|
and you are confident it is a bug in MPlayer, not a compiler
|
|
|
|
|
|
problem or broken file, you have already read the documentation
|
|
|
|
|
|
and you could not find a solution, your sound drivers are OK,
|
|
|
|
|
|
then you might want to subscribe to the mplayer-advusers list
|
|
|
|
|
|
and send your bug report there to get a better and faster
|
|
|
|
|
|
answer.<BR>
|
|
|
|
|
|
<BR>
|
|
|
|
|
|
Please be advised that if you post newbie questions or
|
|
|
|
|
|
questions answered in the manual there, you will be ignored or
|
|
|
|
|
|
flamed instead of getting an appropriate answer.<BR>
|
|
|
|
|
|
So do not flame us and subscribe to -advusers only if you
|
|
|
|
|
|
really know what you are doing and feel like being an advanced
|
|
|
|
|
|
MPlayer user or developer. If you meet these criteria it should
|
|
|
|
|
|
not be difficult to find out how to subscribe...</P>
|
|
|
|
|
|
</BODY>
|
2001-12-16 11:51:02 +00:00
|
|
|
|
</HTML>
|
2003-02-01 14:11:21 +00:00
|
|
|
|
|
