Description: Documents created in MS Office saved in xml format - docx - with embeded documents do not open or it takes a considerable amount of time to have them opened by LibreOffice Writer 5.x. One can easily open them in LibreOffice Writer 4.1 for instance. Steps to Reproduce: 1. Take a docx file with nested docx documents. 2. Open with LibreOffice Writer 5.x. 3. Wait and see. Actual Results: After 10, 20, 30 minutes it might open but otherwise processor utilisation is under constant utilisation by libreoffice, disk is not doing much. Expected Results: LibreOffice Writer not resposive. Reproducible: Always User Profile Reset: Tried it on five different computers x32 and amd64 to no avail. Additional Info: I can send you an example file if you like. User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:51.0) Gecko/20100101 Firefox/51.0
Hello Michal, Thank you for reporting the bug. it seems you're using an old version of LibreOffice. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Created attachment 132075 [details] example file I cannot open it in LibreOffice Writer 5.0 and 5.1 and 5.2 and 5.3 on MS Windows x32 and x64 but it works fine with LibreOffice Writer 4.1.
(In reply to Xisco Faulí from comment #1) > Hello Michal, > > Thank you for reporting the bug. > > it seems you're using an old version of LibreOffice. > Could you please try to reproduce it with the latest version of LibreOffice > from https://www.libreoffice.org/download/libreoffice-fresh/ ? > I have set the bug's status to 'NEEDINFO'. Please change it back to > 'UNCONFIRMED' if the bug is still present in the latest version. The situation repeats itself with 5.0 and 5.1 and 5.2 and 5.3. I can open such files in LibreOffice 4.1.
(In reply to Xisco Faulí from comment #1) > Hello Michal, > > Thank you for reporting the bug. > > it seems you're using an old version of LibreOffice. > Could you please try to reproduce it with the latest version of LibreOffice > from https://www.libreoffice.org/download/libreoffice-fresh/ ? > I have set the bug's status to 'NEEDINFO'. Please change it back to > 'UNCONFIRMED' if the bug is still present in the latest version. I've attached such a document to this bug. You can test the process using it. Will you be so kind as to let me know if you are going to look into it? Regards, Michal
Hello Michal, I'm sorry. Your response went unnoticed to me. The document opens instantly in Version: 5.4.0.0.alpha0+ Build ID: 193f8966135064a32164c9da08d01dab9c1fc15d CPU threads: 4; OS: Linux 4.8; UI render: default; VCL: gtk2; Locale: ca-ES (ca_ES.UTF-8); Calc: group and Versión: 5.3.1.1 Id. de compilación: 72fee18f394a980128dc111963f2eefb05998eeb Subpr. de CPU: 1; SO: Windows 6.1; Repr. de IU: predet.; Motor de trazado: HarfBuzz; Configuración regional: es-ES (es_ES); Calc: group
The situation is persistent across whole 5.x branch: 5.1, 5.2, 5.3...
I've checked it on Mac OS X Sierra with Libreoffice 5.3.1. It does not open the file.
(In reply to Michal Stepniewski from comment #2) > Created attachment 132075 [details] > example file > > I cannot open it in LibreOffice Writer 5.0 and 5.1 and 5.2 and 5.3 on MS > Windows x32 and x64 but it works fine with LibreOffice Writer 4.1. So you are unable to open it normally on Windows or Mac? I was able to open on Windows just fine. I can test with macOS later. Win 7 Pro 64-bit, Version: 5.3.1.2 (x64) Build ID: e80a0e0fd1875e1696614d24c32df0f95f03deb2 CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; Layout Engine: new; Locale: fi-FI (fi_FI); Calc: CL
(In reply to Buovjaga from comment #8) > (In reply to Michal Stepniewski from comment #2) > > Created attachment 132075 [details] > > example file > > > > I cannot open it in LibreOffice Writer 5.0 and 5.1 and 5.2 and 5.3 on MS > > Windows x32 and x64 but it works fine with LibreOffice Writer 4.1. > > So you are unable to open it normally on Windows or Mac? I was able to open > on Windows just fine. I can test with macOS later. > > Win 7 Pro 64-bit, Version: 5.3.1.2 (x64) > Build ID: e80a0e0fd1875e1696614d24c32df0f95f03deb2 > CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; Layout Engine: > new; > Locale: fi-FI (fi_FI); Calc: CL I'm not able to create a proper attachment file in bugzilla so I've put one on my web site. You can download it from: https://1-2.pl/pub/example.docx It has a size of 22MB. It does not compress much but here you are a compressed version: https://1-2.pl/pub/example.docx.zip This file is being easily opened by LibreOffice 4.1 on Windows and Mac. It cannot be opened by LibreOffice 5.1, 5.2, 5.3 on either of the platforms.
(In reply to Buovjaga from comment #8) > (In reply to Michal Stepniewski from comment #2) > > Created attachment 132075 [details] > > example file > > > > I cannot open it in LibreOffice Writer 5.0 and 5.1 and 5.2 and 5.3 on MS > > Windows x32 and x64 but it works fine with LibreOffice Writer 4.1. > > So you are unable to open it normally on Windows or Mac? I was able to open > on Windows just fine. I can test with macOS later. > > Win 7 Pro 64-bit, Version: 5.3.1.2 (x64) > Build ID: e80a0e0fd1875e1696614d24c32df0f95f03deb2 > CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; Layout Engine: > new; > Locale: fi-FI (fi_FI); Calc: CL Xisco, I'm sorry I put you on a wild goose chase. The attachment is irrelevant. I've decided to put a proper example on my web site due to my failure in creating 22MB attachment on bugzilla. You can download it from: https://1-2.pl/pub/example.docx It has a size of 22MB. It does not compress much but here you are a compressed version: https://1-2.pl/pub/example.docx.zip This file is being easily opened by LibreOffice 4.1 on Windows and Mac. It cannot be opened by LibreOffice 5.1, 5.2, 5.3 on either of the platforms. Today it is LibreOffice 5.3.2.
Created attachment 132286 [details] GDB trace of crash with 5.4 master (In reply to Michal Stepniewski from comment #9) > https://1-2.pl/pub/example.docx I get a crash on opening. Got a trace. Arch Linux 64-bit, KDE Plasma 5 Version: 5.4.0.0.alpha0+ Build ID: 0d658dfc8ffdc91f3dcb2bd34dde1dbae76ad8ae CPU threads: 8; OS: Linux 4.10; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on March 30th 2016
3.6 doesn't crash. Arch Linux 64-bit Version 3.6.7.2 (Build ID: e183d5b)
This seems to have begun at the below commit. Adding Cc: to Miklos Vajna ; Could you possibly take a look at this one? Thanks cc44ace348bc71b8e0411f3c4a3dbcec4852c8a5 is the first bad commit commit cc44ace348bc71b8e0411f3c4a3dbcec4852c8a5 Author: Matthew Francis <mjay.francis@gmail.com> Date: Sun Mar 15 01:57:21 2015 +0800 source-hash-41aa970b3120837ca9cadb12997a53ad322145a4 commit 41aa970b3120837ca9cadb12997a53ad322145a4 Author: Miklos Vajna <vmiklos@collabora.co.uk> AuthorDate: Wed Aug 27 15:24:37 2014 +0200 Commit: Miklos Vajna <vmiklos@collabora.co.uk> CommitDate: Wed Aug 27 15:34:41 2014 +0200 DOCX import: fix handling of embedded DOCX files The problem was that SwXTextEmbeddedObject::getEmbeddedObject() returned an empty reference for those embedded objects, so the HTML filter couldn't extract their content when it wanted to do so. It turns out the reason for this was that the DOCX importer only handled the replacement image + raw native data for the object. Fix this by creating the embedded object with the correct CLSID and import the raw data into the empty embedded document model. This is similar to what is done for XLSX-in-PPTX in oox::drawingml::ShapeExport::WriteOLE2Shape(), just for the import part. Change-Id: Ieb1dcb1774d2d4da00117e3a35160053066c78aa
If you want faster import, just go to Tools -> Options -> Load/Save -> Microsoft Office and untick the Load column at the "WinWord to LibreOffice" row. I don't think this is a regression; the binary DOC import always did this "embedded DOC" -> "embedded Writer document" conversion, and it's consistent that with the above commit the DOCX import does the same.
** 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
Large sample is not available anymore. Those who have it, please attach. Anyway, looks like a duplicate of bug 93635. If you disagree, please explain. *** This bug has been marked as a duplicate of bug 93635 ***