Created page with "{{TopMenu}} {{Menu}} {{Menu.QA}} {{OrigLang|How to Report Bugs in LibreOffice}} == Grande passo! == Stai per compiere un apportare contributo a LibreOffice: un chiara segnal..."
New page
{{TopMenu}}
{{Menu}}
{{Menu.QA}}
{{OrigLang|How to Report Bugs in LibreOffice}}
== Grande passo! ==
Stai per compiere un apportare contributo a LibreOffice: un chiara segnalazione di bug è molto importante per aiutare i nostri sviluppatori. Quindi grazie!
Per rendere il processo più semplice, abbiamo preparato alcuni suggerimenti per aiutarti.
È estremamente importante sottoporre bug non ancora aggiunti negli strumenti di tracciamento dei bug.
Potrebbe esserci già una segnalazione aperta per il tuo problema, nel qual caso potresti aggiungervi utili commenti. Per farlo, visita
[https://bugs.freedesktop.org/duplicates.cgi?sortby=count&reverse=1&bug_id=46074%2C46901%2C36263%2C36677%2C46071%2C45081%2C44664%2C37488%2C40298%2C50552%2C50139%2C40571%2C46155%2C44720%2C39007%2C36301%2C49853%2C47044%2C46230%2C43989%2C37044%2C37024%2C34814%2C33463%2C33229%2C32664%2C50651%2C38244%2C37559%2C36496%2C36336%2C35972%2C34617%2C33114%2C32826%2C31716%2C31023%2C47963%2C47368%2C46687%2C45117%2C45020%2C44742%2C43869%2C42169%2C40261%2C39659%2C39093%2C37913%2C37654&sortvisible=0&product=LibreOffice&maxrows=100&changedsince=7 Most Frequently Reported Bugs for LibreOffice].
Entrambe
Both the
* [http://libreoffice.org/get-help/bug/ Bug Submission Assistant] (grandioso per le prime segnalazioni, attualmente non disponibile!) e
* the instructions on [[#Steps for reporting a bug with BugZilla|Steps for reporting a bug with BugZilla]],
ti assisteranno nel sottoporre le tue segnalazioni di bug.
(Guarda le sezioni seguenti per maggiori dettagli)
== General information ==
# Is the problem really a bug? If you require help using LibreOffice, consider reading the user documentation at [https://www.libreoffice.org/get-help/documentation/ Official LibreOffice Documentation]. And if you still require assistance, post your question at [http://nabble.documentfoundation.org/Users-f1639498.html LibreOffice Users Mailing List] or [http://ask.libreoffice.org/questions/ Ask.Libreoffice].
# If you are not sure what component your problem is about, choose the '''Libreoffice''' component. A bug triager will assign the proper component. For more information about that have a look at "[[QA/BugTriage|BugTriage]]". If it is a higher priority issue (broken parts, regression, etc), experienced users can assign it to one of the developers listed on the ''[[FindTheExpert]]'' page.
# If nobody reviewed your report within appropriate time (24 h for a critical bug 14 days for an enhancement request) consider asking someone else to reproduce your bug report on the [http://www.libreoffice.org/get-help/mailing-lists/ '''users'''@global.libreoffice.org mailing list], or [http://webchat.freenode.net/?channels=libreoffice on the #libreoffice IRC channel].
# Please file a separate bug report for each issue!
# Bugs in LibreOffice can be reported directly in '''{{Fdosubmit|Bugzilla}}'''.
== Steps for reporting a bug with BugZilla ==
# '''Before''' you submit a new bug report, please check for existing, similar bug reports on '''''[[BugReport_Details]]''''' under the correct Sub component (Click on the Sub component name under a Component heading to open a list with the currently reported Bugs).
A click on ⓘ leads you to help concerning the Subcomponents. With ''Edit Search'' at the bottom of the Bugzilla page you can modify the search according to your needs.
# If you find that the bug is not listed, start a new report. On [[BugReport_Details]] click the '►' behind the appropriate Sub component to open a Bugzilla bug report page prepared for your needs.
(If you did not find an appropriate Sub component, click the "for all other ...") Then:
## Select your LibreOffice version
## Select your Operating System
## Write your bug report mentioning the [[#What to include in bug reports | Bug Report]] and also [[BugReport_Details]].
## Decide what Severity might be appropriate for your report. Leave it where it is if you do not have much experience, the bug will not be fixed faster if you select blocker.
## Check in "possibly related Bugs" table on the Bug Report Page and additionally in the [https://bugs.freedesktop.org/duplicates.cgi?sortby=count&maxrows=100&changedsince=90&product=LibreOffice Duplicates Table] whether the problem really has not been reported yet.
# Click ''Submit'', and your report will be added to the Bugzilla database
'''Additional Hints'''
*If the Bugzilla bug tracking system seems daunting or too hard to understand, you should post your problem here [http://www.libreoffice.org/get-help/mailing-lists/ '''users@global.libreoffice.org''' LibreOffice user mailing list] or [http://libreofficeforum.org libreofficeforum.org]. Or, of course, try the [[#How to use the Bug Submission Assistant|Assistant]].
== Reporting Ubuntu bugs ==
To file an Ubuntu-specific bug, first check the [https://bugs.launchpad.net/ubuntu/+source/libreoffice current list of issues], then:
*If you're using Ubuntu 10.04 or Ubuntu 10.10 LibreOffice is unsupported. File the bug upstream at LibreOffice or update to Natty or later.
*If you're using Ubuntu 11.04 or later, open a terminal window (under Applications > Accessories > Terminal) and type '''ubuntu-bug libreoffice'''[Enter], then follow the prompts to complete the report. Alternatively use [https://bugs.launchpad.net/ubuntu/+source/libreoffice/+filebug this form].
Remember to include details such as how you installed LibreOffice, what platform you use (32-bit or 64-bit) and steps to reproduce the problem.
Filing a bug report at FreeDesktop.org as described above is also useful as such "upstream reports" can then be checked (and possibly tested and fixed) for other LibreOffice versions. Please file bugs at freedesktop.org, if it is not a Ubuntu-specific bug.
== Detailed explanation of bug reports content ==
The following information help us to reproduce or locate the problem and thus the fix might be available earlier for you:
* If you do not have much experience in bug reporting, please read the ''bug writing guidelines'', you will find a link at the top of the ''Enter Bug'' page!
*Use '''Correct''' selection for ''Component'', ''Version'', ''Initial Status'' and ''Severity'', please mind hints on '''''[[BugReport Details]]'''''.
:
*Additionally to pulldown selections details concerning system version and architecture, e.g. openSUSE 11.2 on x86_64, 32-bit Windows 7
**for Linux, what desktop, e.g. KDE or GNOME
:
*LibreOffice '''version''', e.g. 3.2.0. Get it from the the dialog "Help/About LibreOffice". If using a pre-built LibreOffice, on Linux tell the exact versions of LibreOffice packages in your package management system. For Windows, the exact file name of the installer, and from where downloaded.
** Additionally information concerning installed and used localization (UI language, document language) might be useful
**whether a 32-bit LibreOffice is used on a 64 bit (Linux) system
**the package source if it's not the official LibreOffice build
:
*Please contribute a '''meaningful ''Summary''''' for the problem you want to report. A very bad example would be "LibreOffice WRITER 3.4.5 Problem". Nearby all Bug reports are concerning a "Problem", ''Product'' Libereoffice, ''Version'' "3.4.5" and ''Component'' "Writer" are already known from the selectors, so that example would not contain any useful information. A useful Summary looks like "UI FILESAVE: no progress bar" using the pseudo key words from ''[[BugReport Details]]''. Additional examples:
**Not: "UI broken"
**But: Menu 'File -> Save as' not available (greyed out)
:Avoid short forms like "doesn't" or "isn't" to ease queries for strings in the Summary.
: If the report is concerning a ''crash'' or LibO stops responding ('''hangs'''), please add the word '''CRASH''' to the Summary line ("Heading" of the bug), so that these bugs can be tracked easily.
:
*'''Steps to reproduce the problem''', please mention that every little detail might be important. Describe 1 simple way how to reproduce your problem in a step by step instruction; numbered items will ease to reference to your observations for other users. Be very exact,
**do not write: "Open document"
**but: "In new empty LibO Spreadsheet document, use menu 'File -> Open (LibO dialog) - file type "Text documents" -> select attached sample document -> double click'
**Provide an exact description of your problem
***Not: "Formatting not correct"
***But like: "I expect ''xxx'' because of ''yyy'', but I see ''zzz''
:
*'''Other useful details''' (e.g. screenshots, sample documents, backtrace, strace). Please mention that your sample document might not show your problem if some other user opens it because he uses a different operating system, has other settings for LibO or something else. So a screenshot can help. Often a screenshot is more useful if you edit it (with DRAW) adding comments and marking relevant areas.
** Reference to an existing [http://www.openoffice.org/issues/query.cgi Openoffice.org bug] might be useful. Please mention: Active OOo Bugzilla has moved to [https://issues.apache.org/ooo/ Apache OOo Bugzilla]
* Attachments (sample documents, ...)
** If you want to attach more than one screenshot you should collect them all in 1 document (copy / paste to a DRAW document) and attach as a PDF. Please add a short comment to each screenshot to tell what you want to demonstrate with it.
** If you want to attach more than 1 document (a complete test kit, for example) you should create a .zip file containing all documents and attach that .zip.
** If your attachment is too big to be attached in Bugzilla (bigger than 1 MB) you can use the [[QA/Bugzilla-Attachments|experimental upload page]].
Note: if you create screenshots, it helps the developers if you switch the user interface to English first. You can do so in Tools -> Options -> Language Settings -> Languages.
== Providing extra information for the developers ==
=== How to get a backtrace (on Windows) ===
Read [[How to get a backtrace with WinDbg]] article and watch [http://www.youtube.com/watch?v=fppBTs215yc a screencast] video explaining how to get crash information for developers.
Please remember to copy the text you get to new document and attach it to bug report. That keeps the Bug readable and prevents from getting unusable results in Bugzilla queries.
=== How to get debug information (on Mac OS X)===
The debug information is useful for analysing the reasons why an application crashes or freezes. On Mac OS X, you can receive the standard debug information very simply, without installing any additional software. (This information even includes a simple stack trace, which misses full symbols, but can nevertheless be very useful.)
The exact steps vary depending on your Mac OS X version and setup, but in general you get the debug information as follows:
* When an application crashes, Mac OS X prompts you with a dialog window saying “LibreOffice quit unexpectedly.” and asks you if you want to send a report to Apple. Click on the button labelled “Report…”. Now a larger window with the title “Problem Report for LibreOffice” opens; under “Problem Details and System Configuration”, you find an edit field with a long text containing much technical details. You can just click into this long text, press Command-A to select all the text, then press Command-C to copy it and then switch to any text editor (e.g. Apple’s TextEdit) and press Command-V to insert the text. Then you can save the text as a new file; the best would be to use a plain text (.txt) format. Please attach that file to your bug report. (You do ''not'' need to send the report to Apple, so click on the “Don’t Send” in the “Problem Report” window.)
* When an application hangs or freezes, you can force quit it by pressing Command-Alt-Esc. Mac OS X prompts you with a dialog window entitled “Force Quit Applications”, asking which application(s) you want to quit; in that list, you can recognize the application which hangs or freezes often by the hint “(not responding)”. Select it and click the button “Force quit”. Depending on your system configuration, you will be asked if you want to send a report about that to Apple; if you confirm this, you will get the same “Problem Report” window as described above, and can copy and save the debug information text in the same way.
NB: It depends on your system configuration and user setup, if you will be asked at all about sending a report to Apple; it might be necessary to be logged in as an admin user to see these dialogs.
=== How to get a backtrace (on Linux)===
The backtrace is useful for analysing the reasons why an application crashes or freezes. You might use the following steps:
# Install the libreoffice*-debuginfo packages (on Debian, Ubuntu and derivated, the package name is libreoffice-dbg), if available. If you do not have them, the backtrace is much less useful, but still could potentially provide at least some information.
# Start a terminal / shell
# run soffice --backtrace
# reproduce your crasher, if you have a hang - make the application hang, and in another console type pkill -15 soffice.bin which will force a crash.
# Attach the gdbtrace.log file to the bug.
=== How to get a strace log (on Linux)
===
strace traces the system calls that a process makes. If there is some problem around file-I/O this can be a great way of detecting exactly what is going on at an operating-system level. It's also a fast way to see whether the program continues executing and/or has hung, and finding information about the system libreoffice is run on.
# start a terminal
# soffice --strace
# reproduce your problem
# compress the log: bzip2 strace.log
# now attach the strace.log.bz2 file that is produced to the bug report.
=== How to get a valgrind log (on Linux)===
The valgrind log is invaluable for tracing obscure memory corruption errors that can be extremely difficult to find otherwise. It achieves this by emulating a CPU, the slight downside of that is that the code runs around eighty (80x) slower, that will seem slow to you. The plus side is that it shows us problems that are un-findable in any other way, and that the traces produced very often pin-point the issue in such a way that it is rather easy for a developer to fix: your patience is much appreciated. Valgrind can also produce a number of false-positives.
# install the libreoffice*-debuginfo packages. (if available, and/or from your linux distribution)
# install the valgrind package
# start a terminal
# soffice --valgrind >& /tmp/valgrind.log
# be patient ... 80x is a lot slower ... reproduce the problem.
# attach /tmp/valgrind.log to the bug report.
----
[[Category:EN]]
[[Category:QA]]