Bug 673373 - Gnucash 2.4.0 hard crashes during report generation
Summary: Gnucash 2.4.0 hard crashes during report generation
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: gnucash
Version: 14
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-27 23:06 UTC by Scot Stafford
Modified: 2014-03-17 03:26 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-21 15:40:45 UTC
Type: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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.
Note You need to log in before you can comment on or make changes to this bug.