abrt 1.1.1 detected a crash. architecture: i686 Attached file: backtrace cmdline: /usr/lib/openoffice.org3/program/swriter.bin -writer component: openoffice.org crash_function: Window::~Window executable: /usr/lib/openoffice.org3/program/swriter.bin global_uuid: 76c50834beabfe424f6f75456f9d7c93be12a36f kernel: 2.6.33.5-124.fc13.i686.PAE package: openoffice.org-writer-1:3.2.0-12.24.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 426319 [details] File: backtrace
This one comes from file recovery dialog; I think we already got it (or one very similar to it) once, but we weren't able to determine why it crashed at that time. So, what did you do after that recovery dialog appeared?
*** Bug 568940 has been marked as a duplicate of this bug. ***
*** Bug 594931 has been marked as a duplicate of this bug. ***
Still not reproducible unfortunately. I've a vague feeling the obvious crash in the window dtor is due to the main loop not up and running yet. The window is clearly an error dialog appearing during startup. The real issue is why is there an error dialog in the first place. Which brings it back into the realm of configuration manager issues.