Everytime I try to open .rtf Files generated by Geneatique2011 (a genealogy management program)the opening process start but does not complete.
A windows appears with the message in french sayiing approximately "LibreOffice stoped because of an unexpected error".
BTW: same behaviour with OpenOffice.
Please find attached a file which enables to reproduce the problem.
Cheers (an thanks for the LibreOffice fork and initiative)
The .rtf file may not respect .rtf specifications, but what deserves a fix is LibreOffice Crasch at FILEOPEN. A "non conformant .rtf file" message may perfectly be acceptable (if appropriate; ie. .rtf non conformance)
It's important that you attach a test rtf document that crashes LibreOffice upon opening in order for us to debug this problem.
Could you attach a sample document? Thanks!
Created attachment 41977 [details]
example of .rtf file that crashes LibreOffice at opening
The previous attachment of test files were larger than 1 Meg that why they were not attached to the bug report. Sorry.
This one is just a small one page file.
As said previously, it may occur that the attached file is not .rtf conformant (it was generated by an application name Geneatique2011) but in that case a message stating something like "non conformant .rtf file" would be better than a crash. All .rtf files generated by this application exhibit the same behaviour of LobreOffice
BTW: OpenOffice 3.2 presents the same bug
rtf filter itself doesn't crash, layout crashes on a divide by 0 error. Here lets just tackle the immediate issue of the crash and put aside the quality/fidelity of the rtf import itself.
fixed with http://cgit.freedesktop.org/libreoffice/writer/commit/?id=4a698ffcf5756b7a6e8a2d583b530951fdeba4db
Thanks a lot
LO 3.4.5 crashes when opening this file, LO 3.3.4 too, but LO 3.5 (3.5.1 and 3.5.2 rc0+) does not crash anymore.
There is another bug with this file as a part of the data, visible in Abiword, Wordpad, and very shortly in LO 3.4.5 (before the crash), are not shown by LO 3.5. But that's another bug and I do not know if this bug is already filed.
Closing the bug related to the crash. Please feel free to reopen if needed.
Best regards. JBF