From: Rosina B. <rbi...@ea...> - 2004-05-30 20:21:03
|
I've had this happen a few times now (but not all the time), so here's a traceback. This sometimes happens while gramps is doing an autosave. GRAMPS has encountered an internal error. Please copy the message below and post a bug report at http://sourceforge.net/projects/gramps or send an email message to gra...@li... GRAMPS : 1.0.3-1 LANG : en_US.UTF-8 Python : 2.2.3 final GTK : 2.2.4 PyGTK : 1.99.16 OS : Red Hat Enterprise Linux WS release 3 (Taroon Update 2) Traceback (most recent call last): File "/usr/share/gramps/WriteXML.py", line 81, in exportData g.write(filename) File "/usr/share/gramps/WriteXML.py", line 166, in write self.write_xml_data() File "/usr/share/gramps/WriteXML.py", line 320, in write_xml_data family = familyMap[key] KeyError: F1277 If you need any more information, let me know and I'll see what more I can provide. Cheers, Rosina -- Rosina Bignall rbi...@ea... |
From: Don A. <don...@co...> - 2004-05-30 20:39:49
|
Try running the "Check and repair database" tool under Tools->Database processing. It looks like a family was not completely deleted. This may happen in the merge tool if it cannot figure out what to do. If you can send us a test case (the original database before the merge), we might be able to fix the problem. If you have problems saving the data, you should be able to go back to the previous version by renaming the "data.gramps.bak" file to "data.gramps". Don On Sun, 2004-05-30 at 14:19, Rosina Bignall wrote: > I've had this happen a few times now (but not all the time), so here's a > traceback. This sometimes happens while gramps is doing an autosave. > > GRAMPS has encountered an internal error. > Please copy the message below and post a bug report > at http://sourceforge.net/projects/gramps or send an > email message to gra...@li... > > GRAMPS : 1.0.3-1 > LANG : en_US.UTF-8 > Python : 2.2.3 final > GTK : 2.2.4 > PyGTK : 1.99.16 > OS : Red Hat Enterprise Linux WS release 3 (Taroon Update 2) > > Traceback (most recent call last): > File "/usr/share/gramps/WriteXML.py", line 81, in exportData > g.write(filename) > File "/usr/share/gramps/WriteXML.py", line 166, in write > self.write_xml_data() > File "/usr/share/gramps/WriteXML.py", line 320, in write_xml_data > family = familyMap[key] > KeyError: F1277 > > > If you need any more information, let me know and I'll see what more I > can provide. > > Cheers, > Rosina |
From: Rosina B. <rbi...@ea...> - 2004-05-31 23:11:23
|
Don Allingham wrote: >Try running the "Check and repair database" tool under Tools->Database >processing. > >It looks like a family was not completely deleted. This may happen in >the merge tool if it cannot figure out what to do. If you can send us a >test case (the original database before the merge), we might be able to >fix the problem. > > Yes, it does seem to have been happening while I was in the midst of merging people, so I imagine that was it. My database is around 3000 people, but I could send it if you want. After the merge completed I was able to save the database, and the "check and repair database" tool caught a couple families that had been broken. Thanks for your help and your quick responses! Rosina -- Rosina Bignall rbi...@ea... |
From: Don A. <don...@co...> - 2004-05-31 23:14:47
|
If you have the pre-merge list, and which people you merged, it would help. If you can send me the database, I'll take a look. Don On Mon, 2004-05-31 at 17:09, Rosina Bignall wrote: > Don Allingham wrote: > > >Try running the "Check and repair database" tool under Tools->Database > >processing. > > > >It looks like a family was not completely deleted. This may happen in > >the merge tool if it cannot figure out what to do. If you can send us a > >test case (the original database before the merge), we might be able to > >fix the problem. > > > > > > Yes, it does seem to have been happening while I was in the midst of > merging people, so I imagine that was it. My database is around 3000 > people, but I could send it if you want. After the merge completed I > was able to save the database, and the "check and repair database" tool > caught a couple families that had been broken. > > Thanks for your help and your quick responses! > > Rosina > |