Obviously the solution to your problem is to move to Arizona! David C
On Mon, Oct 29, 2018 at 9:09 AM Colin Law <clan...@gmail.com> wrote: > I am seeing similar problems in the UK running 3.3 on Ubuntu 18.10, from > Ubuntu repo. > The issue occurs if one tries to enter 28/10/18 in the statement date, > which is why the '-' fails. Any other date is ok whether entered using t, > +, -, the calendar, or entering manually via the keyboard. I see the same > error in the trace file as Richard is seeing when 28th is entered. > Richard, is it ok if you enter dates other than 28th? > It also happens if one tries to enter 29/10/17 which was also DST day. > > Colin > > On Mon, 29 Oct 2018 at 12:24, Richard Ullger <rull...@gmail.com> wrote: > > > On 29/10/2018 02:59, John Ralls wrote: > > > > > > > > Sigh. No, and I thought that I’d fixed all of the timezone and DST > > issues. I’ll be interested to know if the problem goes away when you try > > again on Monday. > > > > > > Regards, > > > John Ralls > > > > > > > Hi John, > > > > Unfortunately I've had mixed results trying to reconcile today. > > > > The first register I tried reconciled without any issues. The statement > > date was populated with today's date, 29/10/18. I was able to press '-' > > twice to change the date to 27/10/18. The register ending balance was > > populated with the last balance in the register and I was able to paste > > a value to replace it and proceed with the reconciliation. > > > > Another register cannot be reconciled to the correct date. It has the > > last balance as at 28/10/18. When the Reconcile Information window > > opens, the statement date is populated with today's date, 29/10/18 and > > the Ending Balance is the correct amount. Pressing '-' in the statement > > date box changes the date to 01/10/18 and changes the ending balance to > > the amount as at that date. Pressing 't' resets the date to today's date > > and the balance to the corresponding amount. Selecting a date from the > > calendar dropdown has no effect and doesn't change the date. So I've > > reconciled to today's date as a workaround. > > > > Several other registers have similar issues and the error message > > > > * 11:52:14 CRIT <gnc.gui> gnc_date_edit_set_time_internal: assertion > > 'mytm != NULL' failed > > > > appears several times in the gnucash.trace file. > > > > Closing and restarting gnucash has no effect on the outcome. > > > > Regards, > > > > Richard > > _______________________________________________ > > 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. _______________________________________________ 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.
