As a general remark:
The grdb files are not portable, read:

Can that be to blame?
If that is not the reason, then try the following:

1/export to .gramps format to have a backup
2/in Tools run  'rebuild reference tables'
3/in Tools run  'rebuild secondqry indexes'
4/in Tools run  'check and repair'

The above solves inconsistencies in the data that can have been introduced due to bad import or a bug.
If possible; upgrade afterwards  to 3.0.1, you find an ubuntu package on our website

If the problem persists, let us know


2008/10/6 glyph <>
User Information:

Saving file

Error Details:

790637: ERROR: line 488: Failed to open database.
Traceback (most recent call last):
  File "/usr/share/gramps/", line 485, in open_saved_as
  File "/usr/share/gramps/GrampsDb/", line 465, in load_from
  File "/usr/share/gramps/GrampsDb/", line 384, in load
    self.metadata     = self.open_table(self.full_name,"meta")
  File "/usr/share/gramps/GrampsDb/", line 159, in open_table, table_name, dbtype, self.open_flags(), 0666)
DBInvalidArgError: (22, 'Invalid argument -- /home/deus/geneology/Valiquette Family/Valiquette.grdb: unexpected file type or format')

System Information:

Python version: 2.5.2 (r252:60911, Jul 31 2008, 17:28:52) [GCC 4.2.3 (Ubuntu 4.2.3-2ubuntu7)]
BSDDB version:
Gramps version: 2.2.10-1
OS: Linux
Distribution: 2.6.24-19-rt

All those ... moments will be lost ... in time, like tears ... in rain.  Roy Batty NEXUS 6

This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
Gramps-bugs mailing list