Description of problem: My credit card account was closed and a new one was issued. In aqbanking I deleted the former account and downloaded the new one Pressing the aqbanking forward button expecting to assign the new account to a gnucash account caused the crash. Version-Release number of selected component: gnucash-2.4.15-1.fc19 Additional info: reporter: libreport-2.2.1 backtrace_rating: 4 cmdline: gnucash crash_function: AB_Banking__char2uint64 executable: /usr/bin/gnucash kernel: 3.13.11-100.fc19.i686.PAE runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 AB_Banking__char2uint64 at banking_account.c:350 #1 AB_Banking_GetAccountByCodeAndNumber at banking_account.c:404 #2 gnc_ab_get_ab_account at gnc-ab-utils.c:279 #3 gnc_ab_getbalance at gnc-ab-getbalance.c:79 #4 gnc_plugin_ab_cmd_get_balance at gnc-plugin-aqbanking.c:451 #10 _gtk_action_emit_activate at gtkaction.c:795 #11 gtk_action_activate at gtkaction.c:826 #12 g_cclosure_marshal_VOID__VOIDv at gmarshal.c:115 #13 g_type_class_meta_marshalv at gclosure.c:997 #14 _g_closure_invoke_va at gclosure.c:840
Created attachment 899098 [details] File: backtrace
Created attachment 899099 [details] File: cgroup
Created attachment 899100 [details] File: core_backtrace
Created attachment 899101 [details] File: dso_list
Created attachment 899102 [details] File: environ
Created attachment 899103 [details] File: exploitable
Created attachment 899104 [details] File: limits
Created attachment 899105 [details] File: maps
Created attachment 899106 [details] File: open_fds
Created attachment 899107 [details] File: proc_pid_status
Created attachment 899108 [details] File: var_log_messages
Another user experienced a similar problem: My Discover card had to be re-issued with a new account number. So I tried to change the account number in aqbanking. I did this: 1. Tools > Online Banking Setup.. 2. Started the AqBanking Wizard 3. Went to the Accounts tab 4. Deleted the old Discover account 5. Went to the Users tab 6. Selected the Discover Card user, pressed the Edit User button. 7. Went to the Bank Setting tab 8. Pressed Retrieve Accounts List..seemed to go through successfully. The new account number came through. 9. Closed the Wizard 10. Pressed the "Forward" button..CRASH Gnucash continues to crash everytime I try to go ahead past the Forward in order to set up the Account with the new online banking information. If I try Actions > Online Actions on my Discover account, it crashes. All my other on-line accounts Online Actions still work!! I tried "aqbanking-cli request .. --balance" on the new Discover Card account name and successfully retried the account balance. At this point, it appears this Discover account is broken as far as Gnucash on-line transactions and I cannot set up new accounts. reporter: libreport-2.2.1 backtrace_rating: 4 cmdline: gnucash crash_function: AB_Banking__char2uint64 executable: /usr/bin/gnucash kernel: 3.13.11-100.fc19.i686.PAE package: gnucash-2.4.15-1.fc19 reason: gnucash killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
After stack trace analysis I found that the old card number was still in the gnucash file. Gnucash was crashing when it did not find the old number in the aqbanking files. So I caused this problem by deleting the old account in the aqbanking wizard. I guessed wrong as to how change to the new card number. I guess I should added the new account and then removed the old one later. Hand editing the gnucash file and changing the old for new put me back in business. This should still be a bug. Gnucash should not crash when something does not line up with the aqbanking accounts.
I've tried to reproduce this failure with 2.6.x on F20 and failed. I'll see if I can put a 2.6.x build for F19 up for you to test.
https://kojipkgs.fedoraproject.org//work/tasks/9521/6909521/gnucash-2.6.3-1.fc19.i686.rpm
No 2.6.x crashes also. I installed the 2.6.x package on a different F19 instance. I copied over the working accounts and verified that I could Actions > Online > get balance from an active account. Everything else seemed to work as well. I then: 1. went into Tools > Online Banking Setup.. 2. Started the AqBanking Wizard 3. Went to the Accounts tab 4. Deleted the above working account 5. Closed the Wizard 6. Pressed the "Forward" button..CRASH
OK; it works for me in my testing, albeit with a different OFX direct connect account. One other variable (my test setup is F20 at the moment) would be aqbanking versions - I assume https://kojipkgs.fedoraproject.org//work/tasks/139/6910139/aqbanking-5.3.2-0.1.beta.fc19.i686.rpm probably wouldn't fix it for you, but it's worth a shot. I'll file this upstream as well.
Looks like when I installed the 2.6 gnucash it also brought down aqbanking-5.3.2-0.1.beta.fc19 # yum list installed gnucash* aqbanking* Loaded plugins: langpacks, refresh-packagekit Installed Packages aqbanking.i686 5.3.2-0.1.beta.fc19 @updates gnucash.i686 2.6.3-1.fc19 @/gnucash-2.6.3-1.fc19.i686 gnucash-docs.noarch 2.4.2-1.fc19 @fedora So no, it was crashing even with the newer aqbanking. Looks like it is time to file it upstream. Thanks for your help. P.S. I also brought this up in the gnucash-user list. They felt it was a bug also.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.