Bug 714825 - [abrt] openoffice.org-writer-1:3.3.0-20.5.fc14: Process /usr/lib64/openoffice.org3/program/swriter.bin was killed by signal 11 (SIGSEGV)
Summary: [abrt] openoffice.org-writer-1:3.3.0-20.5.fc14: Process /usr/lib64/openoffice...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: openoffice.org
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:d5423dcce3571007d2f65ef0703...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-20 22:21 UTC by Sailor Ripley
Modified: 2011-08-09 13:13 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-08-09 13:13:08 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (51.29 KB, text/plain)
2011-06-20 22:21 UTC, Sailor Ripley 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Sailor Ripley 2011-06-20 22:21:02 UTC 
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 52517 bytes
cmdline: /usr/lib64/openoffice.org3/program/swriter.bin -writer /home/jcorreia/Downloads/JoseCarlosCorreia_201106_GFI_ArqAnaliseFunc_PT_EU.odt
component: openoffice.org
Attached file: coredump, 253825024 bytes
executable: /usr/lib64/openoffice.org3/program/swriter.bin
kernel: 2.6.35.13-92.fc14.x86_64
package: openoffice.org-writer-1:3.3.0-20.5.fc14
rating: 4
reason: Process /usr/lib64/openoffice.org3/program/swriter.bin was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1308605412
uid: 500

How to reproduce
-----
1. Crash happened after saving a file in .ppt
2.
3.
Comment 1 Sailor Ripley 2011-06-20 22:21:05 UTC 
Created attachment 505713 [details]
File: backtrace
Comment 2 Caolan McNamara 2011-06-21 08:12:33 UTC 
Are you able to reproduce this, i.e. able to attach a .odp which causes this to happen on export to .ppt
Note You need to log in before you can comment on or make changes to this bug.