Bug 709493

Summary: [abrt] openoffice.org-brand-1:3.3.0-20.5.fc14: g_type_check_instance_cast: Process /usr/lib/openoffice.org3/program/soffice.bin was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Ken Jones <ken.jones>
Component: openoffice.orgAssignee: Caolan McNamara <caolanm>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: caolanm, dtardon
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:bc7127c76d763cb92363285d86e42d633204b20a
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-17 15:24:12 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 Ken Jones 2011-05-31 19:54:01 UTC 
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 53589 bytes
cmdline: /usr/lib/openoffice.org3/program/soffice.bin -quickstart -nologo -nodefault
component: openoffice.org
Attached file: coredump, 118865920 bytes
crash_function: g_type_check_instance_cast
executable: /usr/lib/openoffice.org3/program/soffice.bin
kernel: 2.6.35.13-91.fc14.i686
package: openoffice.org-brand-1:3.3.0-20.5.fc14
rating: 4
reason: Process /usr/lib/openoffice.org3/program/soffice.bin was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1306871502
uid: 500

How to reproduce
-----
1.Attempted to open a file with a .odg extension.
2.
3.
Comment 1 Ken Jones 2011-05-31 19:54:03 UTC 
Created attachment 502088 [details]
File: backtrace
Comment 2 David Tardon 2011-06-01 07:23:50 UTC 
You did press Cancel, not OK, though .-) I don't suppose you can reproduce the crash?
Comment 3 Ken Jones 2011-06-01 14:54:13 UTC 
(In reply to comment #2)
> You did press Cancel, not OK, though .-) I don't suppose you can reproduce the
> crash?

I have tried six times to reproduce it, but have not been able to so far.
Comment 4 Caolan McNamara 2011-06-17 15:24:12 UTC 
worrying, but I'm clueless here :-(. Maybe an instance of the "quickstarter active during upgrade", in which case that should be ok for the future cases. Uncertain if that's anything to do with this however.