abrt 1.1.1 detected a crash. architecture: x86_64 Attached file: backtrace cmdline: /usr/lib64/openoffice.org3/program/scalc.bin -calc component: openoffice.org crash_function: IA__gdk_x11_drawable_get_xid executable: /usr/lib64/openoffice.org3/program/scalc.bin global_uuid: afed9911e76e591dc90a84a979aa88ab549a0f12 kernel: 2.6.32.16-141.fc12.x86_64 package: openoffice.org-calc-1:3.1.1-19.34.fc12 rating: 4 reason: Process /usr/lib64/openoffice.org3/program/scalc.bin was killed by signal 11 (SIGSEGV) release: Fedora release 12 (Constantine) How to reproduce ----- 1. Single document loaded in Writer 2. Right-clicked misspelled (red-underlined) word 3. Expected context-menu to appear 4. Context menu did not appear 5. Writer crashed
Created attachment 435833 [details] File: backtrace
Doesn't happen here of course, so rare incident. It crashes in gtk2 at... if( pWin ) { aWin = GDK_WINDOW_XWINDOW(pWin); non NULL pWin. I have to assume that pWin is valid here. Did it happen just once, or does it happen every time for you ?
(In reply to comment #2) > Doesn't happen here of course, so rare incident. It crashes in gtk2 at... > > if( pWin ) > { > aWin = GDK_WINDOW_XWINDOW(pWin); > > non NULL pWin. I have to assume that pWin is valid here. > > Did it happen just once, or does it happen every time for you ? No, doesn't happen every time, but does happen intermittently. Can't duplicate it at present, but the common factor when this happens is that it occurs when I have previously opened a document within Firefox (ie so that that doc appears as editable using writer within the Firefox window or tab). Then the crash happens when I go back to doing something in the Writer main window. Sorry -- not super helpful I know. I'll see if I can reliably duplicate the crash.
Looks like a gtk bug to me, but seeing as you mention firefox, I see that firefox has a long history of "gdk_x11_drawable_get_xid" bugs in F-12. I strongly suspect that its the same issue *** This bug has been marked as a duplicate of bug 547790 ***
*** This bug has been marked as a duplicate of bug 695582 ***