Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1830609
Summary: | aqbanking crashes gnucash | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Henrique Martins <fedora> |
Component: | aqbanking | Assignee: | Bill Nottingham <notting> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 32 | CC: | amessina, jhaiduce, notting, rdieter |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | aqbanking-6.1.4-1.fc32 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-05-12 03:07:55 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Henrique Martins
2020-05-03 00:37:56 UTC
IMHO, let's give aqbanking at least a chance to address the issue before being drastic to revert things and lose features. Fwiw, aqbanking was updated add support for new requirements from many banks (downgrading would cause loss of functionality for those users). Meanwhile I can't use gnucash's online functions, my fault for updating :-) Aqbanking6's README file does say: PLEASE NOTE: AqBanking6 is work in progress, it is by no means stable or fit for use in production That's unfortunate. In the meantime, I'll prepare builds of the latest releases for testing, aqbanking-6.1.4, gwenhywfar-5.3.0.tar.gz See https://bugzilla.redhat.com/show_bug.cgi?id=1743038#c9, I thought 6 was for rawhide, not F32. It was rawhide at the time, that was prior to f32 branching. Here's a reference to an example bug about the newer features that required v6, bug #1763485 Nothing jumps out at me on https://aquamaniac.de/rdm/projects/aqbanking/issues?set_filter=1&tracker_id=1 about this being a known issue, but I'm not fluent in German either. Thus FC32/Aqbanking6 works for people in Europe (Germany?) that use some non-OFX connect type of access to their European bank and it's broken for people in the USA that mostly use OFX to access USA banks. More links, https://lists.gnucash.org/pipermail/gnucash-user/2019-December/088350.html "just a general note on AqBanbkings OFX DirectConnect plugin: Development on this plugin is pretty much on hold right now..." Sounds like there is no good choice here: * stay indefinitely on an older aqbanking stack. PROS: Working ofx * Follow latest aqbanking development. PROS: aqbanking upstream support, new features (like PSD2). CONS: OFX feature development stalled, with regressions I'll defer to Bill how he wants to handle reverting or not. I'm OK with either option. My tentative take: regressions suck... a lot. So, consider reverting things for F32 release, and rawhide? Probably revert there too? Tough call. Corollary: create COPR with latest aqbanking builds (and dependencies, gnucash/kmymoney mostly), for stable fedora releases. Users who want/need these new features then can opt-in to have them. Thoughts, opinions? Picked up aqbanking-6.1.4-1.fc33.x86_64 and gwenhywfar-5.3.0-1.fc33.x86_64 from koji. OFX works. Maybe the plugin is not on hold anymore? Close the ticket when this is pushed to stable? Sigh, sorry for spam, https://bugs.gnucash.org/show_bug.cgi?id=797713#c10 Looks like latest aqbanking/gwenhywfar does fix the issue at hand, that's excellent news. I think that's the best way forward in the short term. I'll prep f32 updates. Thanks Rex! (You did create those f33 rpms.) Yeah, COPR would definitely be a last resort, as the ABI changes means you need to build *everything*. I'm good with a roll-forward to latest if it works. FEDORA-2020-24e4addb7e has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-24e4addb7e FC32 builds also works with my bank FEDORA-2020-24e4addb7e has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-24e4addb7e` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-24e4addb7e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. Had to re-do setup, but this did work for me as well. FEDORA-2020-24e4addb7e has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report. Still getting an error after updating to aqbanking-6.1.4-1.fc32. GnuCash doesn't crash for me, but it issues the error: "error on executing job. status: enqueued (1)" Try the following. - exit gnucash - remove (or rename or move, just in case) the ~/.aqbanking/settings6 directory - try again (In reply to Henrique Martins from comment #19) > Try the following. > - exit gnucash > - remove (or rename or move, just in case) the ~/.aqbanking/settings6 > directory > - try again Thanks Henrique. I got it working by a different method: - Opened Online Banking Setup in Gnucash - Click Next, open the Aqbanking setup wizard - Select "Edit User" - Go to the "Bank Settings" tab - Clicked "Retrieve Account List" |