[Aqbanking-devel] Gnucash crashes on Online Actions (Gett ransactions and Issue Transcation) with aqhbci

[Christian Stimming]

Quoting Oliver König <oliver at windfinder.com>:
> I have got OpenSuse 10.2, gnucash-2.0.2-29, aqbanking-2.2.3-21. I do online
> banking with Gnucash and aqbanking. My bank is Deutsche Bank Hamburg. The
> keyfile for online banking is on my USB-stick at /media/disk/ with:
>
> -r--r----- 1 myself root  1971 2007-04-04 15:05 keyfile.txt
>
> This configuration has worked fine for several month. A few days ago GnuCash
> began to crash

You'll probably guess this yourself, but: When you say "a few days ago  
xy started to happen", you should better think hard whether you  
changed any little thing in your system right beforehand, and include  
this information here. Updating aqbanking or gnucash? Changing the USB  
stick permissions? Turning on the write protection on the USB stick?

> 3:2007/04/05 11-28-07:gwen(14906):ct_file.c:  408:
> open(/media/disk/kgq659.txt): Permission denied
> 3:2007/04/05 11-28-07:gwen(14906):ct_file.c: 1361: Error writing file (-1)
> 3:2007/04/05 11-28-07:aqhbci(14906):jobqueue.c:  426: Could not   
> encode message
> (-1)
> 3:2007/04/05 11-28-07:aqhbci(14906):outbox.c: 1368: Error performing queue
> (-1)
> 3:2007/04/05 11-28-07:gwen(14906):ct_file.c:  408:
> open(/media/disk/kgq659.txt): Permission denied
>
> The application is started with the user "myself".

Aqbanking does not need write access to the keyfile, but it needs  
write access to the whole directory because the changed keyfile is  
first written to a new file (hence the filename "kgq659.txt" instead  
of "keyfile.txt" above) which is then renamed to the previous  
filename. This is done because if there were a crash in between, then  
at least your old keyfile would still be there. So you have to give  
the user "myself" write access to the directory.

> This is what bug buddy said:
> Distribution: openSUSE 10.2 (i586)
> ..
> 0xb7f8f410 in ?? ()
> #0  0xb7f8f410 in ?? ()
> #1  0xbfa8a078 in ?? ()
> #2  0x00000000 in ?? ()

Such a bug-buddy report is unfortunately completely useless for us.  
You need to install the package "gnucash-debuginfo" (might require  
adding another package source), then reproduce this bug, and then you  
will get actually useful back traces. In general, those should then be  
reported to bugzilla, not to the mailing lists. Thanks a lot.

Christian