GnuCash crashes when using online banking

Bug #1875679 reported by omriasta
42
This bug affects 8 people
Affects Status Importance Assigned to Milestone
KMyMoney
New
Undecided
Unassigned
gnucash (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

GnuCash Version 3.8 installed with upgrade to 20.04. Once installed online banking appears to cause gnucash to crash.
To troubleshoot I completely deleted the aqbanking folder in my home directory to start fresh. Started the Online banking setup wizard, created a user, once I select Retrieve Account List the software confirms the cert, then asks for password. Once the password is entered the software crashes and the following is logged:
Found Finance::Quote version 1.49.
* 11:40:51 ERROR <aqbanking> banking_update.c: 610: No AqBanking config folder found at [/home/xxxx/.aqbanking/settings6/users] (-1)
* 11:40:51 ERROR <aqbanking> banking_update.c: 610: No AqBanking config folder found at [/home/xxxx/.aqbanking/settings/users] (-1)
* 11:40:51 ERROR <aqbanking> banking_update.c: 411: There is no old settings folder, need initial setup
* 11:42:28 ERROR <gwenhywfar> pathmanager.c: 83: Path "aqhbci/xmldatadir" already exists
* 11:42:28 ERROR <gwenhywfar> dialog.c: 666: Widget [hbciInitChipcardRadio] not found
* 11:42:38 ERROR <> dlg_newuser.c: 1358: Activated: wiz_app_combo
* 11:42:41 ERROR <> dlg_newuser.c: 1358: Activated: wiz_next_button
* 11:42:46 ERROR <> dlg_newuser.c: 1358: Activated: wiz_bank_button
* 11:42:46 ERROR <> dlg_getinst.c: 386: Activated: listBox
* 11:42:47 ERROR <> dlg_getinst.c: 432: Changed nameEdit
* 11:42:48 ERROR <> dlg_getinst.c: 432: Changed nameEdit
* 11:42:48 ERROR <> dlg_getinst.c: 432: Changed nameEdit
* 11:42:48 ERROR <> dlg_getinst.c: 432: Changed nameEdit
* 11:42:48 ERROR <> dlg_getinst.c: 432: Changed nameEdit
* 11:42:48 ERROR <> dlg_getinst.c: 432: Changed nameEdit
* 11:42:48 ERROR <> dlg_getinst.c: 432: Changed nameEdit
* 11:42:50 ERROR <> dlg_getinst.c: 386: Activated: listBox
* 11:42:55 ERROR <> dlg_getinst.c: 386: Activated: okButton
* 11:43:05 ERROR <> dlg_newuser.c: 1358: Activated: wiz_next_button
* 11:43:12 ERROR <> dlg_newuser.c: 1358: Activated: wiz_next_button
* 11:43:36 ERROR <> dlg_newuser.c: 1358: Activated: wiz_next_button
* 11:43:39 ERROR <> dlg_newuser.c: 1358: Activated: wiz_next_button
* 11:43:39 ERROR <> dlg_newuser.c: 965: Doit
* 11:43:39 ERROR <> dlg_newuser.c: 970: Creating user
* 11:43:39 ERROR <> dlg_newuser.c: 1001: Adding user
* 11:43:39 ERROR <> dlg_newuser.c: 1018: Locking user
* 11:43:45 ERROR <> dlg_newuser.c: 1055: Unlocking user
* 11:43:49 ERROR <> dlg_newuser.c: 1358: Activated: wiz_getaccounts_button
* 11:43:55 ERROR <gwenhywfar> dialog.c: 695: Widget [storePasswordCheck] not found
gnucash: buffer.c:275: GWEN_Buffer_GetUsedBytes: Assertion `bf' failed.
Aborted (core dumped)

Revision history for this message
suanccd (suanccd) wrote :

I have exact same problem, after upgraded from from 18.04 LTS to 20.04 LTS. What I found out is that Gnucash v3.8 in 20.04 LTS uses aqbanking6, which is quite new, and maybe not fully tested.
I have temporarily switched back to 19.10, which has Gnucash v3.7 with older aqbanking.

Revision history for this message
suanccd (suanccd) wrote :

BTW, I am in US so I use OFX.
See below, which mentioned the status of OFX DirectConnect.
https://www.aquamaniac.de/rdm/projects/aqbanking/wiki/AqBanking6

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnucash (Ubuntu):
status: New → Confirmed
Revision history for this message
omriasta (omriasta) wrote :

Seems odd that they would release gnucash 3.8 which is not compatible with previous aqbanking and aqbanking6 is at a state where ofx directconnect is not working or even tested. Is there any way to downgrade just gnucash and aqbanking without having to downgrade the entire distro?

Revision history for this message
omriasta (omriasta) wrote :

OK, so just installed gnucash 3.10 using flatpak and it works without crashing, I am assuming also using AQBanking6 so this is specific to gnucash 3.8 or maybe just the ubuntu package....

Revision history for this message
suanccd (suanccd) wrote :

I was able to compile and install the following packages, with sources from 19.10. It is working for me under 20.04.
./gnucash/python3-gnucash_3.7-1ubuntu1_amd64.deb
./gnucash/gnucash-common_3.7-1ubuntu1_all.deb
./gnucash/gnucash_3.7-1ubuntu1_amd64.deb
./gwenhywfar/libgwenhywfar60-dev_4.20.0-9_amd64.deb
./gwenhywfar/libgwenhywfar60_4.20.0-9_amd64.deb
./gwenhywfar/libgwenhywfar-doc_4.20.0-9_all.deb
./gwenhywfar/libgwengui-cpp0_4.20.0-9_amd64.deb
./gwenhywfar/libgwengui-fox16-dev_4.20.0-9_amd64.deb
./gwenhywfar/libgwenhywfar-core-dev_4.20.0-9_amd64.deb
./gwenhywfar/libgwengui-fox16-0_4.20.0-9_amd64.deb
./gwenhywfar/libgwengui-gtk3-0_4.20.0-9_amd64.deb
./gwenhywfar/gwenhywfar-tools_4.20.0-9_amd64.deb
./gwenhywfar/libgwengui-gtk3-dev_4.20.0-9_amd64.deb
./gwenhywfar/libgwengui-qt5-dev_4.20.0-9_amd64.deb
./gwenhywfar/libgwenhywfar-data_4.20.0-9_all.deb
./gwenhywfar/libgwengui-qt5-0_4.20.0-9_amd64.deb
./aqbanking/libaqofxconnect7_5.8.2-0.1_amd64.deb
./aqbanking/libaqbanking-dev_5.8.2-0.1_amd64.deb
./aqbanking/libaqbanking-data_5.8.2-0.1_all.deb
./aqbanking/libaqhbci24_5.8.2-0.1_amd64.deb
./aqbanking/libaqbanking35-plugins_5.8.2-0.1_amd64.deb
./aqbanking/aqbanking-tools_5.8.2-0.1_amd64.deb
./aqbanking/libaqbanking-doc_5.8.2-0.1_all.deb
./aqbanking/libaqbanking35_5.8.2-0.1_amd64.deb
./aqbanking/libaqebics0_5.8.2-0.1_amd64.deb

Revision history for this message
Jason Thompson (jason-jasonandmary) wrote :

When I use kmymoney to import transactions, I get the same error.

affects: gnucash → kmymoney
Revision history for this message
SirG (sirg-nj) wrote :

Same problem after upgrading to Mint 20.04.

Workaround-ish:
- remove/rename ~/.aqbanking/setting6 directory
- install flatpak GnuCash 4.0

I got re-prompted for the password and to accept the cert, everything else just worked.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.