Bug 607286

Summary: [abrt] crash in Window::~Window: Error dialog before startup complete (SIGSEGV)
Product: [Fedora] Fedora Reporter: Glauco Amorim <glauco.amorim>
Component: openoffice.orgAssignee: Caolan McNamara <caolanm>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: caolanm, dtardon, oido.de.burro, rfox60
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:76c50834beabfe424f6f75456f9d7c93be12a36f
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-07-01 19:40:28 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Attachments:
Description Flags
File: backtrace none

Description Glauco Amorim 2010-06-23 17:23:32 UTC 
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)
Comment 1 Glauco Amorim 2010-06-23 17:23:38 UTC 
Created attachment 426319 [details]
File: backtrace
Comment 2 David Tardon 2010-06-23 18:21:44 UTC 
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?
Comment 3 Caolan McNamara 2010-06-23 19:19:59 UTC 
*** Bug 568940 has been marked as a duplicate of this bug. ***
Comment 4 Caolan McNamara 2010-06-23 19:20:13 UTC 
*** Bug 594931 has been marked as a duplicate of this bug. ***
Comment 5 Caolan McNamara 2010-07-01 19:40:28 UTC 
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.