On a debian system where the 'libreoffice-writer' package has been removed but the rest of libreoffice remains, attempting to open a .odt file from the command line like this libreoffice my_valid_document.odt causes libreoffice to say LibreOffice Document Recovery Due to an unexpected error, LibreOffice crashed. All the files you were working on will now be saved. The next time LibreOffice is launched, your files will be recovered automatically. I expected libreoffice to (a) not crash and (b) say something along the lines of "can't open that file because the 'writer' component isn't installed". Originally filed as Debian bug 837156, the maintainer there asked me to report it upstream.
Note we in Debian move libsw from -core to -writer (as it's clearly something writer'ish), so it _might_ be that this doesn't happen when libsw is there in -coreXY (as for upstream). See [1] Still this needs to be fixed ;) [1] https://anonscm.debian.org/cgit/pkg-openoffice/libreoffice.git/tree/patches/make-package-modules-not-suck.diff
@Rene can we take that as a confirmation of the bug report?
Yep -> NEW. Rene wasn't in CC, so could not reply.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
In today's Debian testing, the 'libreoffice-writer' package can't be removed without forcing dependencies, so the bug can't happen any more. I've marked the bug as 'resolved-worksforme' because creating this situation seems to have become harder since 2016 thanks to Debian fixing dependencies. The versions I have are Debian libreoffice-writer 1:6.1.2-1 Libreoffice help: Version: 6.1.2.1 Build ID:1:6.1.2-1 If I forcibly remove Debian's libreoffice-writer package (i.e. --force dependencies), I get various different behaviours depending on how much of libreoffice I remove. In one case I get an unfriendly stack trace: terminate called after throwing an instance of 'com::sun::star::uno::RuntimeException' Fatal exception: Signal 6 Stack: /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3cfb3)[0x7ff5d9d40fb3] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3d1c3)[0x7ff5d9d411c3] In another case I get a dialog offering to import from a list of about 100 formats which aren't in any obvious order (not alphabetical, for instance), presumably to view the document in one of the libreoffice components that is actually still installed.