[Ubuntu Wiki] Update of "LibreOfficeBugWrangling_it" by fabiomarconi

Ubuntu Wiki noreply at ubuntu.com
Wed May 9 19:52:28 UTC 2012


Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification.

The "LibreOfficeBugWrangling_it" page has been changed by fabiomarconi:
http://wiki.ubuntu.com/LibreOfficeBugWrangling_it

Comment:
Italian translation

New page:
<<Include(Debugging/Header)>>
||<tablestyle="float:right; font-size: 0.9em; width:30%; background:#F1F1ED; background-image: url('https://librarian.launchpad.net/1812570/bugsquad.png'); background-repeat: no-repeat; background-position:  98% 0.5ex; margin: 0 0 1em 1em; padding: 0.5em;">'''Contents'''<<BR>><<TableOfContents>>||

= Come fare una segnalazione =

 * Vi preghiamo di non segnalare bug inerenti LibreOffice senza avere prima letto questa pagina ed avere eseguito le necessarie azioni riportate in seguito. La mancata inosservanza causerà ritardi nell'indirizzamento della vostra segnalazione.
 * Vi preghiamo di segnalare tutti i vostri bug in LibreOffice eseguendo nel terminale: <<BR>> {{{ubuntu-bug <PACCHETTO>}}} <<BR>> <<BR>> dove <PACCHETTO> è lo specifico pacchetto nel quale è stato rinvenuto il problema. Per esempio, se si ha un problema importando un documento con Writer: <<BR>> {{{ubuntu-bug libreoffice-writer}}}
 * Un semplice modello di segnalazione di bug: <<BR>> 
||<tablestyle="background-color: #eee"> 1) lsb_release -rd <<BR>> <<BR>> 2) apt-cache policy libreoffice-writer <<BR>> <<BR>> 3) What is expected to happen in Writer is (cosa dovrebbe succedere) <PRECISE ISTRUZIONI PASSO-PASSO>. <<BR>> <<BR>> 4) What happened instead is...(cosa invece accade...) <<BR>> <<BR>> WORKAROUND: Perform the following steps:...||
 * Per cortesia non riportare più di un bug per ogni segnalazione.
 * Per cortesia evitare commenti sul tempo necessario alla riparazione, specialmente se non si sono seguiti i fondamentali passi di debugging in seguito descritti. Siate consapevoli che noi tutti vorremmo vedere i bug riparati immediatamente, ma purtroppo gli ostacoli maggiori si incontrano nella riproducibilità e chiarezza della segnalazione.

= Debugging Procedure =
== Document Issues ==

=== Bug importing a non-MS Office document ===
  * If you are reporting about importing a non-MS Office document, please attach the document to the bug report before opening in LibreOffice or in any other program. As well, please post a screenshot of how it looks in LibreOffice with a specific description about how it should look.

=== Bug exporting to MS Office ===
  * If you are reporting about how a document looks different exporting to MS Office, please attach the document to the bug report immediately after saving via LibreOffice, but before opening in MS Office. As well, please post a screenshot of how it looks in LibreOffice and then how it shows in MS Office.

=== Bug Importing from MS Office ===
  * If you are reporting about how a document looks importing from MS Office, please save the file in MS Office, then before opening in any other program, attach the document to the bug report. As well, please post a screenshot of how it looks in LibreOffice and then how it shows in MS Office.

=== Bug Exporting to Adobe PDF ===
  * If you are reporting about how a document looks exporting to Adobe Reader, please attach the file to the bug report before and after exporting to PDF. As well, provide screenshots of how it looks in LibreOffice and Adobe Reader.

=== Bug Importing PDF ===
  * If you are reporting about how a PDF document looks importing into Draw, please attach the file to the bug report before importing into Draw. As well, provide screenshots of how it looks in LibreOffice and Adobe Reader.

