HBCI doesn't work on Gnucash 2.2.9 and libaqbanking 4.1.2

Bug #426685 reported by Norbert
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
GnuCash
Fix Released
Critical
gnucash (Ubuntu)
Fix Released
Undecided
Unassigned
Nominated for Karmic by Micha Lenk

Bug Description

Binary package hint: gnucash

I cant sent a accout transfer via online banking to my bank (I use Ubuntu 9.10).

The query for the account transactions are working fine. And the assistant to set up the aqbanking-settings works also.

But when I sent a transfer the online banking is not working. I found this messagges in the /tmp/gnucash.trace:

* 09:54:18 WARN <aqhbci> jobsingletransfer.c: 652: No local name, filling in
* 09:54:18 WARN <aqhbci> msgengine.c: 388: SystemId requested (deprecated)
* 09:54:18 WARN <aqbanking> de.c: 116: Bank data for KtoBlzCheck not found (-51), falling back to default
* 09:54:18 CRIT <aqhbci> msgcrypt_pintan.c: 252: Error getting pin from medium (-67)
* 09:54:18 CRIT <aqhbci> jobqueue.c: 442: Could not encode message (-67)
* 09:54:18 CRIT <aqhbci> outbox.c: 1410: Error performing queue (-1)
* 09:54:18 CRIT <aqhbci> jobsingletransfer.c: 1556: No segment results
* 09:54:18 WARN <aqbanking> banking_online.c: 141: Not a single job successfully executed

An this is answer from the gnucash mailing list:

---------------------------------
Martin Preuss schrieb:
> On Montag, 7. September 2009, Norbert Holze wrote:
> [...]
>> * 10:01:18 CRIT <aqhbci> msgcrypt_pintan.c: 252: Error getting pin
>> from medium (-67)
> [...]
>
> "-67" ist "NOT_IMPLEMENTED", soll heissen: In GnuCash wurde ein callback nicht
> gesetzt...

... oh, ja. - Ganz offensichtlich ein Programmierfehler in Gnucash.

Du solltest das Problem definitiv als Ubuntu-Bug berichten (unter
https://bugs.launchpad.net/ubuntu/+source/gnucash/+filebug ), evtl. wird
das ja noch in Ubuntu 9.10 behoben bevor es veröffentlicht wird.
----------------------------------

At Jaunty, Gnucash 2.2.9 form getdeb worked fine.

Norbert (asterix52)
description: updated
Revision history for this message
Norbert (asterix52) wrote :

Hi!

I got the information from the maillinglist that this patch for libaqbanking > 4.x is nessarry. Or Gnucash version > 2.3.2 (unstable).

This is bugreport for gnucash: https://bugzilla.gnome.org/show_bug.cgi?id=582048

Please add this patch for Ubuntu 9.10.

Micha Lenk (micha)
Changed in gnucash (Ubuntu):
status: New → Confirmed
Changed in gnucash:
status: Unknown → Fix Released
Revision history for this message
Saivann Carignan (oxmosys) wrote :

Can you test the patch, and if it fixes the problem, can you follow these steps to create a debdiff and request sponsorship from ubuntu developers?

https://wiki.ubuntu.com/SponsorshipProcess

Revision history for this message
Norbert (asterix52) wrote :

I tried the patch and it works.

Revision history for this message
Saivann Carignan (oxmosys) wrote :

Thanks! You forgot to subscribe ubuntu-universe-sponsors, I did it for you.

Norbert (asterix52)
Changed in gnucash (Ubuntu):
status: Confirmed → Fix Committed
Revision history for this message
Micha Lenk (micha) wrote :

From https://wiki.ubuntu.com/MOTU/Sponsorship/SponsorsQueue :
# The Status should be "Confirmed" for bugs that represent a new candidate revision (e.g. bugfix uploads, merges.) In other words, use Status "Confirmed" when you have uploaded a debdiff that requires attention from a sponsor.

Changed in gnucash (Ubuntu):
status: Fix Committed → Confirmed
Revision history for this message
Daniel Holbach (dholbach) wrote :

Please make use of https://wiki.ubuntu.com/UbuntuDevelopment/PatchTaggingGuidelines next time - I added the necessary information before uploading.

Revision history for this message
Daniel Holbach (dholbach) wrote :

You forgot to add (LP: #426685) to the entry in debian/changelog - else the bug would have been automatically closed.

Changed in gnucash (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Norbert (asterix52) wrote :

The new version work fine.

Thanks.

Changed in gnucash:
importance: Unknown → Critical
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.