you lost connection to the database backend. This type of error is normally not reproducable.

You will have better success if you work with the GRAMPS native format, so create a .grdb file, and import XML/GEDCOM into it, work on the grdb, and export to xml from time to time as a backup means.


2007/11/6, Patrick Royer <>:
"User Information: ===================Error Details:
===================247220: ERROR: line 148: Unhandled
exceptionTraceback (most recent call last): File
"/usr/share/gramps/Editors/", line 220, in ok_clicked
self.commit_event(self.source,trans) File
"/usr/share/gramps/GrampsDb/", line 564, in
commit_personal_event self.commit_event(event, transaction, change_time)
File "/usr/share/gramps/GrampsDb/", line 281, in
GrampsDbBase.commit_event(self,event,transaction,change_time) File
"/usr/share/gramps/GrampsDb/", line 578, in commit_event
transaction, change_time) File
"/usr/share/gramps/GrampsDb/", line 448, in _commit_base
transaction.add(key, handle, old_data, new_data) File
"/usr/share/gramps/GrampsDb/", line 2276, in add
1)DBError: (0, 'DB object has been closed')System Information:
===================Python version: 2.5.1 (r251:54863, May 2 2007,
16:56:35) [GCC 4.1.2 (Ubuntu 4.1.2-0ubuntu4)] BSDDB version:
Gramps version: 2.2.8-0.SVN LANG: en_US.UTF-8OS: LinuxDistribution:
2.6.20-16-generic "

This email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>
Gramps-bugs mailing list