Bug 673373

Summary: Gnucash 2.4.0 hard crashes during report generation
Product: [Fedora] Fedora Reporter: Scot Stafford <sj-stafford>
Component: gnucashAssignee: Bill Nottingham <notting>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 14CC: notting, rvokal, sj-stafford
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-02-21 15:40:45 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Scot Stafford 2011-01-27 23:06:55 UTC 
Description of problem: 
Gnucash crashes with no indication in ABRT when generating a report. This happens will all Gnucash reports. My uneducated guess is a x86_64 vs. i386 dependency problem with WebKit. My Fedora is completely up to date as of this writing. This only started when Gnucash updated to the new 2.4 series.


Version-Release number of selected component (if applicable): 
2.4.0 r19974M on 2011-01-03


How reproducible: very


Steps to Reproduce:
1. Open Gnucash
2. Run a report
3.
  
Actual results:
Hard crash. ABRT does not pick up the crash.


Expected results:
The selected report should appear.


Additional info:
This is my first bug report, please go easy on me if I did not provide enough information, or have duplicated a bug report ( I did search for this bug first).
Comment 1 Bill Nottingham 2011-02-01 17:45:39 UTC 
Is it possible to run it under gdb and get a trace that way? Without any sort of backtrace, it's not really possible to debug it.
Comment 2 Scot Stafford 2011-02-21 15:40:45 UTC 
After loading all debuginfo packages as required for gdb, it failed once ... and then is working fine. I don't understand it. Version 2.4.0 "healed itself" miraculously and 2.4.2 is working fine. Please close this bug report and thanks to those who replied.