[Ubuntu Wiki] Update of "LibreOfficeBugWrangling" by penalvch

Ubuntu Wiki noreply at ubuntu.com
Fri Apr 6 21:48:56 UTC 2012


Dear Wiki user,

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

The "LibreOfficeBugWrangling" page has been changed by penalvch:
http://wiki.ubuntu.com/LibreOfficeBugWrangling?action=diff&rev1=8&rev2=9

Comment:
added === Bug importing a non-MS Office document ===, redid PDF ex/import sections, & added info on programcrash when apport does not activate.

  
  = How to File =
  
+  * Please do not report a LibreOffice bug without first reading this wiki article and performing all the relevant actions mentioned here. Failure to do so will delay your bug getting addressed as quickly as possible.
   * Please file all your LibreOffice bugs by executing at the Terminal: <<BR>> {{{ubuntu-bug <PACKAGE>}}} <<BR>> <<BR>> where <PACKAGE> is the specific package you found the problem in. For example, if you have a document import issue with Writer: <<BR>> {{{ubuntu-bug libreoffice-writer}}}
   * Sample bug reporting template: <<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 <PRECISE, STEP-BY-STEP INSTRUCTIONS>. <<BR>> <<BR>> 4) What happened instead is... <<BR>> <<BR>> WORKAROUND: Perform the following steps:...||
@@ -13, +14 @@

  
  = 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 PDF ===
+ === Bug Exporting to Adobe PDF ===
-   * If you are reporting about how a document looks exporting to Evince, please attach the file to the bug report before and after exporting to PDF. As well, provide screenshots of how it looks in LibreOffice, Evince, and Adobe Reader.
+   * 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 .
@@ -28, +36 @@

  == 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 your graphics card driver 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.
+  * 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 .




More information about the Ubuntu-bugsquad mailing list