Update userguide from i18n.haiku-os.org.
This commit is contained in:
Niels Sascha Reedijk
@@ -4,7 +4,7 @@
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2010, Haiku. All rights reserved.
|
||||
* Copyright 2008-2012, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
@@ -53,76 +53,77 @@
|
||||
<div class="box-info">Preklad tejto stránky zatiaľ nie je dokončený. Dovtedy sa nedokončené časti zobrazia v anglickom origináli.</div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>Nahlasovanie chýb</td></tr>
|
||||
<tr class="index"><td><a href="#account">Getting a Trac account</a><br />
|
||||
<a href="#report">Creating a bug report</a><br />
|
||||
<a href="#app">Application bugs</a><br />
|
||||
<a href="#server">Server bugs</a><br />
|
||||
<a href="#kernel">Kernel bugs</a><br />
|
||||
<tr class="heading"><td>Index</td></tr>
|
||||
<tr class="index"><td><a href="#account">Získanie účtu v Trac</a><br />
|
||||
<a href="#report">Vytvorenie hlásenia o chybe</a><br />
|
||||
<a href="#app">Chyby aplikácií</a><br />
|
||||
<a href="#server">Chyby serverov</a><br />
|
||||
<a href="#kernel">Chyby jadra</a><br />
|
||||
<a href="#kdl">Kernel Debugging Land - KDL</a><br />
|
||||
<a href="#syslog">Syslog</a><br />
|
||||
<a href="#onscreen">On screen debug output</a><br />
|
||||
<a href="#hardware">Hardware/Driver bugs</a><br />
|
||||
<a href="#next">What's next?</a></td></tr>
|
||||
<a href="#onscreen">Výstup ladenia na obrazovku</a><br />
|
||||
<a href="#hardware">Chyby hardvéru/ovládačov</a><br />
|
||||
<a href="#next">Čo ďalej?</a></td></tr>
|
||||
</table>
|
||||
|
||||
<h1>Nahlasovanie chýb</h1>
|
||||
|
||||
<p>Since our developers are unable to test every hardware combination, nor every different way of interacting with the operating system, we are relying on users to give us some input on how things work at their end. Since Haiku is still quite young, it's very likely that you will encounter bugs. We thank you for taking the time to report these. Together we can improve Haiku, bit by bit.</p>
|
||||
<p>To keep our bugtracker effective, it's essential to abide by the <a href="http://dev.haiku-os.org/wiki/BugTrackerEtiquette">Bug Tracker Etiquette</a>.</p>
|
||||
<p>Keďže je nemožné, aby naši vývojári otestovali každú kombináciu hardvéru či každý možný spôsob interakcie s operačným systémom, spoliehame sa na našich používateľov, aby nám poslali spätnú väzbu ako veci fungujú u nich. Keďže Haiku je stále relatívne mladé, je veľmi pravdepodobné, že narazíte na chyby. ďakujeme vám za čas, ktorý venujete ich nahláseniu. Spolu môžeme Haiku vylepšovať, trochu po troche.</p>
|
||||
<p>Aby bol náš nástroj na sledovanie chýb fungoval efektívne, je nevyhnutné dodržiavať <a href="http://dev.haiku-os.org/wiki/BugTrackerEtiquette">Etiketu nástroja na sledovanie chýb</a>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="account" name="accout">Getting a Trac account</a></h2>
|
||||
<p>To file a ticket, you need to have an account at <a href="http://dev.haiku-os.org/register" title="Register at Haiku's Bugtracker">Haiku's Bugtracker</a>.<br />
|
||||
When creating a new account, be certain to <b>provide your email address</b> as it is necessary to obtain basic ticket modification privileges. Be sure to <b>check your spam folder</b> shortly afterwards, as the all important verification mail often ends up there.</p>
|
||||
<a id="account" name="accout">Získanie účtu v Trac</a></h2>
|
||||
<p>Aby ste mohli založiť hlásenie, musíte mať účet v <a href="http://dev.haiku-os.org/register" title="Registrácia v nástroji na sledovanie chýb Haiku">Nástroji na sledovanie chýb Haiku</a>.<br />
|
||||
Pri vytváraní účtu určite poskytnite <b>vašu emailovú adresu</b>, pretože je potrebné získať základné oprávnenia na zmenu hlásení. Určite sa krátko potom <b>pozrite aj do spamového priečinka</b>, pretože dôležité overovacie emaily tam často skončia.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="report" name="report">Creating a bug report</a></h2>
|
||||
<p>Before reporting a bug, please <a href="http://dev.haiku-os.org/query?status=new&status=assigned&status=reopened&status=closed&summary=%7Etext+you+want+to+search+for&order=priority">make sure</a> that it does not yet exist. You can also use the <a href="http://dev.haiku-os.org/search?q=&noquickjump=1&ticket=on">search</a> function for this.<br />
|
||||
After you have established that it's a unique bug, make your information as accurate as possible:</p>
|
||||
<a id="report" name="report">Vytvorenie hlásenia o chybe</a></h2>
|
||||
<p>Pred nahlásením chyby sa prosím <a href="http://dev.haiku-os.org/query?status=new&status=assigned&status=reopened&status=closed&summary=%7Etext+you+want+to+search+for&order=priority">uisitite</a>, že už nebola nahlásená. Tiež na to môžete použiť funkciu <a href="http://dev.haiku-os.org/search?q=&noquickjump=1&ticket=on">hľadanie</a>.<br />
|
||||
Potom, ako ste sa uistili, že chyba je jedinečná, uveďte čo najpresnejšie vaše informácie:</p>
|
||||
<ul>
|
||||
<li><p>Attempt to reproduce your issue on the current revision of Haiku. Pre-built images for testing purposes are <a href="http://haiku-files.org/">available</a>.</p></li>
|
||||
<li><p>Include basic information such as how you are testing Haiku (on real hardware, on VMWare, on QEMU, etc.).</p></li>
|
||||
<li><p>Mention which revision from <acronym title="Subversion, the source code management system we use">SVN</acronym> you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
|
||||
<li><p>Describe the problem you are experiencing. Try to be as accurate as you can: describe the actual behavior, and the behavior you expected.</p></li>
|
||||
<li><p>Describe what steps you need to perform in order to expose the bug. This will help developers reproduce the bug.</p></li>
|
||||
<li><p>Attach as much information as you have. If it is a GUI bug, or a bug in one of the applications, try to take a screenshot by pressing the <span class="key">PRINT</span> key.</p></li>
|
||||
<li><p>Pokúste sa reprodukovať problém v aktuálnej revízii Haiku. Sú pripravené <a href="http://haiku-files.org/">obrazy na testovacie účely</a>.</p></li>
|
||||
<li><p>iveďte základné infomrácie o tom ako testujete Haiku (na skutočnom hardvéri, vo VMWare, v QEMU atď.).</p></li>
|
||||
<li><p>Uveďte, ktorú revíziu zo <acronym title="Subversion, nástroj na správu zdrojového kódu, ktorý používame">SVN</acronym> používate. Túto informáciu nájdete v dialógu <span class="menu">O Haiku...</span> z menu Panela. Tiež uvete, aký druh Haiku testujete (gcc2, gcc4, gcc2hybrid, gcc4hybrid). Obsazy na stiahnutie sú podľa toho pomenované; pri obraze, ktorý ste zostavili sami by ste mali vedieť ako ste ho zostavili.</p></li>
|
||||
<li><p>Popíšte váš problém. Skúste byč čo najpresnejší: popíšte správanie, ktoré ste očakávali a správanie, ktoré ste dostali.</p></li>
|
||||
<li><p>Popíšte kroky, ktoré je potrebné vykonať na vyvolanie chyby. To pomôže vývojárom chybu reprodukovať.</p></li>
|
||||
<li><p>Priložte všetky informácie,ktoré máte k dispozícii. Ak je to chyba používateľského rozhrania alebo chyba v niektorej z aplikácií, skúste urobiť snímku obrazovky stlačením klávesu <span class="key">Print Screen</span>.</p></li>
|
||||
</ul>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="app" name="app">Application bugs</a></h2>
|
||||
<p>When an application crashed, you should invoke the debugger from the alert that pops up. This will open a Terminal window with gdb (the GNU debugger) running in it. Entering <span class="cli">bt</span>, you create a "backtrace" that you should copy in its entirety (including the part before you entered the <span class="cli">bt</span> command) and attach it to the ticket.</p>
|
||||
<a id="app" name="app">Chyby aplikácií</a></h2>
|
||||
<p>Keď aplikácia havaruje, mali by ste vyvolať ladiaci nástroj z upozornenia, ktoré vyskočí. To otvorí okno Terminálu, v ktorom beží gdb (GNU debugger). Zadaním <span class="cli">bt</span> vytvoríte „backtrace“, ktorý by ste mali kompletne skopírovať (vrátane časti zorbazenej než ste zadali príkaz <span class="cli">bt</span>) a priložiť ho k hláseniu.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="server" name="server">Server bugs</a></h2>
|
||||
<p>When vital servers like the app server, the registrar or the input server crash, you won't see the usual crash alert. Instead the whole screen will be cleared white and a gdb session will be started, its output appearing directly on screen. Likely you will still be able to move the mouse, which will overwrite the white and gdb output on screen. Applications still running (like ProcessController or the clock in the Deskbar) might also draw over the debugger output on screen.<br />
|
||||
Besides everything being more ugly and inconvenient, basically the same applies as for application bugs. Most importantly procure a back trace (<span class="cli">bt</span> command). You may need to take a picture of the screen with a digital camera, since you won't be able to copy the text anywhere.</p>
|
||||
<a id="server" name="server">Chyby serverov</a></h2>
|
||||
<p>Ak havarujú dôležité servery ako aplikačný server, registrátor alebo server vstupu, neuvidíte zvyčajné upozornenie na haváriu. Namiesto toho sa celá obrazovka zmaže na bielu farbu, spustí sa relácia gdb a jej výstup sa objaví priamo na obrazovke. Pravdepodobne budete môcť pohybovať myšou, čo prepíše bielu farbu a výstup gdb na obrazovke. Aplikácie, ktoré ešte bežia (ako ProcessController alebo hodiny v Paneli) tiež možno prekreslia časť ladiaceho výstupu na obrazovke.<br />
|
||||
Okrem toho, že je všetko škaredšie a nepohodlné platí prakticky to isté ako pri chybách aplikácií. Predovšetkým získajte backtrace (príkaz <span class="cli">bt</span>). Možno budete musieť odfotiť obrazovku digitálnym fotoaparátom, pretože nebudete môcť text nikam skopírovať.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kernel" name="kernel">Kernel bugs</a></h2>
|
||||
<p>Kernel bugs are usual the ones with the most severe effects while at the same time being the hardest to debug. There are different kinds of symptoms, which most likely point to a kernel or driver issue:</p>
|
||||
<a id="kernel" name="kernel">Chyby jadra</a></h2>
|
||||
<p>Chyby jadra sú zvyčajne tie, ktoré majú najzávažnejší vplyv a zároveň sa najťažšie ladia. Existujú rôzne druhy symptómov, ktoré pravdepodobne naznačujú problém s jadrom alebo ovládačom:</p>
|
||||
<ul>
|
||||
<li><p>The system enters kernel debugging land (KDL) on its own volition. The upper part of the screen is cleared white and several lines of text are printed on it. The second line says "<i>Welcome to Kernel Debugging Land...</i>", the one above it states the immediate reason for entering KDL.</p></li>
|
||||
<li><p>The system reboots spontaneously.</p></li>
|
||||
<li><p>The system freezes completely. You can't move the mouse and no application draws anything anymore. An important test in that situation is, whether you still can enter KDL via the shortcut <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span> (<span class="key">SysReq</span> being <span class="key">PRINT</span> on most keyboards). Wait at least a minute to see, if anything happens.</p></li>
|
||||
<li><p>The system doesn't boot up correctly. It may reboot spontaneously or stop at some point (e.g. at some icon of the boot screen). In the latter case also try <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.</p></li>
|
||||
<li><p>The whole system or some piece of hardware doesn't behave correctly. For example, it could be very slow, errors occur, or something doesn't work at all. If some hardware doesn't work at all, the first obvious check is whether Haiku supports it at all at the moment (e.g. ask on a mailing list or a forum).</p></li>
|
||||
<li><p>Systém svojvoľne vstúpi KDL (kernel debugging land). Horná časť obrazovky sa vyčistí do biela a vypíše sa na ňu niekoľko riadkov textu. Druhý riadok bude obsahovať „<i>Welcome to Kernel Debugging Land...</i>“ a ten nad ním bude obsahovať okamžitý dôvod, prečo bolo vyvolané KDL.</p></li>
|
||||
<li><p>Systém sa spontánne reštartuje.</p></li>
|
||||
<li><p>Systém kompletne zamrzne. Nemôžete hýbať myšou a žiadna aplikácia nič nevykresľuje. Dôležitý test v tejto situácii je, či ešte môžete vyvolať KDL klávesovou skratkou <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span> (<span class="key">SysReq</span> je na väčšine klávesníc <span class="key">PRINT</span>). Počkajte aspoň minútu, aby ste uvideli, či sa niečo stane.</p></li>
|
||||
<li><p>Systém nenaštartuje korektne. Môže spontánne naštartovať alebo v niektorom bode zastaviť (napr. na niektorej ikone štartovacej obrazovky). V druhom prípade tiež skúste <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.</p></li>
|
||||
<li><p>Celý systém alebo niektorá časť hardvéru sa nespráva korektne. Napríklad môže byť veľmi pomalý, vyskytnú sa chyby alebo niečo vôbec nefunguje. Ak nejaký hardvér vôbec nefunguje, prvá vec, ktorú treba skontrolovať je, či ho momentálne Haiku vôbec podporuje (napr. spýtať sa v poštovej konferencii alebo na fóre).</p></li>
|
||||
</ul>
|
||||
<p>Note that while only the last point seems to indicate hardware relation, all the other symptoms could be caused by a bug in a hardware driver as well. If you have a suspicion what piece of hardware or corresponding driver might have to do with the problem, check whether removing/disabling the hardware or the driver makes a difference. For example, if you suspect Wifi you may find that your BIOS has an option to disable it. Or if not, you could remove the responsible Wifi driver from your Haiku installation (in <span class="path">/boot/system/add-ons/kernel/drivers/bin</span>).</p>
|
||||
<p>pamätajte, že hoci iba posledný bod indikuje súvislosť s hardvérom, všetky ostatné symptómy môžu byť spôsobené aj chybou v ovládači hardvéru. Ak máte podozrenie, ktorá časť hardvéru alebo zodpovedajúci ovládač môže súvisieť s problémom, skontrolujte, či odstránenie alebo vypnutie hardvéru či ovládača pomôže. Napríklad ak podozrievate Wi-Fi, možno zistíte, že váš BIOS umožňuje ju vypnúť. Alebo ak nie, môžete odstrániť príslušný ovládač Wi-Fi z vašej inštalácie Haiku (v <span class="path">/boot/system/add-ons/kernel/drivers/bin</span>).</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kdl" name="kdl">Kernel Debugging Land - KDL</a></h3>
|
||||
<p>If the system hasn't entered KDL by itself, you can do that intentionally by invoking the keyboard shortcut <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.<br />
|
||||
Note that in KDL your keyboard may not work. PS/2 keyboards always do, USB keyboards connected via UHCI controllers do only, if one has entered KDL via the keyboard shortcut at least once. USB OHCI is not supported at the moment.</p>
|
||||
<p>KDL itself is a kind of a shell. One can execute commands that print information about the system. The following commands might be of interest:</p>
|
||||
<p>Ak systém sám nevstúpil do KDL, môžete ho úmyselne vyvolať klávesovou skratkou <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.<br />
|
||||
Pamätajte, že v KDL vaša klávesnica nemusí fungovať. Klávesnice PS/2 fungujú vždy, klávesnice USB pripojené prostredníctvom ovládačov UHCI fungujú iba ak už aspoň raz ste vstúpili do KDL použitím klávesovej skratky. USB OHCI momentálne nie je podporované.</p>
|
||||
<p>Samotné KDL je istým druhom shellu. Môžete vykonávať príkazy, ktoré vypisujú informácie o systéme. Nasledovné príkazy môžu byť zaujímavé:</p>
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td><span class="cli">bt</span> (aka sc)</td><td> </td><td>Prints a back trace. If the system entered KDL on its on volition, always enter that one.</td></tr>
|
||||
<tr><td><span class="cli">ints</span></td><td> </td><td>Shows the handled and unhandled hardware interrupts.</td></tr>
|
||||
<tr><td class="onelinetop"><span class="cli">co</span> (aka continue)</td><td> </td><td>Leaves the kernel debugger and continues normal operation of the system, if that is possible.</td></tr>
|
||||
<tr><td><span class="cli">reboot</span></td><td> </td><td>Reboots the system immediately. You will lose all unsaved data and even those that have been saved, but have not yet been written back to disk.</td></tr>
|
||||
<tr><td><span class="cli">bt</span> (resp. sc)</td><td> </td><td>Vypíše backtrace. Ak systém svojvoľne vstúpil do KDL, vždy ho spustite.</td></tr>
|
||||
<tr><td><span class="cli">ints</span></td><td> </td><td>Zobrazí ošetrené a neošetrené hardvérové prerušenia.</td></tr>
|
||||
<tr><td class="onelinetop"><span class="cli">co</span> (resp. continue)</td><td> </td><td>Opustí ladenie jadra a pokračuje v normálnej prevádzke systému ak je to možné.</td></tr>
|
||||
<tr><td><span class="cli">reboot</span></td><td> </td><td>Okamžite reštartuje systém. Stratíte všetky neuložené dáta a aj tie, ktoré už boli uložené, ale zatiaľ neboli zapísané na disk.</td></tr>
|
||||
</table>
|
||||
<p>For more information, see the article <a href="http://www.haiku-os.org/documents/dev/welcome_to_kernel_debugging_land">Welcome to Kernel Debugging Land</a>.</p>
|
||||
<p>The KDL output is written to the serial port (if you have one, a respective cable, and a second computer to connect with, you can capture the output there via a terminal program) and to the syslog. If you can't leave KDL it won't be written to the syslog file, though. There's a boot loader debug option that allows you to capture it nonetheless (see below).</p>
|
||||
<p>Ďalšie informácie nájdete v článku <a href="http://www.haiku-os.org/documents/dev/welcome_to_kernel_debugging_land">Welcome to Kernel Debugging Land</a>.</p>
|
||||
<p>Výstup KDL sa zapisuje na sériový port (ak ho máte a ak máte príslušný kábel na pripojenie druhého počítača, môžete prostredníctvom neho zachytiť výstup pomocou terminálového programu) a do syslogu. Ak nemôžete opustiť KDL, nezapíše však sa do súboru syslog. Existuje voľba zavádzača systému, ktorá vám umožňuje zachytiť ho napriek tomu (pozri nižšie).</p>
|
||||
<p>You can generate QR codes from KDL output that can then be converted to text using smartphones or similar devices. See the blog post <a href="http://www.haiku-os.org/blog/mmlr/2012-07-01_qr_encode_your_kdl_output">QR Encode your KDL Output</a> on how to get data out of KDL using that feature.</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="syslog" name="syslog">Syslog</a></h3>
|
||||
@@ -132,14 +133,14 @@ The syslog (short for system log) contains valuable information about what has h
|
||||
In the boot loader's <span class="menu">Debug menu</span> you should now find the entries <span class="menu">Display syslog from previous session</span> and <span class="menu">Save syslog from previous session</span>. The former displays the syslog on screen, the latter allows you to save it as a file to disk. Note that at the moment only FAT32 volumes are supported for saving the file. If you want to use a USB stick, but have plugged it in too late so that it isn't recognized yet, you can reset the machine and re-enter the boot loader menu. But again: Don't accidentally boot any operating system or the data will be lost.</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="onscreen" name="onscreen">On screen debug output</a></h3>
|
||||
<a id="onscreen" name="onscreen">Výstup ladenia na obrazovku</a></h3>
|
||||
<p><b>The on-screen debug output is useful only for debugging very specific issues and is known to have (timing) issues. Don't use it, if you don't have to.</b><br />
|
||||
This is only relevant when Haiku fails to boot on your machine and the <span class="menu">Debug syslog option</span> doesn't work for some reason. Before the Haiku boot logo appears, hold <span class="key">SHIFT</span> to enter the boot loader menu. Select <span class="menu">Select safe mode options</span>. Near the bottom, <span class="menu">[ ] Enable on screen debug output</span> will be listed. (Note: The other options could be enabled in an attempt to boot Haiku. If Haiku will boot only when one or more options are activated, be sure to mention which ones.)<br />
|
||||
Finally select <span class="menu">Return to main menu</span> and then <span class="menu">Continue booting</span>.<br />
|
||||
One or more pages of text will display on the screen, only the last few lines need to be included on your ticket. There's more information on the <a href="../../../userguide/sk/bootloader.html">Boot Loader</a>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="hardware" name="hardware">Hardware/Driver bugs</a></h2>
|
||||
<a id="hardware" name="hardware">Chyby hardvéru/ovládačov</a></h2>
|
||||
<p>When dealing with a hardware/driver related bug, you should attach the following information as text files:</p>
|
||||
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
@@ -154,7 +155,7 @@ One or more pages of text will display on the screen, only the last few lines ne
|
||||
<p>The first four commands are entered into Terminal. Add a <span class="cli"> > output.txt</span> after a command, and it's piped into a text file called "output.txt" that you can attach to your bug report or email.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="next" name="next">What's next?</a></h2>
|
||||
<a id="next" name="next">Čo ďalej?</a></h2>
|
||||
<p>After the bug has been reported, a developer will look at your bug and try to classify it. Remember, we are all volunteers, and as such, sometimes a bug report might go unanswered for a while. Adding new information when it becomes available usually helps getting a bug picked up quicker, but do not try to 'bump' the bug up by adding
|
||||
non-descriptive comments.</p>
|
||||
<p>Remember, reporting a bug is not something you spend a little time on and then you are done. If you reported a bug, then you are part of the Haiku development process. Developers might come up with questions while they are trying to fix your bug. Please stay around to answer these. Consider your participation 'done' when the bug is marked
|
||||
|
||||
Reference in New Issue
Block a user