Red Hat Bugzilla – Bug 1274081
Crash opening Word document in SwFrm::_FindPrev
Last modified: 2016-07-19 14:18:07 EDT
Created attachment 1085328 [details]
Backtrace of crash
Description of problem:
Opening this one Word document consistently crashes libreoffice.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Open document from terminal/nautilus.
Document is opened.
Unfortunately, I am unable to share said document because it is a student-submitted work, but I have attached the backtrace produced by `libreoffice --backtrace file.docx`. I can inspect it in gdb if necessary.
You need to install libreoffice-debuginfo to get a reasonable backtrace...
Could you send the document to firstname.lastname@example.org? It'll be handled as private.
Created attachment 1085749 [details]
Backtrace of crash
Sorry, thought I had installed everything with the debuginfo line from gdb.
backtrace doesn't immediately ring a bell with me, but we did do a lot of fixes upstream to layout crashes. I imagine this is from a docx and it might be something like a table in a footnote causing this problem. Can you attach the document which triggers this ?
I have sent the document to the email above. I don't think there were any tables in footnotes, but there were comments on text in tables.
the good news is that LO 5.0 does not crash since this commit:
Author: Caolán McNamara <email@example.com>
AuthorDate: Sat May 9 16:51:13 2015 +0100
bodge layout to not crash on load of File_1292.docx
the bad news is that LO 5.0 has an infinite loop in the layout,
while formatting a table, since the above commit...
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.