The attached DOCX file does not open in LibreOffice and immediately offers recovery, which still does not resolve the issue.
Since the attachment is too big, please follow the link below to download the issue DOCX file: https://drive.google.com/file/d/0B6ccfQG2Kep-Nzk5QW1sc3kxNkk/edit?usp=sharing
The document appears corrupted. Does it open at all?
Created attachment 95522 [details] backtrace with symbols from SIGABRT With master commit 806f4d8, fetched 2014-03-04, configured as: --enable-option-checking=fatal --enable-dbgutil --enable-crashdump --without-system-postgresql --without-myspell-dicts --with-extra-buildid --without-doxygen --with-external-tar=/home/terry/lo_hacking/git/src built and running on debian-wheezy 64-bit, I have managed to provoke a SIGABRT. The interesting part of the terminal output is: /usr/include/c++/4.7/debug/vector:366:error: attempt to access an element in an empty container. Objects involved in the operation: sequence "this" @ 0x0x39300c8 { type = NSt7__debug6vectorIN5boost10shared_ptrINS0_IiSaIiEEEEESaIS5_EEE; } Application Error Fatal exception: Signal 6 This is another case of an assertion raised by a STL debug container. It may not be exactly the crash originally reported, but hopefully it happened earlier and more informatively.
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/FDO/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team
(In reply to Orbel from comment #0) > The attached DOCX file does not open in LibreOffice and immediately offers > recovery, which still does not resolve the issue. > ... > https://drive.google.com/file/d/0B6ccfQG2Kep-Nzk5QW1sc3kxNkk/edit?usp=sharing Trying to open the given docx file crashes LibreOffice 4.3.2.2 on Ubuntu 14.04. It appears that there is some doubt about whether this file is actually validly-formatted, so I'll tentatively mark it as NEW.
** 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.0.1 or preferably 5.0.2.2 or later) 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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-10-14
Summary ------- Over time, people have reported various problems opening the file linked from comment 1 ... - description : does not open - c#2 : document appears corrupted - c#3 : SIGABRT, access an element in an empty container - c#5 : crashes. doubt about validity of file - c#7 (here!) : SAXParseException New comment ----------- In daily dbgutil repository version 2015-11-13, upon attempt to open the file, LO displays a message box (newlines added) ... File format error found at unsatisfied query for interface of type com.sun.star.lan.XComponent! SAXParseException: '[word/endnotes.xml line 2]: unknown error', Stream 'word/endnotes.xml', Line 2, Column 169834 SAXParseException: '[word/document.xml line 2]: unknown error', Stream 'word/document.xml', Line 2, Column 139175(row,col). officeotron reports one error in "Checking OPC Package" (newlines added): Entry with MIME type "application/vnd.openxmlformats-package.core-properties+xml" has unrecognized relationship type "http://schemas.openxmlformats.org/package/2006/relationships/metadata/core-properties" (see ISO/IEC 29500-1:2008, Clause 15.2.12.1) I am changing bug summary from The attached DOCX file does not open in LibreOffice to FILEOPEN: SAXParseException on one .DOCX (summary in comment 07) and adding whiteboard summaryUpdate.
Created attachment 121849 [details] compressed DOCX and PDF The file opens with Word. It contains 5013 pages. Word works with document very slowly; repagination takes ~5 min. The archive also contains PDF generated with Word. On my system, it opens with Version: 5.0.4.2 (x64) Build ID: 2b9802c1994aa0b7dc6079e128979269cf95bc78 Locale: ru-RU (ru_RU) (opening takes ~12 mins; after that it shows first pages), and immidiately crashes with SEH Exception: ACCESS VIOLATION. Screenshot is also in attachment.
** 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
On Win 10 with master sources updated yesterday, I don't reproduce the crash. However, it's quite long to open (several minutes). Any update with recent LO version? (eg 6.2.3)
Created attachment 151934 [details] massaged terminal output I do not see the bug in a local build of of commit 74288f5a from 2019-04-12, configured with --enable-debug, built and running on debain-buster. However, just opening the test file and quitting LibreOffice wrote 47796 lines to the terminal. Attachment is the result of: < $outfile sort | uniq --count | sort --numeric --reverse
Dear Orbel, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear Orbel, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp