On Sunday 07 January 2007 07:55, Alex Roitman wrote:
> On Fri, 2007-01-05 at 08:26 +0000, Richard Taylor wrote:
> > I am still see a nasty db bug. It only happens on my main gramps db but
> > it happens everytime.
> > I am concentrating on the gtkprint stuff at the moment so I thought I
> > would just report that this was happening even though I don't have the
> > time to look into it in more detail at the moment.
> > I can provide my db for debugging.
> If you export your db into XML and then import XML
> into the new empty db, does the problem happen again
> with the new db if you do same things?
No the problem does not reappear after a export -> new -> import cycle. I
should have thought of trying that. So it must be a database portability
thing. Nasty, it could catch lots of people out because the database opens up
fine and only fails when you close it.
> > This is completely repeatable.
> > Every time I close gramps I get this error. It leaves the db env corrupt
> > so that gramps will not reopen the database until I remove the
> > ~/.gramps/env directory.
> You actually don't have to remove the whole ~/.gramps/env dir,
> just the ~/.gramps/env/home/blah/blah/filename.grdb/ directory.
Yep I spotted that :-)
> > DBInvalidArgError: (22, 'Invalid argument -- txn_checkpoint: failed to
> > flush the buffer cache Invalid argument')
> This is some mysterious error: I've seen it reported a few times,
> and I have no idea how and why it happens.
Maybe we need a way of catching the situation and explaining the issue to the