Summary: | FILEOPEN DOCX: File containing lots of formula's saved with LibO impossible to open again | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | Telesto <telesto> |
Component: | Writer | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | RESOLVED INSUFFICIENTDATA | ||
Severity: | normal | CC: | dgp-mail, serval2412 |
Priority: | medium | ||
Version: | 6.4.0.0.alpha1+ | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Crash report or crash signature: | Regression By: | ||
Bug Depends on: | |||
Bug Blocks: | 104450 | ||
Attachments: |
Example file
Exported DOCX (broken) |
Description
Telesto
2019-06-11 07:36:11 UTC
Created attachment 152089 [details]
Example file
Created attachment 152090 [details]
Exported DOCX (broken)
I confirm it with Version: 6.4.0.0.alpha0+ (x64) Build ID: b170256fb6ebaf774b02b89835b19d9f3a1afb89 CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win; TinderBox: Win-x86_64@42, Branch:master, Time: 2019-06-07_03:30:35 Locale: de-DE (de_DE); UI-Language: en-US Calc: threaded I could open file in MS Word 2017 For me it took also to much time to open and save document from comment 1 On Win10 with master sources updated today + enable-dbgutil, I can't even open the initial example file. At least, after several minutes, it's still not opened. I noticed these logs which repeat endlessly: warn:legacy.osl:19480:32484:oox/source/vml/vmlshapecontainer.cxx:45: lclMapShapesById - shape identifier already used warn:legacy.osl:19480:32484:svx/source/unodraw/unoshape.cxx:1974: SvxShape::GetAnyForItem() Returnvalue has wrong Type! (In reply to Julien Nabet from comment #4) > On Win10 with master sources updated today + enable-dbgutil, I can't even > open the initial example file. > At least, after several minutes, it's still not opened. Same result with Version: 7.1.3.2 (x64) / LibreOffice Community Build ID: 47f78053abe362b9384784d31a6e56f8511eb1c1 CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL I could finally open the file in Word 2016, but it took a very long time. So for me, the source file itself seems to be problematic and therefor the bug is mor or less document related. So I suggest to close the bug. Telesto, feel free to change it back to NEW with a short reasoning if you disagree and could test it with the latest version of LO. |