Available languages: Italiano
This page is part of the debugging series — pages with debugging details for a variety of Ubuntu packages.
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 remove all openoffice.org 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 the Terminal:
where <PACKAGE> is the specific package you found the problem in. For example, if you have a document import issue with Writer:
Bug reporting template
1) lsb_release -rd
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 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.
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. 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 LibreOffice and Adobe Reader.
For issues printing from LibreOffice please report this against cups first via the Terminal:
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 .
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 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 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
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 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 .
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.
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.
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.
An appropriate Won't Fix Wishlist reply:
Thank you for reporting this and helping make Ubuntu better. Regarding this report:
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 here.
Hence, an appropriate triaging response is:
Thank you for reporting this and helping make Ubuntu.
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.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.