Windows savefile causes to crash next open time
NoNameA 774
nonamea774 at gmail.com
Sat Feb 21 08:52:46 EST 2015
2015-02-21 22:40 GMT+09:00 Geert Janssens <geert.gnucash at kobaltwit.be>:
> On Saturday 21 February 2015 13:27:57 Colin Law wrote:
>
> > On 21 February 2015 at 13:22, Geert Janssens <geert.gnucash at kobaltwit.be>
> wrote:
>
> > >> I showed trace log(with option " --debug --extra"). I could not get
>
> > >> any idea from that.
>
> > >> This is that trace.
>
> > >> https://gist.github.com/nna774/9bc91251fc3dec2ebfb5 Can you get any
>
> > >> information from here?
>
> > >
>
> > > Unfortunately no. There is no clue as to why the program suddenly
>
> > > stops.
>
> > >
>
> > > If it *is* due to an invalid date, you could search the gnucash xml
>
> > > file for a date starting with '1969-'.
>
> > >
>
> > > If there's no such date in your data file the issue is not an
>
> > > invalid date, but something else.
>
> >
>
> > If a date was the issue would the file open ok in linux but not in
>
> > Win?
>
> >
>
> Yes.
>
>
>
> For Windows the oldest acceptable date is 1970-01-01 while on linux that
> is 1969-12-31.
>
>
>
> So you *can* get into a situation where the file has this 1969 date which
> works well on linux but not on Windows.
>
>
>
> We have had issues with this in the past which is why I want to verify
> this.
>
>
>
> Geert
>
In my gnucash file, there is no 1969- date.
$ zcat kakeibo.gnucash | grep 1969
puts no output.
I think I had setup assistant on linux.
thanks, nona
More information about the gnucash-user
mailing list