== Printing ==
 * For issues printing from LibreOffice please report this against cups first via the Terminal: <<BR>> {{{ubuntu-bug cups}}} <<BR>> <<BR>> It could end up being an issue with LibreOffice, but it's best to start with cups in order to rule it out. As well, please follow all steps noted in https://wiki.ubuntu.com/DebuggingPrintingProblems .

== Crashes ==
=== LibreOffice Crashes but System Still Functional ===
 * For instances when only LibreOffice crashes but you can still use the OS without hard rebooting, please report this via via Apport and ensure you have all the LibreOffice debug symbols installed (libreoffice-dbg, uno-libs3-dbg, and ure-dbg). For more on this please see https://wiki.ubuntu.com/Apport . As well, if this happened while a particular document was open or you were manipulating the document, please attach that document to the bug report with detailed, click-for-click steps on how to reproduce the crash.
 * In the rare instance that after you followed the above, apport did not kick in, please provide a backtrace, valgrind, and strace following https://wiki.ubuntu.com/DebuggingProgramCrash .

=== The Whole System Hangs or Boots to the Login Screen ===
 * For instances when your using LibreOffice and either the system hangs requiring a hard reset or your booted to the login screen, this is a bug in either xorg or the kernel. Please follow https://help.ubuntu.com/community/DebuggingSystemCrash . As well, if this happened while a particular document was open or you were manipulating the document, please attach that document to the bug report with detailed, click-for-click steps on how to reproduce the crash.

== Regressions ==
 * For regressions, it is helpful to perform a binary bisect ("bibisect") to narrow down which commit specifically caused the problem. For instructions please see http://sweetshark.livejournal.com/7683.html .

== Wishlists ==
 * For Wishlist reports, many of these are requests to implement a feature in LibreOffice found in MS Office. A broad but good rule of thumb is if you want LibreOffice to do something that MS Office does (MS Office compatibility expectation), please document how specifically MS Office does it, then how LibreOffice does not or does not do well that which you desire. Please keep in mind, pocket cases exist where LibreOffice intentionally does not do what MS Office does (ex. leap year implementation https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/456100).

= Triaging LibreOffice Bugs =

== Writer and Calc ==
 * For bugs in Writer, it is helpful to check to see if the problem exists in AbiWord. For bugs in Calc, it is helpful to check to see if the problem exists in Gnumeric. Sometimes, AbiWord and Gnumeric give the bug reporter a usable workaround to the problem (and vice versa). If a workaround is found, feel free to document it in the report. As well, while not quite apples and oranges code wise, it gives LibreOffice developers code to base a patch on.

== Wishlist Reports ==
 * For Wishlist reports, they most likely should be marked Won't Fix Wishlist. This is due to how Ubuntu diverts very little from the LibreOffice upstream source release, and upstream's rapid maintenance cadence. <<BR>> A Won't Fix Wishlist stock reply:

||<tablestyle="background-color: #eee">Thank you for reporting this and helping making Ubuntu better. Regarding this report:<<BR>>- This is a clearcut upstream issue. Your welcome to send this to the developers of the software by following the instructions at http://wiki.documentfoundation.org/BugReport . If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status.<<BR>>- Marking LibreOffice Packaging and libreoffice (Ubuntu) => Won't Fix Wishlist. This does not mean the issue will not be cared about, but if it is cared about (even by Ubuntu/Canonical contributors), it is done upstream at LibreOffice.||

== How to Forward Bugs Upstream ==
 * Once marked Triaged, a report may be filed upstream using the [[https://www.libreoffice.org/get-help/bug/|LibreOffice Bug Submission Assistant]] <<FootNote(Or in the old fashioned way at https://bugs.freedesktop.org/enter_bug.cgi?product=LibreOffice)>>.

  * Once a remote bug watch has been added to a bug report, it is helpful to append [Upstream] to the beginning of the bug title. This helps in searching for bugs reports by title. Please do not append this unless a remote bug watch has been added to the report as this creates confusion on which bugs have been reported upstream and which have not.

----
CategoryBugSquad
CategoryDebugging



More information about the Ubuntu-bugsquad mailing list