System -
Linux Mint 19.3
GnuCash 3.8-7 flatpak
GnuCash 2.6.19 conventional install via software manager
data files both flat file (XML) and MySQL database (MariaDB 10.3.22)

Both GnuCash versions 2.6.19 and 3.8-7 successfully access and manipulate
content of either flat file or database file.

The problem is than when I attempt to perform transaction download (Actions
> Online Actions > Get Transactions) version 3.8-7 fails immediately after
the "date range " prompt with the pop-up error message "Error on executing
job. Status: enqueued (1)" with close button.

The version 2.6.19 has no problem with transaction download using either
data file (flat or SQL).

The trace log reads -
* 16:37:16  CRIT <gwenhywfar> gui.c: 1818: Progress by id 00000002 not found
* 16:37:18  WARN <gnc.import.aqbanking> bal_accountinfo_cb: noted_bal ==
NULL.  Assuming 0
* 16:37:54  WARN <gnc.core-utils> Could not locate file AUTHORS
* 16:37:54  WARN <gnc.core-utils> Could not locate file DOCUMENTERS
* 16:37:54  WARN <gnc.core-utils> Could not locate file LICENSE
* 16:53:48  CRIT <gwenhywfar> gui.c: 1818: Progress by id 00000002 not found
* 16:53:50  WARN <gnc.import.aqbanking> bal_accountinfo_cb: noted_bal ==
NULL.  Assuming 0
* 16:54:15  CRIT <GLib> g_file_test: assertion 'filename != NULL' failed
* 16:54:57  CRIT <gwenhywfar> gui.c: 1818: Progress by id 00000002 not found
* 16:54:59  WARN <gnc.import.aqbanking> bal_accountinfo_cb: noted_bal ==
NULL.  Assuming 0

Any help would be greatly appreciated.

Regards,
Tom B.






--
Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html
_______________________________________________
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Reply via email to