Hello Paul, I'm the upstream author of AB-Transfers. Thank you for your detailed explanations.
A little background for the history functionality of abtransfers: I'm using the import and export functions from aqbanking to store all relevant data at a 'ctx-file' (aqbanking main file format). I'm using this to store all needed information, regardless of if it is an account, transfer, standing order (Dauerauftrag) or whatever else aqbanking supports. Another benefit of this is that I can use the same parser for the data, regardless of if it was send by the bank or read from a file. [...] > Looking at the “bad” `history.ctx` it’s size is 41 MB (42626560 Bytes) > and I think it contains strange characters due to umlauts I put into > the “Verwendungszweck” with the middle click as it’s not allowed (for > some reason) entering it with the keyboard. During development I had some issues with the German umlauts. Some banks supported it some don't. And also the aqbanking backend sometimes replaced some umlauts with spaces or not readable characters (but a crash did not happened). Therefore I decided to be on the save side and disabled the input of umlauts at abtransfers (didn't blocked/checked copy&paste input, my fault). Also a size of 41 MB is pretty big, either you using the program for a long time with a lot of transfers or something else is wrong. A normal transfer should occupy around 1.2 KB at the history (>34000 transfers needed to reach 41MB). > Also looking at `history.ctx` after the crash yesterday, the format > seems to be incorrect. The following is missing at the end of the file > compared to the file written today. > > int cycle="0" > int executionDay="0" > char type="transaction" > char subType="none" > char status="none" > char charge="Nobody" > char sequenceType="once" > } #transfer > } #transferList > } #accountInfo > } #accountInfoList > A few lines above this missing entries (or directly at the end) of your "bad" history.ctx file should be a line starting with "char purpose=". Could you remember which purpose (with umlauts) do you used? Which is the character that could not be written at the "bad" history.txt and maybe caused the crash? If I know this I could try to reproduce it here and maybe could fix it. Kind regards Patrick Wacker -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
