After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 661109 - Do not close aqbanking log window in case of errors
Do not close aqbanking log window in case of errors
Status: RESOLVED FIXED
Product: GnuCash
Classification: Other
Component: Import - AqBanking
2.2.9
Other Linux
: Normal normal
: ---
Assigned To: Christian Stimming
Christian Stimming
Depends on:
Blocks:
 
 
Reported: 2011-10-06 18:06 UTC by Ben Bucksch
Modified: 2018-06-29 23:01 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Ben Bucksch 2011-10-06 18:06:20 UTC
Reproduction:
1. set up aqbanking with HBCI
2. Fetch account statements
3. Check checkbox in log window to close log window at the end
4. Break setup (no network, server broken, break aqbanking setup etc.)
5. Fetch account statements

Actual result:
Msg: "no new transactions", GnuCash assumes that there's nothing new. In reality, the communication failed and there are new transactions.

Expected result:
GnuCash differentiates between a successful and a failed aqbanking request, and if there is an error:
1. the log window stays open
2. no message that there are "no new transactions"
3. The "last fetch" date (start time for the next request) is
   not changed to today, but stays on the old date.

What makes this worse is that I don't see an obvious way to get the log window back (it closes in a split-second and the checkbox is *in* the window), so there's no way for me to get to the error message from aqbanking. Makes fixing the problem kind-of hard.

Story:
I moved to a new machine. In the process, I re-installed the OS to change to 64bit, reorganized file systems, and reinstalled gnucash and aqbanking. Then I try to fetch my statements and ran into the above problem. Finally I used aqbanking-cli (which is more than most users would be able to do), and found that aqbanking doesn't store symlinks, but resolves them and stores the absolute path. That's rather stupid, because the whole purpose of the symlink is to keep the paths independent from physical filesystem organization. My home dir is symlinked and I moved it.
Before I used aqbanking-cli and saw the error message, I suspected as cause and tried to fix:
* gnucash and aqbanking installation, including HBCI
* change to 64bit
* dotfiles wreckup
* setup (data) nulled by GnuCash due to any of these things
* several other things

In other words, without error message, you are in the dark and waste time. Please make sure to give proper errors. Do whatever is necessary to give them.
Comment 1 Christian Stimming 2011-10-06 20:03:49 UTC
This problem has been fixed in the development version. The fix will be available in the next major software release. (The log window can be opened and closed from the "Online Actions" menu in the SVN trunk versions.) Thank you for your bug report.
Comment 2 Ben Bucksch 2011-10-06 20:16:08 UTC
Thanks for the fast response, but:

> The log window can be opened and closed from the "Online Actions" menu
> in the SVN trunk versions.

This doesn't fix the bug. Please see the "Expected result".
Comment 3 Christian Stimming 2011-10-06 20:29:40 UTC
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.
Comment 4 John Ralls 2018-06-29 23:01:41 UTC
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=661109. Please update any external references or bookmarks.