Bug 661249

Summary: [abrt] openoffice.org-brand-1:3.3.0-17.2.fc14: GDIMetaFile::Rotate: Process /usr/lib/openoffice.org3/program/soffice.bin was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Bengt Sjögren <bengt.sjogren>
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:ebb0b9d319ad2d802c63fb3bf7e84f88f4f00fa8
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-12-08 11:02:01 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 Bengt Sjögren 2010-12-08 10:16:21 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: /usr/lib/openoffice.org3/program/soffice.bin -quickstart -nologo -nodefault
component: openoffice.org
crash_function: GDIMetaFile::Rotate
executable: /usr/lib/openoffice.org3/program/soffice.bin
kernel: 2.6.35.6-48.fc14.i686.PAE
package: openoffice.org-brand-1:3.3.0-17.2.fc14
rating: 4
reason: Process /usr/lib/openoffice.org3/program/soffice.bin was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1291646317
uid: 500

How to reproduce
-----
1. I just started OpenOffice
2.
3.
Comment 1 Bengt Sjögren 2010-12-08 10:16:24 UTC 
Created attachment 467432 [details]
File: backtrace
Comment 2 David Tardon 2010-12-08 10:55:25 UTC 
Did you update before that (and without restart)? I bet this is another instance of bug 610103 and the stack is just misleading...
Comment 3 Caolan McNamara 2010-12-08 11:02:01 UTC 
I'd say so, looks like using a different debuginfo than the exact crashing binary.

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