see if you can upgrade to the recent version 2.2.10, see:

About the bug, is it possible you moved the database? It is not a portable format, see:

If not that; do the following:
1/take a backup as .gramps file
2/look for the last backup you have and copy it to save place (in the dir as .backup.gramps file)
3/in the tools menu, run the rebuild reference tables tool and rebuild secondary indexes tool. Then run the check and repair tool
4/If above does not work, start a new database and import the .gramps backup into it.


2008/3/22, Bob Shueey <>:
User Information:

It happens whenever I close gramps, by any means.  The x in the top right,
the close
in the KDE program bar, and the exit option in the menu bar

Error Details:

31351707: ERROR: line 147: Unhandled exception
Traceback (most recent call last):
  File "/usr/share/gramps/", line 492, in quit
  File "/usr/share/gramps/GrampsDb/", line 1077, in close
DBRunRecoveryError: (-30977, 'DB_RUNRECOVERY: Fatal error, run database
recovery -- txn_checkpoint: failed to flush the buffer cache
DB_RUNRECOVERY: Fatal error, run database recovery')

System Information:

Python version: 2.4.3 (#1, Apr  3 2007, 03:41:32) [GCC 4.1.1 (Gentoo
BSDDB version:
Gramps version: 2.2.6-1
OS: Linux
Distribution: 2.6.22-gentoo-r5

This email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
Gramps-bugs mailing list