[GNC] Can't enter the number from statement
It seems I'm unable to enter the numbers as reported on the statement. Here is the statement: https://imgur.com/GA250qz When I try to enter the split into Gnucash, it always gives me 121.64 in the trading:AUD and 0.01 orphan (?!). I changed manually the account to trading:AUD so that the balances match. Why won't it let me enter 121.65 into the split? -- 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.
Re: [GNC] Can't enter the number from statement
of course, forgot to link the GC transaction: https://imgur.com/ANoGpG0 -- 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.
Re: [GNC] Can't enter the number from statement
Actually, that didn't work so I have to leave the 0.01 at Imbalance-AUD. This type of transaction is quite difficult to create and enter as a scheduled transaction. I have to do it manually every time (fortunately not that often but still). -- 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.
Re: [GNC] Can't enter the number from statement
> On Oct 24, 2018, at 4:44 AM, cicko wrote: > > Actually, that didn't work so I have to leave the 0.01 at Imbalance-AUD. > > This type of transaction is quite difficult to create and enter as a > scheduled transaction. I have to do it manually every time (fortunately not > that often but still). It’s because you’re trying to force the 1.4011 AUD/USD exchange rate. 86.82 * 1.4011 = 121.6478, which GnuCash rounds up to 121.65. Enter the amounts and let GnuCash calculate the exchange rate. Regards, John Ralls ___ 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.
Re: [GNC] AqBanking help for Citi CC
Hello Jim, This is great news. I had the Citibank Credit Card download working for years, but it broke early this year. I've attempted to setup GNUCash based on the above, but continue to struggle. I receive the following error during the initial bank connection: *Error on gnutls_bye: -24 (Decryption has failed.)* After looking at your OFX settings above, I used the following during the GNUCash setup: - Create User - Select OFX - Bank Name: Citi Credit Card - Broker Id: - FID: 24909 - ORG: Citigroup - Server URL: https://www.accountonline.com/cards/svc/CitiOfxManager.do - User Name: myusername - User Id: myusername<--- I added a space per your comments - Client UID: - Emulated App: Quicken 2013 - Application ID: QWIN - Application Version: 2400 - Header Version: 103 After accepting the certificate , the log window has that error. If I retrieve accounts after this, I get the following: 09:12:27 Sending request... 09:12:27 Using GnuTLS default ciphers. 09:12:28 TLS: SSL-Ciphers negotiated: TLS1.2:ECDHE-RSA-AES-256-GCM:AEAD 09:12:28 Signer not found 09:12:28 Certificate is not trusted 09:13:31 Waiting for response... 09:13:31 No message received 09:13:31 Network error while waiting for response 09:13:31 Operation finished, you can now close this window. I have a long password, but no special characters in it. I'm on windows and need to read up a bit more on how to get the OFX.log. Setting the ENV variable and starting GNUCash from the command session didn't seem to produce one. I appreciate the guidance and the time. I'm sure a lot of people use Citi Cards and your debugging can benefit a lot of people. Can you provide any differences in your GNUCash config settings that what I have above? I've tried a few variations but to no avail. Thank you! Michael On Tue, Oct 23, 2018 at 11:12 PM Jim Maki via gnucash-user < gnucash-user@gnucash.org> wrote: > I just successfully set up GnuCash to download Citi credit card data > using AqBanking - for now all you have to do is add a space to the end > of your userid (assuming everything else is correct).The issue seems to > be with Citi ... > > When it consistently failed with code 403, I turned on OFX logging > (export AQOFX_LOG_COMM=1), snagged the OFX request (from /tmp/ofx.log), > formatted it to make it more readable, and created a bash script using > curl to make the OFX request. Paradoxically it worked while the > equivalent un-beautified GnuCash request failed. > > After little debugging, the key lines in the GnuCash ofx.log were: > > == OFX == > ... > ... myuserid > mypassword > ... > == OFX == > > The above will work if you add a space either at the end of the > "...myuserid" line, or before "" in the next line. At > the GnuCash user interface level that involves adding a trailing space > to the AqBanking userid for Citi. > > For reference, below is the OFX template file I use to feed my > curl-based script. Eventually GnuCash makes an equivalent request. > (Again, eliminate the leading spaces before "" and it, too > fails.) > > == OFX == > OFXHEADER:100 > DATA:OFXSGML > VERSION:103 > SECURITY:NONE > ENCODING:USASCII > CHARSET:1252 > COMPRESSION:NONE > OLDFILEUID:NONE > NEWFILEUID:$OFX_DATETIME > > > > > $OFX_DATETIME > $OFX_USER > $OFX_PW > ENG > > $OFX_ORG > $OFX_FID > > QWIN > 2400 > > > > > $OFX_DATETIME > 1 > > > $OFX_ACCOUNT > > > $OFX_STARTDATE > $OFX_ENDDATE > Y > > > > > > == OFX == > > If GnuCash did prettified SGML it would avoid this problem with Citi's > parsing. > >Jim > > ___ > 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. ___ 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.
Re: [GNC] GNUCash fails to start on Windows 10 after windows update
Hi, Anyone else with the same issue? Any ideas to debug this? Thanks. Cristian On Sunday, October 21, 2018, 1:18:24 PM GMT+2, crysty sandu via gnucash-user wrote: The file is empty if I run it normally. If I run the program with --debug --extra I got:* 13:12:24 INFO [main] System locale returned (null) * 13:12:24 INFO [main] Effective locale set to C. * 13:12:36 INFO [gnc_load_app_icons] The icon theme search path has 10 elements. * 13:12:36 INFO [gnc_load_app_icons] Path 0: C:\Users\username\AppData\Local\icons * 13:12:36 INFO [gnc_load_app_icons] Path 1: C:\Users\username\.icons * 13:12:36 INFO [gnc_load_app_icons] Path 2: C:\Program Files (x86)\gnucash/share\icons * 13:12:36 INFO [gnc_load_app_icons] Path 3: /usr/local/share/icons * 13:12:36 INFO [gnc_load_app_icons] Path 4: /usr/share/icons * 13:12:36 INFO [gnc_load_app_icons] Path 5: C:\Program Files (x86)\gnucash/share\pixmaps * 13:12:36 INFO [gnc_load_app_icons] Path 6: /usr/local/share/pixmaps * 13:12:36 INFO [gnc_load_app_icons] Path 7: /usr/share/pixmaps * 13:12:36 INFO [gnc_load_app_icons] Path 8: C:\Program Files (x86)\gnucash/share\gnucash\icons * 13:12:36 INFO [gnc_load_app_icons] Path 9: C:\Program Files (x86)\gnucash/share\icons * 13:12:38 INFO [gnc_gsettings_register_cb] schema: general, key: retain-days, settings_ptr: 059d4488, handler_id: 16 * 13:12:38 INFO [gnc_gsettings_register_cb] schema: general, key: retain-type-never, settings_ptr: 059d4488, handler_id: 17 * 13:12:38 INFO [gnc_gsettings_register_cb] schema: general, key: retain-type-days, settings_ptr: 059d4488, handler_id: 18 * 13:12:38 INFO [gnc_gsettings_register_cb] schema: general, key: retain-type-forever, settings_ptr: 059d4488, handler_id: 19 * 13:12:38 INFO [gnc_gsettings_register_cb] schema: general, key: file-compression, settings_ptr: 059d4488, handler_id: 20 * 13:12:40 INFO [gnc_gsettings_register_cb] schema: general, key: account-separator, settings_ptr: 059d4488, handler_id: 68 * 13:12:40 INFO [gnc_gsettings_register_cb] schema: general, key: reversed-accounts-none, settings_ptr: 059d4488, handler_id: 69 * 13:12:40 INFO [gnc_gsettings_register_cb] schema: general, key: reversed-accounts-credit, settings_ptr: 059d4488, handler_id: 70 * 13:12:40 INFO [gnc_gsettings_register_cb] schema: general, key: reversed-accounts-incomeexpense, settings_ptr: 059d4488, handler_id: 71 * 13:12:40 INFO [gnc_gsettings_register_cb] schema: general, key: currency-choice-locale, settings_ptr: 059d4488, handler_id: 72 * 13:12:40 INFO [gnc_gsettings_register_cb] schema: general, key: currency-choice-other, settings_ptr: 059d4488, handler_id: 73 * 13:12:40 INFO [gnc_gsettings_register_cb] schema: general, key: currency-other, settings_ptr: 059d4488, handler_id: 74 * 13:12:40 INFO [gnc_gsettings_register_cb] schema: general.report, key: currency-choice-locale, settings_ptr: 09cb52a0, handler_id: 75 * 13:12:40 INFO [gnc_gsettings_register_cb] schema: general.report, key: currency-choice-other, settings_ptr: 09cb52a0, handler_id: 76 * 13:12:40 INFO [gnc_gsettings_register_cb] schema: general.report, key: currency-other, settings_ptr: 09cb52a0, handler_id: 77 * 13:12:40 INFO [gnc_gsettings_register_cb] schema: general, key: auto-decimal-point, settings_ptr: 059d4488, handler_id: 78 * 13:12:40 INFO [gnc_gsettings_register_cb] schema: general, key: auto-decimal-places, settings_ptr: 059d4488, handler_id: 79 * 13:12:40 INFO [gnc_gsettings_register_cb] schema: general, key: date-format, settings_ptr: 059d4488, handler_id: 80 * 13:12:40 INFO [gnc_gsettings_register_cb] schema: general, key: date-completion-thisyear, settings_ptr: 059d4488, handler_id: 81 * 13:12:40 INFO [gnc_gsettings_register_cb] schema: general, key: date-completion-sliding, settings_ptr: 059d4488, handler_id: 82 * 13:12:40 INFO [gnc_gsettings_register_cb] schema: general, key: date-backmonths, settings_ptr: 059d4488, handler_id: 83 * 13:12:40 INFO [gnc_gsettings_register_cb] schema: general, key: (NULL), settings_ptr: 059d4488, handler_id: 84 * 13:12:40 INFO [gnc_gsettings_register_cb] schema: general, key: tab-close-buttons, settings_ptr: 059d4488, handler_id: 85 * 13:12:40 INFO [gnc_gsettings_register_cb] schema: general, key: tab-width, settings_ptr: 059d4488, handler_id: 86 * 13:12:40 INFO [gnc_hook_lookup] no hook lists * 13:12:40 INFO [gnc_gsettings_register_cb] schema: general, key: show-account-color-tabs, settings_ptr: 059d4488, handler_id: 90 * 13:12:40 INFO [gnc_gsettings_register_cb] schema: general, key: tab-position-top, settings_ptr: 059d4488, handler_id: 712 * 13:12:40 INFO [gnc_gsettings_register_cb] schema: general, key: tab-position-bottom, settings_ptr: 059d4488, handler_id: 713 * 13:12:40 INFO [gnc_gsettings_register_cb] schema: general, key: tab-position-left, settings_ptr: 059d4488, handler_id: 714 * 13:12:40 INFO [gnc_gsettings_register_cb] schema: general, key: tab-posi
[GNC] Gnucash 3.3 crash after upgrading from Ubuntu 18.04 to 18.10
Just upgraded my Ubuntu 18.04 to 18.10. This upgraded GC from 2.6.19 (at
least I think it was 19) to 3.3 and now GC crashes immediately on startup.
Starting in a terminal gives result below. There is nothing in the trace
file. On another machine with a fresh install of 18.10 GC 3.3 runs fine so
I guess it is to with updated file locations or something.
Colin
$ gnucash
Backtrace:
In ice-9/boot-9.scm:
2994:20 19 (_)
2312:4 18 (save-module-excursion _)
3014:26 17 (_)
In unknown file:
16 (primitive-load-path "gnucash/utilities" #)
In utilities.scm:
28:0 15 (_)
In ice-9/boot-9.scm:
3377:20 14 (process-use-modules _)
222:17 13 (map1 (((gnucash core-utils
3378:31 12 (_ ((gnucash core-utils)))
2800:17 11 (resolve-interface (gnucash core-utils) #:select _ # _ # …)
In ice-9/threads.scm:
390:8 10 (_ _)
In ice-9/boot-9.scm:
2726:13 9 (_)
In ice-9/threads.scm:
390:8 8 (_ _)
In ice-9/boot-9.scm:
2994:20 7 (_)
2312:4 6 (save-module-excursion _)
3014:26 5 (_)
In unknown file:
4 (primitive-load-path "gnucash/core-utils" #)
In core-utils.scm:
40:0 3 (_)
In ice-9/boot-9.scm:
2071:24 2 (call-with-deferred-observers #)
260:13 1 (for-each # …)
In unknown file:
0 (scm-error misc-error #f "~A ~S" ("Undefined variab…" …) …)
ERROR: In procedure scm-error:
Undefined variable: gnc-build-userdata-path
___
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.
Re: [GNC] Gnucash 3.3 crash after upgrading from Ubuntu 18.04 to 18.10
Further to this I see I have two files ice-9/boot-9.scm
/usr/share/guile/2.2/ice-9/boot-9.scm
/usr/share/guile/2.0/ice-9/boot-9.scm
Could it be picking up the wrong one, or is that a red herring?
Colin
On Wed, 24 Oct 2018 at 15:57, Colin Law wrote:
> Just upgraded my Ubuntu 18.04 to 18.10. This upgraded GC from 2.6.19 (at
> least I think it was 19) to 3.3 and now GC crashes immediately on startup.
> Starting in a terminal gives result below. There is nothing in the trace
> file. On another machine with a fresh install of 18.10 GC 3.3 runs fine so
> I guess it is to with updated file locations or something.
>
> Colin
>
> $ gnucash
> Backtrace:
> In ice-9/boot-9.scm:
> 2994:20 19 (_)
>2312:4 18 (save-module-excursion _)
> 3014:26 17 (_)
> In unknown file:
> 16 (primitive-load-path "gnucash/utilities" #)
> In utilities.scm:
> 28:0 15 (_)
> In ice-9/boot-9.scm:
> 3377:20 14 (process-use-modules _)
>222:17 13 (map1 (((gnucash core-utils
> 3378:31 12 (_ ((gnucash core-utils)))
> 2800:17 11 (resolve-interface (gnucash core-utils) #:select _ # _ # …)
> In ice-9/threads.scm:
> 390:8 10 (_ _)
> In ice-9/boot-9.scm:
> 2726:13 9 (_)
> In ice-9/threads.scm:
> 390:8 8 (_ _)
> In ice-9/boot-9.scm:
> 2994:20 7 (_)
>2312:4 6 (save-module-excursion _)
> 3014:26 5 (_)
> In unknown file:
>4 (primitive-load-path "gnucash/core-utils" #)
> In core-utils.scm:
> 40:0 3 (_)
> In ice-9/boot-9.scm:
> 2071:24 2 (call-with-deferred-observers #)
>260:13 1 (for-each # …)
> In unknown file:
>0 (scm-error misc-error #f "~A ~S" ("Undefined variab…" …) …)
>
> ERROR: In procedure scm-error:
> Undefined variable: gnc-build-userdata-path
>
>
___
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.
Re: [GNC] Gnucash 3.3 crash after upgrading from Ubuntu 18.04 to 18.10
Yes, that was the issue (two versions of boot-9.scm). Having checked
dependencies and so on, including doing a dry run remove to check it wasn't
going to remove anything critical, I uninstalled guile-2.0-libs and now it
runs ok.
So is this a packaging bug?
Colin
On Wed, 24 Oct 2018 at 16:39, Colin Law wrote:
> Further to this I see I have two files ice-9/boot-9.scm
> /usr/share/guile/2.2/ice-9/boot-9.scm
> /usr/share/guile/2.0/ice-9/boot-9.scm
> Could it be picking up the wrong one, or is that a red herring?
>
> Colin
>
> On Wed, 24 Oct 2018 at 15:57, Colin Law wrote:
>
>> Just upgraded my Ubuntu 18.04 to 18.10. This upgraded GC from 2.6.19 (at
>> least I think it was 19) to 3.3 and now GC crashes immediately on startup.
>> Starting in a terminal gives result below. There is nothing in the trace
>> file. On another machine with a fresh install of 18.10 GC 3.3 runs fine so
>> I guess it is to with updated file locations or something.
>>
>> Colin
>>
>> $ gnucash
>> Backtrace:
>> In ice-9/boot-9.scm:
>> 2994:20 19 (_)
>>2312:4 18 (save-module-excursion _)
>> 3014:26 17 (_)
>> In unknown file:
>> 16 (primitive-load-path "gnucash/utilities" #)
>> In utilities.scm:
>> 28:0 15 (_)
>> In ice-9/boot-9.scm:
>> 3377:20 14 (process-use-modules _)
>>222:17 13 (map1 (((gnucash core-utils
>> 3378:31 12 (_ ((gnucash core-utils)))
>> 2800:17 11 (resolve-interface (gnucash core-utils) #:select _ # _ # …)
>> In ice-9/threads.scm:
>> 390:8 10 (_ _)
>> In ice-9/boot-9.scm:
>> 2726:13 9 (_)
>> In ice-9/threads.scm:
>> 390:8 8 (_ _)
>> In ice-9/boot-9.scm:
>> 2994:20 7 (_)
>>2312:4 6 (save-module-excursion _)
>> 3014:26 5 (_)
>> In unknown file:
>>4 (primitive-load-path "gnucash/core-utils" #)
>> In core-utils.scm:
>> 40:0 3 (_)
>> In ice-9/boot-9.scm:
>> 2071:24 2 (call-with-deferred-observers #)
>>260:13 1 (for-each # …)
>> In unknown file:
>>0 (scm-error misc-error #f "~A ~S" ("Undefined variab…" …) …)
>>
>> ERROR: In procedure scm-error:
>> Undefined variable: gnc-build-userdata-path
>>
>>
___
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.
Re: [GNC] AqBanking help for Citi CC
My experience this week suggests that your Application Version setting is at least sufficient to cause your problem. Direct connection from gnucash to citicards stopped working for me earlier this year, and any time I attempted to make the connection, Citi decided someone was trying break into my account and a couple hours later would require me to reset my password (providing erroneous information about what constituted a valid password, argh). Since Citi would never tell me why they thought someone was trying to break into my account, I gave up on them after a while. But when Chase stopped responding to requests for transaction data from gnucash this week, I figured out that something else was amiss. Quicken has always disabled data connections after 3-3.5 years from any version release. They’ll give you an informative message if you’re using Quicken, but either aqbanking or gnucash haven’t handled such messages. I had been running with AppVer=2500. I changed that to 2700 last night and both Chase and Citicards resumed working from within gnucash. I believe Quicken 2019 is AppVer=2800, but I’m not sure. -- Dave Reiser dbrei...@icloud.com > On Oct 24, 2018, at 10:17 AM, Fross, Michael wrote: > > Hello Jim, > > This is great news. I had the Citibank Credit Card download working for > years, but it broke early this year. I've attempted to setup GNUCash based > on the above, but continue to struggle. I receive the following error > during the initial bank connection: > > *Error on gnutls_bye: -24 (Decryption has failed.)* > > After looking at your OFX settings above, I used the following during the > GNUCash setup: > > - Create User - Select OFX > - Bank Name: Citi Credit Card > - Broker Id: > - FID: 24909 > - ORG: Citigroup > - Server URL: https://www.accountonline.com/cards/svc/CitiOfxManager.do > - User Name: myusername > - User Id: myusername<--- I added a space per your comments > - Client UID: > - Emulated App: Quicken 2013 > - Application ID: QWIN > - Application Version: 2400 > - Header Version: 103 > > After accepting the certificate , the log window has that error. If I > retrieve accounts after this, I get the following: > > 09:12:27 Sending request... > 09:12:27 Using GnuTLS default ciphers. > 09:12:28 TLS: SSL-Ciphers negotiated: TLS1.2:ECDHE-RSA-AES-256-GCM:AEAD > 09:12:28 Signer not found > 09:12:28 Certificate is not trusted > 09:13:31 Waiting for response... > 09:13:31 No message received > 09:13:31 Network error while waiting for response > 09:13:31 Operation finished, you can now close this window. > > I have a long password, but no special characters in it. I'm on windows > and need to read up a bit more on how to get the OFX.log. Setting the ENV > variable and starting GNUCash from the command session didn't seem to > produce one. > > I appreciate the guidance and the time. I'm sure a lot of people use Citi > Cards and your debugging can benefit a lot of people. Can you provide any > differences in your GNUCash config settings that what I have above? I've > tried a few variations but to no avail. > > Thank you! > > Michael > > > On Tue, Oct 23, 2018 at 11:12 PM Jim Maki via gnucash-user < > gnucash-user@gnucash.org> wrote: > >> I just successfully set up GnuCash to download Citi credit card data >> using AqBanking - for now all you have to do is add a space to the end >> of your userid (assuming everything else is correct).The issue seems to >> be with Citi ... >> >> When it consistently failed with code 403, I turned on OFX logging >> (export AQOFX_LOG_COMM=1), snagged the OFX request (from /tmp/ofx.log), >> formatted it to make it more readable, and created a bash script using >> curl to make the OFX request. Paradoxically it worked while the >> equivalent un-beautified GnuCash request failed. >> >> After little debugging, the key lines in the GnuCash ofx.log were: >> >> == OFX == >> ... >> ... myuserid >> mypassword >> ... >> == OFX == >> >> The above will work if you add a space either at the end of the >> "...myuserid" line, or before "" in the next line. At >> the GnuCash user interface level that involves adding a trailing space >> to the AqBanking userid for Citi. >> >> For reference, below is the OFX template file I use to feed my >> curl-based script. Eventually GnuCash makes an equivalent request. >> (Again, eliminate the leading spaces before "" and it, too >> fails.) >> >> == OFX == >> OFXHEADER:100 >> DATA:OFXSGML >> VERSION:103 >> SECURITY:NONE >> ENCODING:USASCII >> CHARSET:1252 >> COMPRESSION:NONE >> OLDFILEUID:NONE >> NEWFILEUID:$OFX_DATETIME >> >> >> >> >> $OFX_DATETIME >> $OFX_USER >> $OFX_PW >> ENG >> >> $OFX_ORG >> $OFX_FID >> >> QWIN >> 2400 >> >> >> >> >> $OFX_DATETIME >> 1 >> >> >> $OFX_ACCOUNT >> >> >> $OFX_STARTDATE >> $OFX_ENDDATE >> Y >> >> >> >> >> >> ==
Re: [GNC] AqBanking help for Citi CC
< Can you provide any differences in your GnuCash config settings that what I have above? Here goes my settings: AqBanking Setup ==> User Settings > User Name - "YOURUSERID" > User Id - "YOURUSERID " (trailing space) > Client UID - not specified ==> Bank Settings > Bank Name - "Citi Credit Card" > Broker Id - "Citigroup" > FID - "24909" > ORG - "Citigroup" > Server URL - "https://www.accountonline.com/cards/svc/CitiOfxManager.do"; ==> Application Settings > Application ID - "QWIN" > Application Version - "2400" > Header Version - "103" > No Special Settings ==> Account Info > Account Number - "YOUR CC NUMBER" > Account Name - "Citigroup" > IBAN - not specified > Owner Name - not specified > Currency - "US Dollar (USD)" > Account Type - "Credit Card Account" ==> Bank Info > Country - "United States of America (US)" > Bank Code - "www.accountonline.com" > Bank Name - "www.accountonline.com" > SWIFT BIC - not specified > Selected User - the user you defined above > After accepting the certificate , the log window has that error. If I retrieve accounts after this, I get the following: > 09:12:27 Sending request... > 09:12:27 Using GnuTLS default ciphers. > 09:12:28 TLS: SSL-Ciphers negotiated: TLS1.2:ECDHE-RSA-AES-256-GCM:AEAD > 09:12:28 Signer not found > 09:12:28 Certificate is not trusted > 09:13:31 Waiting for response... > 09:13:31 No message received > 09:13:31 Network error while waiting for response > 09:13:31 Operation finished, you can now close this window. Little help, but you'll find the "Signer not found" and "Certificate is not trusted" in: https://github.com/cstim/gwenhywfar/blob/master/src/sio/syncio_tls.c So those errors relate to the certificate presented by the site you used. First make sure you're running a current version of GnuCash/AqBanking and update your settings (especially check the URL). The certificate I get validates OK: * Server certificate: * subject: businessCategory=Private Organization; jurisdictionC=US; jurisdictionST=Delaware; serialNumber=2154254; C=US; ST=New York; L=New York; O=Citigroup Inc.; OU=Web Hosting Group; CN=www.accountonline.com * start date: Aug 15 00:00:00 2018 GMT * expire date: Jan 2 12:00:00 2020 GMT * subjectAltName: host "www.accountonline.com" matched cert's "www.accountonline.com" * issuer: C=US; O=DigiCert Inc; OU=www.digicert.com; CN=DigiCert SHA2 Extended Validation Server CA * SSL certificate verify ok. Jim ___ 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.
[GNC] Settings problem after update to 3.3 on Ubuntu - missing keys
I have updated a system from Ubuntu 18.04 to 18.10 and gnucash has been automatically updated from version 2.6.19 to 3.3 from the Ubuntu repository. I noticed that I was not getting the alternating colours in the registers and when I went to Preferences > Register I can see that 'Use GnuCash built in color theme' is not checked. If I check it, exit preferences and then go back in again I can see that the preference has not been saved. Some options do get saved however, Auto-raise lists for example. On looking in gnucash.trace I see a lot of errors like * 21:33:32 CRIT [gnc_gsettings_get_int()] Invalid key prefs-version for schema general * 21:33:32 CRIT [gnc_gsettings_set_bool()] Invalid key use-gnucash-color-theme for schema general.register * 21:33:32 CRIT [gnc_gsettings_set_int()] Invalid key prefs-version for schema general * 21:33:46 CRIT [gnc_gsettings_get_bool()] Invalid key grid-lines-horizontal for schema general and if I run dconf-editor I can see that those keys are missing. Would I be right in surmising that these are new keys that were not present in 2.6.19? Is this a bug in gnucash in that it has not created those keys automatically, or should the act of updating the package have added the new keys, or something else? What is the best way to recover from this? I do have another machine with a new install of 3.3 so I could use dconf dump /org/gnucash on that machine and then dconf load to load it onto the failing one. Colin ___ 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.
Re: [GNC] Gnucash 3.3 crash after upgrading from Ubuntu 18.04 to 18.10
Good detective work.
Guile is supposed to be able to handle having multiple versions installed and
to link the right libraries, but I suppose if you had guile-2.0-compiled files
in a guile cache and guile-2.2-compiled ones installed by the .deb it might get
confused. Was this a clean install of Ubuntu or were you upgrading and using a
GnuCash you’d built yourself before upgrading?
Regards,
John Ralls
> On Oct 24, 2018, at 9:40 AM, Colin Law wrote:
>
> Yes, that was the issue (two versions of boot-9.scm). Having checked
> dependencies and so on, including doing a dry run remove to check it wasn't
> going to remove anything critical, I uninstalled guile-2.0-libs and now it
> runs ok.
>
> So is this a packaging bug?
>
> Colin
>
> On Wed, 24 Oct 2018 at 16:39, Colin Law wrote:
>
>> Further to this I see I have two files ice-9/boot-9.scm
>> /usr/share/guile/2.2/ice-9/boot-9.scm
>> /usr/share/guile/2.0/ice-9/boot-9.scm
>> Could it be picking up the wrong one, or is that a red herring?
>>
>> Colin
>>
>> On Wed, 24 Oct 2018 at 15:57, Colin Law wrote:
>>
>>> Just upgraded my Ubuntu 18.04 to 18.10. This upgraded GC from 2.6.19 (at
>>> least I think it was 19) to 3.3 and now GC crashes immediately on startup.
>>> Starting in a terminal gives result below. There is nothing in the trace
>>> file. On another machine with a fresh install of 18.10 GC 3.3 runs fine so
>>> I guess it is to with updated file locations or something.
>>>
>>> Colin
>>>
>>> $ gnucash
>>> Backtrace:
>>> In ice-9/boot-9.scm:
>>> 2994:20 19 (_)
>>> 2312:4 18 (save-module-excursion _)
>>> 3014:26 17 (_)
>>> In unknown file:
>>> 16 (primitive-load-path "gnucash/utilities" #)
>>> In utilities.scm:
>>> 28:0 15 (_)
>>> In ice-9/boot-9.scm:
>>> 3377:20 14 (process-use-modules _)
>>> 222:17 13 (map1 (((gnucash core-utils
>>> 3378:31 12 (_ ((gnucash core-utils)))
>>> 2800:17 11 (resolve-interface (gnucash core-utils) #:select _ # _ # …)
>>> In ice-9/threads.scm:
>>>390:8 10 (_ _)
>>> In ice-9/boot-9.scm:
>>> 2726:13 9 (_)
>>> In ice-9/threads.scm:
>>>390:8 8 (_ _)
>>> In ice-9/boot-9.scm:
>>> 2994:20 7 (_)
>>> 2312:4 6 (save-module-excursion _)
>>> 3014:26 5 (_)
>>> In unknown file:
>>> 4 (primitive-load-path "gnucash/core-utils" #)
>>> In core-utils.scm:
>>> 40:0 3 (_)
>>> In ice-9/boot-9.scm:
>>> 2071:24 2 (call-with-deferred-observers #)
>>> 260:13 1 (for-each # …)
>>> In unknown file:
>>> 0 (scm-error misc-error #f "~A ~S" ("Undefined variab…" …) …)
>>>
>>> ERROR: In procedure scm-error:
>>> Undefined variable: gnc-build-userdata-path
>>>
>>>
> ___
> 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.
___
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.
Re: [GNC] AqBanking help for Citi CC
> I changed that to 2700 last night and both Chase and Citicards resumed working from within gnucash. I believe Quicken 2019 is AppVer=2800, but I’m not sure. Can you list your sanitized configuration parameters as I have? I'd like to compare them. And can you get your working (sanitized) ofx.log file? Does it differ from mine which has followed by on the first byte of the next line: /== OFX == />/... />/... myuserid />/mypassword />/... />/== OFX == / Here's why I'm so curious. My first test was to try Application Version 2700 and 2900: both worked with my blank-padded userid and both failed with my non-blank-padded userid. I suspect Liang's would also. But your's clearly wouldn't. So how could yours possibly work? One way is that somehow your OFXSGML interjects a tag between and . So I fired up my trusty curl-based script doing just that by sticking the "" tag between: ... 20181024221016.000MYUSERIDWITHOUTBLANK ENG MYPASSWORD ... And it worked without blank padding the userid (the results you found). So if your version of GnuCash based on your exact configuration inputs creates an OFXSGML file (ofx.log) different from mine (and Liang's) in just the right way, yours could work. Feedback would be appreciated. I'd like to see the magic that makes yours work. I was running 2.6.19 at first but am running 3.3 now. Jim ___ 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.
