Bug 611567 - [abrt] crash in openoffice.org-writer-1:3.2.0-12.25.fc13: SwXText::convertToTextFrame: Process /usr/lib64/openoffice.org3/program/swriter.bin was killed by signal 11 (SIGSEGV)
[abrt] crash in openoffice.org-writer-1:3.2.0-12.25.fc13: SwXText::convertToT...
Product: Fedora
Classification: Fedora
Component: openoffice.org (Show other bugs)
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Caolan McNamara
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-07-05 13:47 EDT by Tim Püschel
Modified: 2010-07-19 11:16 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-07-19 11:16:59 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (22.07 KB, text/plain)
2010-07-05 13:47 EDT, Tim Püschel
no flags Details

  None (edit)
Description Tim Püschel 2010-07-05 13:47:51 EDT
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/openoffice.org3/program/swriter.bin -writer file:///tmp/Zeugnis-1.docx
component: openoffice.org
crash_function: SwXText::convertToTextFrame
executable: /usr/lib64/openoffice.org3/program/swriter.bin
global_uuid: bdbde505c7f86029c07f5017a84a86eacc4b5b82
package: openoffice.org-writer-1:3.2.0-12.25.fc13
rating: 4
reason: Process /usr/lib64/openoffice.org3/program/swriter.bin was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
1. Try to open certain .docx-files
Comment 1 Tim Püschel 2010-07-05 13:47:54 EDT
Created attachment 429569 [details]
File: backtrace
Comment 2 Caolan McNamara 2010-07-05 15:00:13 EDT
This is a crash on import of a particular .docx. Can you attach the .docx which triggers the crash ?
Comment 3 Caolan McNamara 2010-07-19 11:16:59 EDT
We'd need the example .docx to be able to reproduce this in order to attempt to fix it :-(

Note You need to log in before you can comment on or make changes to this bug.