Aqbanking lost the HBCI USE-flag with version 4.0.0. But other applications with HBCI enabled don't work anymore. Reproducible: Always Steps to Reproduce:
Can you be more specific. What kind of hbci? Chipcard-hbci? (obviously doesn't work without the chipcard useflag) Which application? How does "not work" appear to you? It should work with pin/tan or keyfile hbci, though I don't have that to test.
(In reply to comment #1) > Can you be more specific. What kind of hbci? Chipcard-hbci? (obviously doesn't > work without the chipcard useflag) Which application? How does "not work" > appear to you? > > It should work with pin/tan or keyfile hbci, though I don't have that to test. > I use keyfile hbci with Gnucash, but it didn't recognized my accounts. Then I tried qt3-wizard. I even coudn't create new accounts. Aqbanking complained that it couldn't load the aqhbci plugin. After emerging aqbanking with +libchipcard everything worked fine.
(In reply to comment #1) > Can you be more specific. What kind of hbci? I use hbci in the qbankmanager with an encrypted key file. After the upgrade to qbankmanager-0.9.51_beta with aqbanking-4.0.0 it still recognized my accounts. But every hbci operation failed. It didn't even ask me for the key of the encrypted key file. The message was something like "could not decode (or encode) the response", I think. I downgraded back to net-libs/aqbanking-2.3.3 where the hbci useflag still exists and everything works well. I tried aqbanking-4.0.0 both with enabled and disabled chipcard useflag. BTW. downgrading requires masking of these packages: =net-libs/aqbanking-4.0.0 >=sys-libs/gwenhywfar-3 >app-office/qbankmanager-0.9.5
gnucash 2.2.9 works for me with aqbanking 4.1.0 & gwenhywfar 3.9.2. You have to convert your old aqbanking config though using aqbanking-cli updateconf Note that the command has to be executed before any new aqbanking 4 client has been started. In your case you should restore the old $HOME/.banking folder and delete an existing $HOME/.aqbanking folder. It would have been nice to get some kind of warning form the ebuild though!
(In reply to comment #4) > You have to convert your old aqbanking config though using > aqbanking-cli updateconf I did this now. I have still the same problem. I'll downgrade back again.
It works with: [ebuild UD] sys-libs/gwenhywfar-2.6.2 [3.8.2] USE="ncurses%* ssl -debug -doc" [ebuild UD] sys-libs/libchipcard-3.0.4 [4.2.8] USE="ssl%* usb%* -debug% -doc" [ebuild UD] net-libs/aqbanking-2.3.3 [4.0.0] USE="chipcard geldkarte%* hbci%* kde ofx python qt3 -debug -dtaus% (-yellownet)"
Try, [ebuild R ] net-libs/aqbanking-4.2.0 USE="qt4 -chipcard -debug -ofx" 0 kB [ebuild R ] app-office/qbankmanager-0.9.52_beta-r1 USE="-debug" 0 kB
Using aqbanking-4.2.0 with gnucash-2.2.9-r1 (HBCI-PIN/TAN) leads to repeated questions for my PIN during one procedure (retrieving transactions). qbankmanager-0.9.52_beta-r1 does not show this behaviour. AFAIK gnucash-2.2 upstream has no official support for >=aqbanking-3*, so i wonder why aqbanking-2* has vanished from the tree at all.
(In reply to comment #8) > Using aqbanking-4.2.0 with gnucash-2.2.9-r1 (HBCI-PIN/TAN) leads to repeated For me, the earlier versions have not really worked with Deutsche Postbank. My last test with the official version aqbanking-4.0.0 a month ago was successful and so I then can switch to them.
