When I tried to open docx files they were being reported by a libreoffice dialog as corrupt. LibreOffice would offer to repair the file, but it would always fail. The actual problem was that I only had libre office calc installed. It would be a better error/warning if the file was not determined to be corrupt, but instead libreoffice reported components are missing.
Well, maybe it was still possible in version 4.4 to "remove" applications in the Windows installer, but it is not possible anymore. You didn't define an operating system - were you using Windows?
(In reply to Buovjaga from comment #1) > Well, maybe it was still possible in version 4.4 to "remove" applications in > the Windows installer, but it is not possible anymore. > You didn't define an operating system - were you using Windows? No I am using fedora, sorry I didn't define it before.
Is it possible for you to try with 5.1.1? Or does it even allow to install the applications separately?
(In reply to Buovjaga from comment #3) > Is it possible for you to try with 5.1.1? Or does it even allow to install > the applications separately? I do not know how to install it separately if it is possible. Right now fedora lets me install individual components. I only have calc and writer installed. It looks like the rpm from the site will install everything.
Buovjaga, I could reproduce this in Ubuntu 15.10, which also has LO components installed separately (5.0.5.2). I removed these two packages: libreoffice-writer libreoffice-help-en-us. As far as I can see the practice is the same in 16.04, separate packages per components: https://launchpad.net/ubuntu/xenial/+package/libreoffice
NEW per comment 5.
** 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 on a currently supported version of LibreOffice (5.2.7 or 5.3.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170522
Dear Matt, 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 https://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
Dear Matt, 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 https://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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Experiencing issues with docx files being reported as corrupt due to missing writer software? Our essay writing service Toronto team can assist by ensuring your documents are properly formatted and compatible with all standard software. This prevents corruption and ensures seamless submission. Visit here: https://essaywritingservices.ca/
When attempting to open reports in .docx format without the appropriate software, they may appear as corrupt. This issue underscores the importance of having the right tools, like a compatible word processor, to access and read these files seamlessly. Visit here: https://onlinenursingessayhelp.uk/topic/medical-surgical-nursing-dissertation-topics/
Thinking about this again and after discussing in the developer chat, the applications are not supposed to be used separately and there is no guarantee that they will work that way. So the Linux distros wanting to separate them in this unusual way should provide some mechanism to handle these sorts of errors.
This just shows how bad the libre office suite is. Let the OS try to delegate, and fail. LO offers a service that will delegate office related files to the respective program. So Fedora as an OS uses the LO service. The LO service should say "cannot open the file with the available programs." Instead it says "file is corrupt". Don't tell the OS your service handles such files. What is the point of a single service that doesn't know what files it can handle? You're incorrectly saying that someones data is corrupt. Take some responsibility for your actions. How about you say, "We cannot open it, do you have the correct components installed." I don't use your software, and this just confirms my reasoning.
It would be better, if LibreOffice just refused to launch in a situation where the installation is incomplete. Surely there are many more cases of "undefined behaviour" in this kind of a broken setup.
That would be a much more reasonable approach. It fails, The response is "You have an incomplete office installation." I think that sends a user down the path of, what is wrong with my office software.
Ok, let's reopen this with a different summary.
With my distro packager hat on: (In reply to Matt from comment #15) > That would be a much more reasonable approach. It fails, The response is > "You have an incomplete office installation." I think that sends a user down > the path of, what is wrong with my office software. Maybe with a warning. A failure is out of the question. I would consider simply patching that out... If you want writer stuff (and docx obviously is a text document so wants writer) then install writer? What is the problem? Or do you want to have all kinds of stuff you don't need (including Java and all kinds of Java libraries or scientific stuff) installed a) polluting your filesystem b) making the .deb/.rpm/.. bigger, also for every upload
LibreOffice project provides packages and installation instructions that install all components: see e.g. its Linux instructions at [1], where it tells to select *all* in GUI installation, and to use *.deb / *.rpm in the command line. Linux distros choose to make some modules separate; and provide maybe incomplete instructions to their users about how to use that modularized product. LibreOffice project doesn't need that modularization; but since some of its users need that, it gladly accepts improvements from the interested parties, for their special corner usecases. If maintainers do not test their unusual install set configurations, and don't provide patches that would be useful in their setups, there's nothing LibreOffice project can do. This is NOTOURBUG. https://wiki.documentfoundation.org/Documentation/Install/Linux
> How about you say, "We cannot open it, do you have the correct components installed." That indeed should be done, though.
LibreOffice project provides packages and installation instructions that install all components: see e.g. its Linux instructions at [1], [...] to use *.deb / *.rpm in the command line. That assumes people read that in the wiki. And if they don't and get -writer etc. you already get the modularization even in TDF .rpm/.deb (they would need to handle dependencies, maybe). Never underestimate creativity of users...
> If maintainers do not test their unusual install set configurations, [...] That is going to far. It is 100% obvious that you might need writer for a docx document. In this case it's 100% a user error (just install writer and be done) imho. For other cases, it's not that easy. Base and Java comes to my mind. Or optional stuff which you don't need in "normal" operation. (And thus it's ok if it failed, because you simply can install the needed module)