[Ubuntu Wiki] Update of "LibreOfficeBugWrangling" by penalvch

Sun Jan 24 20:49:57 UTC 2016

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=27&rev2=28

Comment:
1) RM'ed commented out preface. 2) Added triage statement requesting document. 3) RM'ed footnote syntax as it puts it after categories, which looks odd. 4) Minor presentation fixes.

- ## 20121122 https://launchpad.net/~penalvch When one files a bug via apport against libreoffice via ubuntu-bug libreoffice and did not install the libreoffice meta package, the filed bug report tends not to provide enough information to triage appropriately. Ex. https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1080509 one has no idea what specific LO packages they actually have installed. Hence, asking for apt-show-versions -r libreoffice* in the bug reporting template section is an extremely helpful way an original reporter can provide information for triagers to work on the problem without asking for follow up information, and waiting for the response. However, not all packages in https://launchpad.net/ubuntu/+source/libreoffice have libreoffice in the name, so some will be missed (ex. ure, python-uno, etc.). If a more comprehensive command exists to provide all the installed packages for libreoffice with versions compactly, that does not contain the word libreoffice in the package name, please replace. I just have not come across a more relevant one. Thank you for your understanding.
- 
  Available languages: [[https://wiki.ubuntu.com/LibreOfficeBugWrangling_it| Italiano]]
  
  <<Include(Debugging/Header)>>
@@ -10, +8 @@

  = How to file a bug =
  
   * 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 may delay your bug getting addressed as quickly as possible. 
-  * First, before filing a bug report, please make sure you uninstall all openoffice.org packages first, then install the full LibreOffice suite to avoid [[https://blueprints.launchpad.net/ubuntu/+spec/desktop-q-libreoffice-split|package split collatoral damage]], by executing at a terminal:
+  * First, before filing a bug report, please make sure you remove all openoffice.org packages first, then install the full LibreOffice suite to avoid [[https://blueprints.launchpad.net/ubuntu/+spec/desktop-q-libreoffice-split|package split collateral damage]], by executing at a terminal:
  ||<tablestyle="background-color: #eee"> {{{sudo apt-get -y install libreoffice}}}||
    * 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}}}
  
@@ -19, +17 @@

  ||<tablestyle="background-color: #eee"> 1) lsb_release -rd <<BR>> <<BR>> 2) apt-cache policy <PACKAGE> <<BR>> <<BR>> apt-show-versions -r libreoffice* <<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>> I have the following extensions installed: lo-menubar... <<BR>> <<BR>> WORKAROUND: Perform the following steps:...||
   /!\ Please note the above 1) and 2) are terminal commands to execute, and post the results of when initially filing your bug report. As well, you may need to install the package [[https://launchpad.net/ubuntu/+source/apt-show-versions|apt-show-versions]].
   * Please do not stack multiple issues into one bug.
-  * Please do not complain about how long it takes to fix a bug, the severity of your bug is high so it should be fixed immediately, "I cannot believe it's not fixed...", etc. Especially, if you have not completed the relevant, below mentioned debugging procedures, let alone contributed code upstream. This type of behavior is unconstructive, irritating to others who read your E-Mail, and spammy. We all want to see every bug fixed as soon as possible! Naturally, bugs being fixed is limited to reproducibility and clarity of the bug report, the actual impact the bug has on the community, and available developer resources.
+  * Please do not complain about how long it takes to fix a bug, the severity of your bug is high so it should be fixed immediately, "I cannot believe it's not fixed...", etc. Especially, if you have not completed the relevant, below mentioned debugging procedures, let alone contributed code upstream. This type of behavior is nonconstructive, irritating to others who read your E-Mail, and perceived as spam. We all want to see every bug fixed as soon as possible! Naturally, bugs being fixed is limited to reproducibility and clarity of the bug report, the actual impact the bug has on the community, and available developer resources.
  
  = Debugging =
  
@@ -57, +55 @@

    * Please consult https://wiki.ubuntu.com/Apport to ensure Apport is enabled.
    * Please make sure LibreOffice debug symbols are installed (libreoffice-dbg, uno-libs3-dbg, and ure-dbg).
    * If this happened while a particular document was open or you were manipulating the document in a certain way, please attach that document to the bug report with detailed, click-for-click steps on how to reproduce the crash.
-   * For suspected GUI/desktop environment driven crashes (ex. reproducible in Kubuntu but not Xubuntu), please uninstall the packages libreoffice-gtk, libreoffice-gnome, libreoffice-gtk3, and libreoffice-kde and comment on if this changes anything.
+   * For suspected GUI/desktop environment driven crashes (ex. reproducible in Kubuntu but not Xubuntu), please remove the packages libreoffice-gtk, libreoffice-gnome, libreoffice-gtk3, and libreoffice-kde and comment on if this changes anything.
  
  == The Whole system hangs or boots to the login screen ==
  
@@ -69, +67 @@

  
  = Triaging LibreOffice bugs =
  
+ == Requesting a document ==
+ 
+ Many bugs are dependent on the document. Hence, it is vital the original reporter provide a minimal test case that demonstrates the issue. An example triaging statement:
+ ||<tablestyle="background-color: #eee">Thank you for reporting this and helping make Ubuntu better. Regarding this report:<<BR>>Could you please attach to this report a document that reproduces this problem? Please ensure that:<<BR>>1) If a concern of privacy exists due to the sensitive information in the document, you need to remove it. Please do not directly e-mail anyone the sensitive document as this puts an undue burden on the other person to maintain a chain of custody that is not legally maintainable.
+ 2) Please reduce the document so that it has the least amount of content possible, but still demonstrates this problem. The bigger the document, the harder it is for a developer to quickly review the document, and provide a fix.<<BR>><<BR>> Thank you for your understanding.||
+ 
  == 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.
@@ -79, +83 @@

    * 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).
   * For Wishlist reports, they would typically 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>> An appropriate [[https://wiki.ubuntu.com/Bugs/Bug%20statuses|Won't Fix]] [[https://wiki.ubuntu.com/Bugs/Bug%20importances|Wishlist]] 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. You are 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. <<BR>><<BR>> Thank you for your understanding.||
+ ||<tablestyle="background-color: #eee">Thank you for reporting this and helping make Ubuntu better. Regarding this report:<<BR>>- This is a clearcut upstream issue. Could you please send this to the developers of the software by following the instructions at [[http://wiki.documentfoundation.org/BugReport]]? Please provide a URL of the upstream bug, so a bugwatch may be added that will advise 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. <<BR>><<BR>> Thank you for your understanding.||
  
  == Apache OpenOffice / OpenOffice.org bugs ==
  
@@ -90, +94 @@

  
  == How to forward bugs Upstream ==
  
-  * Once marked Triaged, a bug that is reproducible in the upstream release would want to 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 marked Triaged, a bug that is reproducible in the upstream release would want to be filed upstream using the [[https://www.libreoffice.org/get-help/bug/|LibreOffice Bug Submission Assistant]], 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.
  


