Bug 695582 - [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)
Summary: [abrt] openoffice.org-writer-1:3.3.0-20.2.fc14: IA__gdk_x11_drawable_get_xid:...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: openoffice.org
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:f0aac7d9a3282d4fe4681a59c44...
: 585280 620134 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-12 05:22 UTC by 03
Modified: 2011-04-17 21:49 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-04-17 21:49:40 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (26.56 KB, text/plain)
2011-04-12 05:22 UTC, 03 		no flags Details
View All

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 :-(
Note You need to log in before you can comment on or make changes to this bug.