Created attachment 68209 [details] Normal application document from the City .docx document received in Evolution mail, opened with default application (LibreOffice Writer), and LibreOffice crash. Save to a file, and attempt to open without Evolution in the chain. Same crash. Copy file to a Windows-7 host, and document opens without issue. Abrt traceback is matched to https://bugzilla.redhat.com/show_bug.cgi?id=758860, which is an old bug in LibreOffice 3.4.4. It is not clear whether this is re-introduced in Fedora-latest or Abrt is mismatching bugs. 100% repeatable. Environment is fully-updated Fedora-17 on an AMD processor.
Created attachment 68210 [details] Traceback generated by abrt Traceback generated by abrt
Redhat bug https://bugzilla.redhat.com/show_bug.cgi?id=863810 created, in case the problem is due to problems building LibreOffice in Fedora-17.
Is the Windows host using the same version? I don't get a crash using 3.5.4 or current master on Ubuntu 12.04 or 3.6.2 on 12.10 so looks like either Fedora specific or a regression in the 3.5 series.
The differences between the (presumably) Windows host that created the document and the one that I used to check it are unknown. I used the home & student edition, and presumably they used a more expensive and more complete version. I have a Ubuntu 12.10 install at work, so it sounds like I'll be able to fill out the form from there.
this is a regression in LO 3.5.5 on the libreoffice-3-5 branch; current libreoffice-3-6 appears not not crash or loop. it appears the commit on the libreoffice-3-5 branch that makes the import fail is d32f3048052af80b21e8968d24eb55c48d298052 it doesn't crash for me but complains about some invalid nodes array index and then goes into infinite loop.
I wonder how serious this is; how many .docx documents trigger the mis-behaviour; presumably not all - is it isolated to those containing embedded shapes or somesuch ? ...
This appears to work nicely in 3.6.x and 4.x betas and master - so since 3.5 is at end-of-life, closing this. Apparently we missed something necessary for the back-port of that - sorry about that & thanks for filing the bug !