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)
Summary: [abrt] crash in openoffice.org-writer-1:3.2.0-12.25.fc13: SwXText::convertToT...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: openoffice.org
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:bdbde505c7f86029c07f5017a84...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-05 17:47 UTC by Tim Püschel
Modified: 2010-07-19 15:16 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-07-19 15:16:59 UTC
Type: ---
Embargoed:

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

Description Tim Püschel 2010-07-05 17:47:51 UTC 
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
kernel: 2.6.33.5-124.fc13.x86_64
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
2.
3.
Comment 1 Tim Püschel 2010-07-05 17:47:54 UTC 
Created attachment 429569 [details]
File: backtrace
Comment 2 Caolan McNamara 2010-07-05 19:00:13 UTC 
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 15:16:59 UTC 
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.