Bug 682966

Summary: [abrt] openoffice.org-writer-1:3.3.0-20.2.fc14: SwViewImp::StartAction: Process /usr/lib64/openoffice.org3/program/swriter.bin was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: marc <mmarcrr>
Component: openoffice.orgAssignee: Caolan McNamara <caolanm>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: caolanm, dtardon
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:84d4e5302b0794a69aa47ed0faf8510b31e7924c
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-29 14:20:54 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description marc 2011-03-08 06:33:13 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 212597 bytes
cmdline: /usr/lib64/openoffice.org3/program/swriter.bin -writer file:///tmp/34984392021EOIB1601%2020110302.doc
component: openoffice.org
Attached file: coredump, 129093632 bytes
crash_function: SwViewImp::StartAction
executable: /usr/lib64/openoffice.org3/program/swriter.bin
kernel: 2.6.35.10-74.fc14.x86_64
package: openoffice.org-writer-1:3.3.0-20.2.fc14
rating: 4
reason: Process /usr/lib64/openoffice.org3/program/swriter.bin was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1299519265
uid: 500

How to reproduce
-----
1.opening

2.
3.
Comment 1 marc 2011-03-08 06:33:19 UTC 
Created attachment 482842 [details]
File: backtrace
Comment 2 David Tardon 2011-03-08 08:14:38 UTC 
It crashed when you cancelled a print job. Did you do anything special, like printing a selection, comments etc.?

Note to myself: could be duplicate of bug 657783.
Comment 3 Caolan McNamara 2011-03-29 14:20:54 UTC 

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