GnuCash
Contact   Instructions
Bug 797281 - Gnucash crashes when attempting to match online accounts
Summary: Gnucash crashes when attempting to match online accounts
Status: RESOLVED FIXED
Alias: None
Product: GnuCash
Classification: Unclassified
Component: Import - AqBanking (show other bugs)
Version: 3.5
Hardware: PC Mac OS
: Normal normal
Target Milestone: ---
Assignee: import
QA Contact: import
URL:
Whiteboard:
Keywords:
: 797305 (view as bug list)
Depends on:
Blocks:
 
Reported: 2019-06-19 22:30 EDT by Dawid Wrobel
Modified: 2019-07-07 11:13 EDT (History)
5 users (show)

See Also:


Attachments
macOS crash log (78.06 KB, text/plain)
2019-06-19 22:30 EDT, Dawid Wrobel
no flags Details

Description Dawid Wrobel 2019-06-19 22:30:24 EDT
Created attachment 373301 [details]
macOS crash log

I am unable to match online accounts with GnuCash accounts when setting up banking. 

The app crashes immediately after pressing Next while on Start Online Banking Wizard page.

Build ID: 3.5+(2019-03-30) on macOS 10.14.5

Crash log attached.
Comment 1 John Ralls 2019-06-19 23:31:47 EDT
You chopped off the top of the crash report, the part with the error and the MacOS version you're running. Please either attach it or paste it into a comment.

In what language are you running GnuCash and what is the name of the bank you were trying to set up?
Comment 2 Dawid Wrobel 2019-06-20 09:42:40 EDT
The bug writing guideline (https://bugs.gnucash.org/page.cgi?id=bug-writing.html) explicitly asks for Thread 0 information only, I guess I misunderstood. 

The missing bit is below. I use US English. I am not even at the point when I get to choose any bank when it crashes. I just open the dialog (Tools ->Online Banking Setup), hit Next, hit Next again and it goes off immediately.


Process:               Gnucash [76107]
Path:                  /Applications/Gnucash.app/Contents/MacOS/Gnucash
Identifier:            org.gnucash.Gnucash
Version:               3.5-1 (3.5-1)
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           Gnucash [76107]
User ID:               501

Date/Time:             2019-06-19 22:26:37.452 -0400
OS Version:            Mac OS X 10.14.5 (18F132)
Report Version:        12
Bridge OS Version:     3.0 (14Y901)
Anonymous UUID:        755B5004-220A-3076-1056-249C360914DB

Sleep/Wake UUID:       7DB944CF-DFD5-4D1A-900D-081B02A05154

Time Awake Since Boot: 880000 seconds
Time Since Wake:       15000 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Application Specific Information:
abort() called
Gnucash(76107,0x110e405c0) malloc: *** error for object 0x114e3fcae: pointer being freed was not allocated
Comment 3 John Ralls 2019-06-20 10:26:18 EDT
Thanks for the top of the report, that's very helpful.

What you're describing can't happen. The Next button on the second screen is disabled until you at least create a user and an account with the AQBanking Wizard, which you run by clicking the button Start AqBanking Wizard above the Cancel and Next buttons. Perhaps you'd done that in a previous session?

Open a Finder window and select Go>Go to Folder and in the dialog box type
  ~/.aqbanking/settings
and click Go.

If there's an accounts folder, click that. Is there anything in it?
Comment 4 John Ralls 2019-06-20 10:45:36 EDT
Meanwhile, I've found the erroneous free() that caused the crash and fixed it.
Comment 5 Dawid Wrobel 2019-06-20 12:35:40 EDT
John, yes, I have previously created multiple users and accounts successfully. In fact, I think I created one a few weeks back and was able to assign it to an existing GnuCash account. It just started to crash very recently.
Comment 6 John Ralls 2019-06-20 15:13:50 EDT
"Recently" probably means since you upgraded to GnuCash 3.5 as that's when that bug crawled in.

To work around it open the AQBanking Setup Wizard, switch to the Accounts tab and add a name to any accounts where the Bank Name field is blank.
Comment 7 Dawid Wrobel 2019-06-20 15:26:35 EDT
Indeed that helped. Thanks!
Comment 8 John Ralls 2019-07-07 11:13:31 EDT
*** Bug 797305 has been marked as a duplicate of this bug. ***

Note You need to log in before you can comment on or make changes to this bug.