abrt 1.1.1 detected a crash. architecture: i686 Attached file: backtrace cmdline: /usr/lib/openoffice.org3/program/swriter.bin -writer file:///home/bvn/my/Documents/office%20migration%20project/2010%20bamboo%20touch%20log.odt comment: I don't know what I did. I just finished a forum posting and was shutting down the open windows (just prior to a re-boot back to FC11) when I noticed this. component: openoffice.org crash_function: Application::GetSolarMutex executable: /usr/lib/openoffice.org3/program/swriter.bin global_uuid: 13bf3b8d4440b5173b69e06ec5f8adaa62fb10e1 kernel: 2.6.33.5-112.fc13.i686.PAE package: openoffice.org-writer-1:3.2.0-12.23.fc13 rating: 4 reason: Process /usr/lib/openoffice.org3/program/swriter.bin was killed by signal 11 (SIGSEGV) release: Fedora release 13 (Goddard)
Created attachment 421181 [details] File: backtrace
Accessibility is enabled, and on shutdown there was a crash. Of course that solarmutex is gone by the time the shutdown stuff shows up.
Hmm, I guess we could stuff something into atk_object_wrapper_finalize to not release anything if we're already past exit, and layer more horrors on horrors.
I don't think that explicitly calling gnome_accessibility_module_init/gnome_accessibility_module_shutdown would affect spi_atk_bridge_exit_func being registered as an atexit handler, and continuing to trundle around the place at a fairly arbitrary exit point
*** Bug 640314 has been marked as a duplicate of this bug. ***
As far as I can tell, the new gtk2 a11y stack in F15 appears to fix this problem.