Bug 664946

Summary: [abrt] openoffice.org-writer-1:3.3.0-17.2.fc14: SwXTextSection::attach: Process /usr/lib/openoffice.org3/program/swriter.bin was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Yakov <ooki2day>
Component: openoffice.orgAssignee: Caolan McNamara <caolanm>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: caolanm, dtardon
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:15c159cb2c4234c8efac67ff2be5d252e430edf1
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-12-23 13:11:51 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Yakov 2010-12-22 09:19:11 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: /usr/lib/openoffice.org3/program/swriter.bin -writer '/media/1/\xd0\xa1\xd0\x90\xd0\x9e\xd0\x94/\xd0\x9c\xd0\xa3\xd0\x9b\xd0\xa0_\xd0\xa1\xd0\x90\xd0\x9e\xd0\x94_2003.doc'
component: openoffice.org
crash_function: SwXTextSection::attach
executable: /usr/lib/openoffice.org3/program/swriter.bin
kernel: 2.6.35.9-64.fc14.i686
package: openoffice.org-writer-1:3.3.0-17.2.fc14
rating: 4
reason: Process /usr/lib/openoffice.org3/program/swriter.bin was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1293005470
uid: 500

How to reproduce
-----
1.Try to open .docx
2.
3.
Comment 1 Yakov 2010-12-22 09:19:14 UTC 
Created attachment 470159 [details]
File: backtrace
Comment 2 Caolan McNamara 2010-12-22 10:16:38 UTC 
Can you attach a sample .docx which causes this crash ?
Comment 3 Yakov 2010-12-23 13:07:52 UTC 
I do not can. file is removed. I opened him from the archive .rar
Comment 4 David Tardon 2011-01-04 11:09:57 UTC 

*** This bug has been marked as a duplicate of bug 667082 ***