Bug 695582

Summary: [abrt] openoffice.org-writer-1:3.3.0-20.2.fc14: IA__gdk_x11_drawable_get_xid: Process /usr/lib/openoffice.org3/program/swriter.bin was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: 03
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: brandon.gardner, caolanm, dtardon, patrick.sefton
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:f0aac7d9a3282d4fe4681a59c4452b66cd8bc423
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-04-17 21:49:40 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 03 2011-04-12 05:22:33 UTC 
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 27201 bytes
cmdline: /usr/lib/openoffice.org3/program/swriter.bin -writer file:///home/sly/Downloads/Monster%20Letter.odt
component: openoffice.org
Attached file: coredump, 159285248 bytes
crash_function: IA__gdk_x11_drawable_get_xid
executable: /usr/lib/openoffice.org3/program/swriter.bin
kernel: 2.6.35.9-64.fc14.i686
package: openoffice.org-writer-1:3.3.0-20.2.fc14
rating: 4
reason: Process /usr/lib/openoffice.org3/program/swriter.bin was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
How to reproduce: I clicked on Ignore All on a word it didn't recognize.
time: 1302585010
uid: 500
Comment 1 03 2011-04-12 05:22:35 UTC 
Created attachment 491405 [details]
File: backtrace
Comment 2 David Tardon 2011-04-12 06:09:48 UTC 
Crashes on

GdkWindow* pWin = GTK_WIDGET(m_pWindow)->window;
if( pWin )
{
    aWin = GDK_WINDOW_XWINDOW(pWin);

so it's probably a Gtk bug. I suppose you cannot reproduce it?
Comment 3 David Tardon 2011-04-12 06:12:34 UTC 
*** Bug 620134 has been marked as a duplicate of this bug. ***
Comment 4 Caolan McNamara 2011-04-17 21:46:47 UTC 
*** Bug 585280 has been marked as a duplicate of this bug. ***
Comment 5 Caolan McNamara 2011-04-17 21:49:40 UTC 
Can't reproduce this one, probably a tricky one to track down, ideally need a reproducible scenario to assign blame correctly :-(