[GNC] Proper way to record receiving a commission check
What is the "GnuCash" way of properly recording what will be a monthly commission check that I will be receiving. Rick ___ 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] 503 Error on install
I'm trying to download (install) the flatpack on Linux Mint and receiving an error: While pulling app/org.gnucash.GnuCash/x86_64/stable from remote flathub: Server returned status 503: Service Unavailable. Rick ___ 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] Error noted
Thank you John, I've noted this and will run search if these errors begin to show up in a report or as an on-screen error. Rick -Original Message- From: John Ralls [mailto:jra...@ceridwen.us] Sent: Friday, November 15, 2019 11:02 PM To: Rick Mobley Cc: gnucash-user@gnucash.org Subject: Re: [GNC] Error noted Probably not, because it's more than likely a field that isn't required to be filled, like reconcile date. You could search for "trn:date-posted" (if you use grep to do so you'll want to use `-A 1` to also get the following line) and see that all of those dates are sane... but if you have more than a few transactions that will be at best tedious. Regards, John Ralls > On Nov 15, 2019, at 9:03 AM, Rick Mobley wrote: > > Can I tell what is missing by viewing the XML data file? > > Is this anything of concern? > > Rick > > -Original Message- > From: John Ralls [mailto:jra...@ceridwen.us] > Sent: Friday, November 15, 2019 10:31 AM > To: Rick Mobley > Cc: gnucash-user > Subject: Re: [GNC] Error noted > > > >> On Nov 15, 2019, at 8:10 AM, Rick Mobley wrote: >> >> I'm not seeing an on-screen error, but today I found these "Trace" >> log files in my temp directory today. Gnucash.trace.RNFVA0.log, etc. >> >> >> >> Is this a concern? Should I post as a bug report? >> >> >> >> Running GNuCash v3.6 on a Windows 10 PC. >> >> >> >> >> >> * 13:50:52 WARN Could not spawn perl: Failed to >> execute child process (Bad file descriptor) >> >> * 13:51:16 ERROR xmlNode* time64_to_dom_tree(const >> char*, >> time64): assertion 'time != INT64_MAX' failed >> >> * 13:51:16 ERROR xmlNode* time64_to_dom_tree(const >> char*, >> time64): assertion 'time != INT64_MAX' failed >> >> * 13:51:16 ERROR xmlNode* time64_to_dom_tree(const >> char*, >> time64): assertion 'time != INT64_MAX' failed >> >> * 13:51:16 ERROR xmlNode* time64_to_dom_tree(const >> char*, >> time64): assertion 'time != INT64_MAX' failed >> >> * 13:51:16 ERROR xmlNode* time64_to_dom_tree(const >> char*, >> time64): assertion 'time != INT64_MAX' failed >> >> * 13:51:17 ERROR xmlNode* time64_to_dom_tree(const >> char*, >> time64): assertion 'time != INT64_MAX' failed >> >> * 13:53:35 ERROR xmlNode* time64_to_dom_tree(const >> char*, >> time64): assertion 'time != INT64_MAX' failed >> >> * 13:53:35 ERROR xmlNode* time64_to_dom_tree(const >> char*, >> time64): assertion 'time != INT64_MAX' failed >> >> * 13:53:35 ERROR xmlNode* time64_to_dom_tree(const >> char*, >> time64): assertion 'time != INT64_MAX' failed >> >> * 13:53:35 ERROR xmlNode* time64_to_dom_tree(const >> char*, >> time64): assertion 'time != INT64_MAX' failed >> >> * 13:53:35 ERROR xmlNode* time64_to_dom_tree(const >> char*, >> time64): assertion 'time != INT64_MAX' failed >> >> * 13:53:35 ERROR xmlNode* time64_to_dom_tree(const >> char*, >> time64): assertion 'time != INT64_MAX' failed > > The first one is routine and just means that you're not using > Finance::Quote to retrieve stock prices or currency exchange rates. > > The others indicate an attempt to write an invalid time stamp into the > data file--we use INT64_MAX as the not a time/unknown time value--and > that's probably just an indication that some date field is empty. > > 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] Error noted
Can I tell what is missing by viewing the XML data file? Is this anything of concern? Rick -Original Message- From: John Ralls [mailto:jra...@ceridwen.us] Sent: Friday, November 15, 2019 10:31 AM To: Rick Mobley Cc: gnucash-user Subject: Re: [GNC] Error noted > On Nov 15, 2019, at 8:10 AM, Rick Mobley wrote: > > I'm not seeing an on-screen error, but today I found these "Trace" log > files in my temp directory today. Gnucash.trace.RNFVA0.log, etc. > > > > Is this a concern? Should I post as a bug report? > > > > Running GNuCash v3.6 on a Windows 10 PC. > > > > > > * 13:50:52 WARN Could not spawn perl: Failed to > execute child process (Bad file descriptor) > > * 13:51:16 ERROR xmlNode* time64_to_dom_tree(const > char*, > time64): assertion 'time != INT64_MAX' failed > > * 13:51:16 ERROR xmlNode* time64_to_dom_tree(const > char*, > time64): assertion 'time != INT64_MAX' failed > > * 13:51:16 ERROR xmlNode* time64_to_dom_tree(const > char*, > time64): assertion 'time != INT64_MAX' failed > > * 13:51:16 ERROR xmlNode* time64_to_dom_tree(const > char*, > time64): assertion 'time != INT64_MAX' failed > > * 13:51:16 ERROR xmlNode* time64_to_dom_tree(const > char*, > time64): assertion 'time != INT64_MAX' failed > > * 13:51:17 ERROR xmlNode* time64_to_dom_tree(const > char*, > time64): assertion 'time != INT64_MAX' failed > > * 13:53:35 ERROR xmlNode* time64_to_dom_tree(const > char*, > time64): assertion 'time != INT64_MAX' failed > > * 13:53:35 ERROR xmlNode* time64_to_dom_tree(const > char*, > time64): assertion 'time != INT64_MAX' failed > > * 13:53:35 ERROR xmlNode* time64_to_dom_tree(const > char*, > time64): assertion 'time != INT64_MAX' failed > > * 13:53:35 ERROR xmlNode* time64_to_dom_tree(const > char*, > time64): assertion 'time != INT64_MAX' failed > > * 13:53:35 ERROR xmlNode* time64_to_dom_tree(const > char*, > time64): assertion 'time != INT64_MAX' failed > > * 13:53:35 ERROR xmlNode* time64_to_dom_tree(const > char*, > time64): assertion 'time != INT64_MAX' failed The first one is routine and just means that you're not using Finance::Quote to retrieve stock prices or currency exchange rates. The others indicate an attempt to write an invalid time stamp into the data file--we use INT64_MAX as the not a time/unknown time value--and that's probably just an indication that some date field is empty. 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.
[GNC] Error noted
I'm not seeing an on-screen error, but today I found these "Trace" log files in my temp directory today. Gnucash.trace.RNFVA0.log, etc. Is this a concern? Should I post as a bug report? Running GNuCash v3.6 on a Windows 10 PC. * 13:50:52 WARN Could not spawn perl: Failed to execute child process (Bad file descriptor) * 13:51:16 ERROR xmlNode* time64_to_dom_tree(const char*, time64): assertion 'time != INT64_MAX' failed * 13:51:16 ERROR xmlNode* time64_to_dom_tree(const char*, time64): assertion 'time != INT64_MAX' failed * 13:51:16 ERROR xmlNode* time64_to_dom_tree(const char*, time64): assertion 'time != INT64_MAX' failed * 13:51:16 ERROR xmlNode* time64_to_dom_tree(const char*, time64): assertion 'time != INT64_MAX' failed * 13:51:16 ERROR xmlNode* time64_to_dom_tree(const char*, time64): assertion 'time != INT64_MAX' failed * 13:51:17 ERROR xmlNode* time64_to_dom_tree(const char*, time64): assertion 'time != INT64_MAX' failed * 13:53:35 ERROR xmlNode* time64_to_dom_tree(const char*, time64): assertion 'time != INT64_MAX' failed * 13:53:35 ERROR xmlNode* time64_to_dom_tree(const char*, time64): assertion 'time != INT64_MAX' failed * 13:53:35 ERROR xmlNode* time64_to_dom_tree(const char*, time64): assertion 'time != INT64_MAX' failed * 13:53:35 ERROR xmlNode* time64_to_dom_tree(const char*, time64): assertion 'time != INT64_MAX' failed * 13:53:35 ERROR xmlNode* time64_to_dom_tree(const char*, time64): assertion 'time != INT64_MAX' failed * 13:53:35 ERROR xmlNode* time64_to_dom_tree(const char*, time64): assertion 'time != INT64_MAX' failed Rick ___ 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-user Digest, Vol 197, Issue 31
David, Perfect! The right click is what I was missing. Now I can work with the tab bar in either position. Thank you very much. Rick Message: 3 Date: Tue, 13 Aug 2019 10:44:57 -0500 From: David Carlson To: Adrien Monteleone Cc: Gnucash Users Subject: Re: [GNC] Default tab on open Message-ID: Content-Type: text/plain; charset="UTF-8" I leave lots of tabs open across the top of the window. When I want to go to a tab that I cannot see, I right click on the tab bar and choose the tab from the dropdown list. David Carlson On Tue, Aug 13, 2019, 10:30 AM Adrien Monteleone < adrien.montele...@lusfiber.net> wrote: > Rick, > > It might not be as bad as you fear. > > I never used the scroll feature and just kept closing tabs as they got > too numerous. > > I don?t keep my GnuCash window full width to allow for some other > windows on the same screen. (bills & Invoices due reminders and the > upcoming SX along with a calculator. This also gives me screen space > to view PDF copies of bills to enter into GnuCash) > > Since moving my tabs to the left, I now keep about 8-10 open at all > times (mostly reports) and I use them much more and find it easier to > ?see? the one I want more easily than when they were on top. It took > me all of maybe a day or two of adapting. > > The only drawback is lots of tabs, especially with complicated > reports, can slow down the re-opening of GnuCash, particularly on Windows. > Fortunately (though I?m on Mac) I never shut the app down except to upgrade. > > Regards, > Adrien > > > On Aug 13, 2019, at 10:17 AM, Rick Mobley > wrote: > > > > Yes, by the end of the month, I will likely have 10 tabs open while > > I am > creating invoices. With the tabs at the top, they disappear off to the > right and I can't just "click" on one I can't see without scrolling to > the right. Scrolling now is one tab at a time instead of mouse wheel > to the right and click on the tab I want to display. > > > > For now, I have moved the tabs to the left and I can see them all to > click on the tab I need. I was used to scrolling with the mouse wheel > but if that feature has broken, I will teach this old dog to look for > the tabs on the left side. > > > > Thanks, > > Rick > > > ___ > 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] Default tab on open
Yes, by the end of the month, I will likely have 10 tabs open while I am creating invoices. With the tabs at the top, they disappear off to the right and I can't just "click" on one I can't see without scrolling to the right. Scrolling now is one tab at a time instead of mouse wheel to the right and click on the tab I want to display. For now, I have moved the tabs to the left and I can see them all to click on the tab I need. I was used to scrolling with the mouse wheel but if that feature has broken, I will teach this old dog to look for the tabs on the left side. Thanks, Rick -Original Message- From: Colin Law [mailto:clan...@gmail.com] Sent: Tuesday, August 13, 2019 5:05 AM To: Rick Mobley Cc: gnucash-user Subject: Re: [GNC] Default tab on open Can I just check that you realise you can have multiple tabs open at once, each showing an account. So to switch accounts you just need to click on the tab. Colin On Tue, 13 Aug 2019 at 01:04, Rick Mobley wrote: > > Is there a place to set a "default" tab to open up to? I'd like for it > to open up to my cash account each time, but it seems to open to the > last place when I closed off the program. > > > > Rick > > > > > > > > ___ > 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] Scroll through tabs
David, Yes that is how it has worked in the past, and I’m thinking it was version 3.4 or 3.5, but it doesn’t work with my Windows 10 and version 3.6 Rick From: David Carlson [mailto:david.carlson@gmail.com] Sent: Monday, August 12, 2019 7:25 PM To: Rick Mobley Cc: Gnucash Users Subject: Re: [GNC] Scroll through tabs Rick, Do you keep the mouse pointer over the the tab area when scrolling? David Carlson On Mon, Aug 12, 2019, 7:17 PM Rick Mobley mailto:rlmob...@sbcglobal.net> > wrote: Running ver 3.6 now but one of the prior versions allowed me to use my mouse scroll wheel to cycle through the open tabs. I can no longer do that, so I have reverted to putting the tabs on the left side instead of across the top to allow quick access to them. Otherwise, I had to hit the right arrow 7 times to move from tab 1 to tab 8 which was very unproductive for me. Is there a workaround other than what I have already done? Rick ___ gnucash-user mailing list gnucash-user@gnucash.org <mailto: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.
[GNC] Scroll through tabs
Running ver 3.6 now but one of the prior versions allowed me to use my mouse scroll wheel to cycle through the open tabs. I can no longer do that, so I have reverted to putting the tabs on the left side instead of across the top to allow quick access to them. Otherwise, I had to hit the right arrow 7 times to move from tab 1 to tab 8 which was very unproductive for me. Is there a workaround other than what I have already done? Rick ___ 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] Default open tab
Is there a place to set a "default" tab to open up to? I'd like for it to open up to my cash account each time, but it seems to open to the last place when I closed off the program. Rick ___ 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] Default tab on open
Is there a place to set a "default" tab to open up to? I'd like for it to open up to my cash account each time, but it seems to open to the last place when I closed off the program. Rick ___ 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.
