Created attachment 83205 [details] Word document that can't be oppened Problem description: I try to open an word document an I get: General Error. General input/output error. Steps to reproduce: 1. open attached document Current behavior: Do not open document Expected behavior: To open document Operating System: Windows 7 Version: 4.1.0.4 release
Thanks for reporting! I can confirm this behavior, tested using Windows 8 with LibreOffice 4.1.0.4. Also reproducible using LibreOffice Version: 4.2.0.0.alpha0+ Build ID: 2f6cbe13e61c44d4bab8192a4708b698d3d9da33 TinderBox: Win-x86@6-debug, Branch:master, Time: 2013-07-25_00:00:21 Kind regards, Joren
*** This bug has been marked as a duplicate of bug 67699 ***
It's not a duplicate of bug 67699, as bug 67699 is already fixed as of 4.1.2.2, while this bug is still reproducible. Tested under Fedora 19 (64-bit). Below I'll attach the stderr output.
Created attachment 86357 [details] stderr output when opening this file
(In reply to comment #3) > It's not a duplicate of bug 67699, as bug 67699 is already fixed as of > 4.1.2.2, while this bug is still reproducible. Also the whole point of bug 67699 is that LO should detect file type according to its contents, not just according to file suffix. As of the current bug - it doesn't open even if you'll rename it to *.xml
Mea culpa - this is not about opening files with wrong extension (as I mistakingly assumed), but about MSO 2003 XML format; maybe this one has something in common with bug 64423?
The document can be opened if terrific whitespaces are cut out.
** 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 (4.4.1 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-04-01
Read error with 5.0 & 3.5.0. 3.3.0 gives ascii filter options dialog. Win 7 Pro 64-bit Version: 5.0.0.0.alpha0+ (x64) Build ID: 211c12b9c64facd1c12f637a5229bd6a6feb032a TinderBox: Win-x86_64@42, Branch:master, Time: 2015-04-18_01:51:17 Locale: fi_FI Ubuntu 14.10 64-bit LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4 LibreOffice 3.5.0rc3 Build ID: 7e68ba2-a744ebf-1f241b7-c506db1-7d53735
Created attachment 122808 [details] Word2013 "fixed" example This file was original the same structure. I opened it with Word2013 and simply saved it (and replaced content with lorem ipsum) Writer simply does a "text import" with LibreOffice 5.1 release.
I tried to open the file from 2013-07-29 (Word document that can't be oppened) with the same result as the original poster: general error general input/ouptut error libreoffice 5.1.4.2 ubuntu 16.04.1 The bug is also still present.
The saved file from Word 2013 is not a Word XML document. It is some kind of flat OOXML file.
@urmas, yes, see https://en.wikipedia.org/wiki/Microsoft_Office_XML_formats @beluga do we have a separated keyword for that file type shouldn't we separate the two file formats?
(In reply to Dennis Roczek from comment #13) > @urmas, yes, see https://en.wikipedia.org/wiki/Microsoft_Office_XML_formats > > @beluga do we have a separated keyword for that file type shouldn't we > separate the two file formats? We do have filter:ooxml, but I don't think we should add it to this report as the file was produced by your test in MSO 2013.
** 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.4.1 or 5.3.6 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-20170929
still repro with Version: 5.4.1.2 (x64) Build-ID: ea7cb86e6eeb2bf3a5af73a8f7777ac570321527 CPU-Threads: 4; Betriebssystem:Windows 6.19; UI-Render: Standard; Gebietsschema: de-DE (de_DE); Calc: group
Repro 6.2+. Sample is DOC. If saved in MSO as XML also cannot be open. Just if saved in MSO as DOCX it works.
Dear Razvan Calugarasu, 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
Repro 6.4+
Repro 7.2+.
Dear Razvan Calugarasu, 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
still repro with Version: 7.6.1.2 (X86_64) / LibreOffice Community Build ID: 60(Build:2) CPU threads: 4; OS: Linux 6.2; UI render: default; VCL: gtk3 Locale: de-DE (de_DE.UTF-8); UI: de-DE Ubuntu package version: 4:7.6.1~rc2-0ubuntu0.22.04.1~lo2 Calc: threaded
The code catches itself doing infinite recursion at line 2343 of workdir\UnpackedTarball\libxslt\libxslt\transform.c in function xsltApplySequenceConstructor: "/* * Check for infinite recursion: stop if the maximum of nested templates * is excceeded. Adjust xsltMaxDepth if you need more. */ if (ctxt->depth >= ctxt->maxTemplateDepth) { " The callstack just has the following frames repeated: libxslt.dll!xsltApplySequenceConstructor(_xsltTransformContext * ctxt, _xmlNode * contextNode, _xmlNode * list, _xsltTemplate * templ) Line 2351 C libxslt.dll!xsltApplyXSLTTemplate(_xsltTransformContext * ctxt, _xmlNode * contextNode, _xmlNode * list, _xsltTemplate * templ, _xsltStackElem * withParams) Line 3211 C libxslt.dll!xsltCallTemplate(_xsltTransformContext * ctxt, _xmlNode * node, _xmlNode * inst, _xsltElemPreComp * castedComp) Line 4788 C libxslt.dll!xsltApplySequenceConstructor(_xsltTransformContext * ctxt, _xmlNode * contextNode, _xmlNode * list, _xsltTemplate * templ) Line 2752 C libxslt.dll!xsltChoose(_xsltTransformContext * ctxt, _xmlNode * contextNode, _xmlNode * inst, _xsltElemPreComp * comp) Line 5269 C libxslt.dll!xsltApplySequenceConstructor(_xsltTransformContext * ctxt, _xmlNode * contextNode, _xmlNode * list, _xsltTemplate * templ) Line 2752 C libxslt.dll!xsltIf(_xsltTransformContext * ctxt, _xmlNode * contextNode, _xmlNode * inst, _xsltElemPreComp * castedComp) Line 5375 C So, it looks like this is a bug in the library. Maybe a bug should be opened at https://gitlab.gnome.org/GNOME/libxslt/-/issues ? Marking as NOTOURBUG
Even if the bug is in a library used by LibreOffice, if/when it gets fixed, the library still needs to be updated in LibreOffice, ie. there's something to do on the side of LO. Let's keep this open until that.