LibreOfficeBugWrangling

Differences between revisions 28 and 31 (spanning 3 versions)
Revision 28 as of 2016-01-24 20:49:54
Size: 11946
Editor: penalvch
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.
Revision 31 as of 2016-12-25 20:09:59
Size: 12823
Editor: penalvch
Comment: 1) Adj. AOO/OOo sect. for transparency, and accuracy. 2) RM'd internal links that were unintentional, or go nowhere. 3) Various adj. to presentation and content for clarity, and approachability.
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
Available languages: [[https://wiki.ubuntu.com/LibreOfficeBugWrangling_it| Italiano]] Available languages: [[https://wiki.ubuntu.com/LibreOfficeBugWrangling_it|Italiano]]
Line 6: Line 6:
= Introduction =

 Please do not report a !LibreOffice bug without first reading this wiki article and performing all the relevant actions mentioned here. Also, please do not complain about how long it takes to release a patch, the severity of your bug is high so it should be fixed immediately, "I cannot believe it's not fixed...", etc. This type of behavior is nonconstructive, irritating to others who read your comment, and does not incentivize developers to want to fix your problem. 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.

= What is not considered a bug? =

== package libreoffice-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/soffice', which is also in package openoffice-debian-menus ==

 If you have a crash, and a window pops up asking to report to Launchpad something like:
 '''package libreoffice-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/soffice', which is also in package openoffice-debian-menus''' <<BR>><<BR>>
 Please do not file this as a bug report. It's not a bug, and will be marked Invalid. Instead, please remove the package openoffice-debian-menus first before upgrading.

== Apache OpenOffice / OpenOffice.org bugs ==

 Apache !OpenOffice (AOO) / !OpenOffice.org (OOo) is not supported in Ubuntu. This is due to how:

  1. !LibreOffice is the default office productivity suite in Ubuntu.
  1. !LibreOffice releases are [[https://wiki.documentfoundation.org/ReleasePlan|fast, timely, and on a scheduled maintenance cadence]].
  1. Historically, AOO has had a long time lag in [[https://openoffice.apache.org/mailing-lists.html#announce-mailing-list|releasing new versions, features, bug fixes, and security updates]].
  1. AOO has not announced a precise, and consistent release schedule for their software.
  1. Against the consensus of the OOo community, OOo was forced to incur an unnecessary, and largely unwanted licensing and branding change into AOO.

 Hence, an appropriate triaging response is:
 ||<tablestyle="background-color: #eee"> Thank you for reporting this and helping make Ubuntu. <<BR>> <<BR>> However, there are no new official Apache !OpenOffice / !OpenOffice.org releases in Ubuntu, as the Ubuntu project has transitioned to !LibreOffice. Hence, the status of this report is being marked as Won't Fix. <<BR>><<BR>> You are welcome to test for this problem in !LibreOffice. If reproducible, please click the button: <<BR>> Also affects distribution <<BR>><<BR>> Distribution: Ubuntu <<BR>> Source Package Name: (Optional) libreoffice <<BR>><<BR>> For more on installing !LibreOffice please see ''''''https://wiki.ubuntu.com/LibreOffice. <<BR>><<BR>> Thank you for your understanding.||
Line 8: Line 33:
 * 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.
 * F
irst, 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}}}
 First, please make sure you remove all AOO/OOo 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 terminal:
 ||
<tablestyle="background-color: #eee">{{{ubuntu-bug <PACKAGE>}}}||
where <PACKAGE> is the specific package you found the problem in. For example, if you have a document import issue with Writer:
 ||
<tablestyle="background-color: #eee">{{{ubuntu-bug libreoffice-writer}}}||
Line 15: Line 42:
||<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 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.
 /!\ Please note 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]].
 ||<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 TO REPRODUCE ONE PROBLEM>. <<BR>> <<BR>> 4) What happened instead is... <<BR>> <<BR>> I have the following extensions installed: lo-menubar... <<BR>> <<BR>> WORKAROUND: Perform the following steps:...||
Line 24: Line 49:
Try moving .libreoffice and ~/.config/libreoffice. If you installed any extensions, remove them and see if the problem is reproducible. Comment on the results of performing these techniques in your report. Please keep these directories around -- if moving the profile helps you, developers might be interested in it to find out what was wrong with it.  Try moving .libreoffice and ~/.config/libreoffice. If you installed any extensions, remove them and see if the problem is reproducible. Comment on the results of performing these techniques in your report. Please keep these directories around -- if moving the profile helps you, developers might be interested in it to find out what was wrong with it.
Line 28: Line 53:
 * 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.  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 in Ubuntu. As well, please post a screenshot of how it looks in !LibreOffice with a specific description about how it should look.
Line 32: Line 57:
 * 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.  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.
Line 36: Line 61:
 * 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.  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.
Line 40: Line 65:
 * 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.  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.
Line 44: Line 69:
 * 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.  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 Draw and Adobe Reader.
Line 48: Line 73:
 * 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 .  For issues printing from !LibreOffice please report this against cups first via a terminal:
 ||
<tablestyle="background-color: #eee">{{{ubuntu-bug cups}}}||
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 debugging steps noted in [[https://wiki.ubuntu.com/DebuggingPrintingProblems]].
Line 52: Line 79:
 * For instances when only LibreOffice crashes but you can still use the OS without hard rebooting:  For instances when only !LibreOffice crashes but you can still use the OS without hard rebooting:
Line 54: Line 81:
  * Please make sure LibreOffice debug symbols are installed (libreoffice-dbg, uno-libs3-dbg, and ure-dbg).   * Please make sure !LibreOffice debug symbol packages are installed:
  * libreoffice-dbg
   *
uno-libs3-dbg
  * ure-dbg
Line 56: Line 86:
  * 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.   * For suspected GUI/desktop environment driven crashes (ex. reproducible in Kubuntu but not Xubuntu), please remove the following packages and comment on if this changes anything:
   * libreoffice-gtk
   * libreoffice-gnome
   *
libreoffice-gtk3
   * libreoffice-kde
Line 60: Line 94:
 * For instances when you are using LibreOffice and either the system hangs requiring a hard reset or you are booted to the login screen, this is a bug in either xorg or the linux 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 you are using !LibreOffice and either the system hangs requiring a hard reset or you are booted to the login screen, this may be a bug in either the X.Org suite or the linux kernel. Please follow [[https://help.ubuntu.com/community/DebuggingSystemCrash]]. Also, 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.
Line 64: Line 98:
 * 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 .  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]].
Line 70: Line 104:
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.||
 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.<<BR>><<BR>>Could you please attach uncompressed/untarred 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, it needs to be removed. Please do not directly e-mail anyone the sensitive document as this puts an undue burden on the other person to ensure a secure chain of custody.<<BR>>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 it, and provide a fix.<<BR>><<BR>>Thank you for your understanding.||
Line 76: Line 109:
 * 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.  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.
Line 80: Line 113:
 * For Wishlist reports, these typically are requests to implement a new feature in LibreOffice not currently supported. A broad but good rule of thumb is if you want LibreOffice to do something that MS Office does, as LibreOffice intends compatibility with MS Office, 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).
 * 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:
 For Wishlist reports, these typically are requests to implement a new feature in !LibreOffice not currently supported. A broad but good rule of thumb is if you want !LibreOffice to do something that MS Office does, as !LibreOffice intends compatibility with MS Office, 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. [[https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/456100|leap year implementation]]).
 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. An appropriate [[https://wiki.ubuntu.com/Bugs/Bug%20statuses|Won't Fix]] [[https://wiki.ubuntu.com/Bugs/Bug%20importances|Wishlist]] reply:
Line 84: Line 117:
||<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 ==

The Ubuntu project no longer supports Apache OpenOffice (AOO) / OpenOffice.org (OOo), in favor of LibreOffice. This is an important distinction for original reporters of AOO/OOo bugs, as AOO/OOo 4.1.1 was released on August 21, 2014, and just the announcement of the next version (4.1.2) coming soon didn't come out until September 27, 2015 (over a year). This indicates a long lag in security and bug fixes, in comparison to LibreOffice's fast, and timely maintenance cadence as noted [[https://wiki.documentfoundation.org/ReleasePlan|here]].

Hence, an appropriate triaging response is:
||<tablestyle="background-color: #eee"> Thank you for reporting this and helping make Ubuntu. <<BR>> <<BR>> However, there are no new official Apache OpenOffice/OpenOffice.org releases in Ubuntu, as the Ubuntu project has transitioned to LibreOffice. Hence, the status of this report is being marked as Won't Fix. <<BR>><<BR>> You are welcome to test for this problem in LibreOffice. If reproducible, please click the button: <<BR>> Also affects distribution <<BR>><<BR>> Distribution: Ubuntu <<BR>> Source Package Name: (Optional) libreoffice <<BR>><<BR>> For more on installing LibreOffice please see [[https://wiki.ubuntu.com/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.||
Line 95: Line 121:
 * 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 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.documentfoundation.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.
Line 97: Line 124:
  * 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. = Links =

 * [[https://wiki.ubuntu.com/LibreOffice]] - The !LibreOffice in Ubuntu support page

Available languages: Italiano

Debugging Central

This page is part of the debugging series — pages with debugging details for a variety of Ubuntu packages.

Introduction

  • Please do not report a LibreOffice bug without first reading this wiki article and performing all the relevant actions mentioned here. Also, please do not complain about how long it takes to release a patch, the severity of your bug is high so it should be fixed immediately, "I cannot believe it's not fixed...", etc. This type of behavior is nonconstructive, irritating to others who read your comment, and does not incentivize developers to want to fix your problem. 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.

What is not considered a bug?

package libreoffice-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/soffice', which is also in package openoffice-debian-menus

  • If you have a crash, and a window pops up asking to report to Launchpad something like:

    package libreoffice-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/soffice', which is also in package openoffice-debian-menus

    Please do not file this as a bug report. It's not a bug, and will be marked Invalid. Instead, please remove the package openoffice-debian-menus first before upgrading.

Apache OpenOffice / OpenOffice.org bugs

  • Apache OpenOffice (AOO) / OpenOffice.org (OOo) is not supported in Ubuntu. This is due to how:

    1. LibreOffice is the default office productivity suite in Ubuntu.

    2. LibreOffice releases are fast, timely, and on a scheduled maintenance cadence.

    3. Historically, AOO has had a long time lag in releasing new versions, features, bug fixes, and security updates.

    4. AOO has not announced a precise, and consistent release schedule for their software.
    5. Against the consensus of the OOo community, OOo was forced to incur an unnecessary, and largely unwanted licensing and branding change into AOO.
    Hence, an appropriate triaging response is:

    Thank you for reporting this and helping make Ubuntu.

    However, there are no new official Apache OpenOffice / OpenOffice.org releases in Ubuntu, as the Ubuntu project has transitioned to LibreOffice. Hence, the status of this report is being marked as Won't Fix.

    You are welcome to test for this problem in LibreOffice. If reproducible, please click the button:
    Also affects distribution

    Distribution: Ubuntu
    Source Package Name: (Optional) libreoffice

    For more on installing LibreOffice please see https://wiki.ubuntu.com/LibreOffice.

    Thank you for your understanding.

How to file a bug

  • First, please make sure you remove all AOO/OOo packages first, then install the full LibreOffice suite to avoid package split collateral damage, by executing at a terminal:

    sudo apt-get -y install libreoffice

    Please file all your LibreOffice bugs by executing at terminal:

    ubuntu-bug <PACKAGE>

    where <PACKAGE> is the specific package you found the problem in. For example, if you have a document import issue with Writer:

    ubuntu-bug libreoffice-writer

Bug reporting template

  • Warning /!\ Please note 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 apt-show-versions.

    1) lsb_release -rd

    2) apt-cache policy <PACKAGE>

    apt-show-versions -r libreoffice*

    3) What is expected to happen in Writer is <PRECISE, STEP-BY-STEP INSTRUCTIONS TO REPRODUCE ONE PROBLEM>.

    4) What happened instead is...

    I have the following extensions installed: lo-menubar...

    WORKAROUND: Perform the following steps:...

Debugging

Move ~/.config/libreoffice

  • Try moving .libreoffice and ~/.config/libreoffice. If you installed any extensions, remove them and see if the problem is reproducible. Comment on the results of performing these techniques in your report. Please keep these directories around -- if moving the profile helps you, developers might be interested in it to find out what was wrong with it.

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 in Ubuntu. 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 PDF to Adobe

  • 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 Draw and Adobe Reader.

Printing problems

  • For issues printing from LibreOffice please report this against cups first via a terminal:

    ubuntu-bug cups

    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 debugging steps noted in https://wiki.ubuntu.com/DebuggingPrintingProblems.

LibreOffice crashes but system still functional

  • For instances when only LibreOffice crashes but you can still use the OS without hard rebooting:

    • Please consult https://wiki.ubuntu.com/Apport to ensure Apport is enabled.

    • Please make sure LibreOffice debug symbol packages are installed:

      • libreoffice-dbg
      • uno-libs3-dbg
      • 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 remove the following packages and comment on if this changes anything:
      • libreoffice-gtk
      • libreoffice-gnome
      • libreoffice-gtk3
      • libreoffice-kde

The Whole system hangs or boots to the login screen

  • For instances when you are using LibreOffice and either the system hangs requiring a hard reset or you are booted to the login screen, this may be a bug in either the X.Org suite or the linux kernel. Please follow https://help.ubuntu.com/community/DebuggingSystemCrash. Also, 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.

Bibisecting regressions

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:

    Thank you for reporting this and helping make Ubuntu better.

    Could you please attach uncompressed/untarred to this report a document that reproduces this problem? Please ensure that:
    1) If a concern of privacy exists due to the sensitive information in the document, it needs to be removed. Please do not directly e-mail anyone the sensitive document as this puts an undue burden on the other person to ensure a secure chain of custody.
    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 it, and provide a fix.

    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.

Wishlist reports

  • For Wishlist reports, these typically are requests to implement a new feature in LibreOffice not currently supported. A broad but good rule of thumb is if you want LibreOffice to do something that MS Office does, as LibreOffice intends compatibility with MS Office, 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). 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. An appropriate Won't Fix Wishlist reply:

    Thank you for reporting this and helping make Ubuntu better. Regarding this report:
    - 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.
    - 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.

    Thank you for your understanding.

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 LibreOffice Bug Submission Assistant, or in the old fashioned way at https://bugs.documentfoundation.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.

Links


CategoryBugSquad CategoryDebugging

LibreOfficeBugWrangling (last edited 2018-06-04 22:50:25 by penalvch)