Windows savefile causes to crash next open time

[NoNameA 774]

2015-02-21 1:06 GMT+09:00 Colin Law <clanlaw at gmail.com>:

> On 20 February 2015 at 15:49, NoNameA 774 <nonamea774 at gmail.com> wrote:
> > 2015-02-21 0:34 GMT+09:00 Colin Law <clanlaw at gmail.com>:
> >
> >> On 20 February 2015 at 15:03, NoNameA 774 <nonamea774 at gmail.com> wrote:
> >> > Hi, I'm using gnucash(2.6.5) in Windows 7.
> >> > I encountered a crash problem. I saved my gnucash file(XML, sqlite)
> >>
> >> What do you mean by XML, sqlite?
> >>
> >> Colin
> >>
> > It means both XML and sqlite leads to crash.
> >
> > I encountered in xml save file, so I next tried sqlite save file.
> > But both of them will lead to crash..
>
> Are you still able to open files that you saved before this started
> happening?
>
> Colin
>

In my Arch Linux Machine, I can read/write my GNUCash save file, so my
transactions are safe.
It's only inconvenience.

Thanks
nona


>
> >
> > nona
> >
> >
> >>
> >> > in
> >> > Windows GNUCash and I reopen that file, then my gnucash crashed.
> >> >
> >> > This is steps to reproduce.
> >> > Create new book and save xml file in Windows GNUCash.
> >> > Open that file.
> >> >
> >> > I encountered this crash in another Windows Machine too, but not
> occurred
> >> > in Arch Linux.
> >> >
> >> > I roughly looked through bugzilla and mailing list archive, but not
> found
> >> > idea.
> >> > Do you have any information about this?
> >> >
> >> > Thanks.
> >> > nona
> >> > _______________________________________________
> >> > gnucash-user mailing list
> >> > gnucash-user at gnucash.org
> >> > https://lists.gnucash.org/mailman/listinfo/gnucash-user
> >> > -----
> >> > 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 at gnucash.org
> > https://lists.gnucash.org/mailman/listinfo/gnucash-user
> > -----
> > Please remember to CC this list on all your replies.
> > You can do this by using Reply-To-List or Reply-All.
>