My database got corrupted some time ago and I have been unknowingly adding to this corrupted file for some time now.
I was wondering how 6.0-beta 2 would fair if I started a new family tree in this version. It’s in beta, yes, but is it considered safe if I’m not using a database file from a previous version of gramps?
My appologies, of course the error message would be helpful with tracing the error it self…
The below error log is from clicking one of the ovals. Clicking Jane leads to it loading for a good while and eventually showing zero people in the chart view.
862749: ERROR: grampsapp.py: line 188: Unhandled exception
Traceback (most recent call last):
File "C:\Users\Matt\AppData\Local\gramps\gramps52\plugins\GraphView\graphview.py", line 4436, in edit_family
family = self.dbstate.db.get_family_from_handle(handle)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Program Files\GrampsAIO64-5.2.3\gramps\gen\db\generic.py", line 1347, in get_family_from_handle
return self._get_from_handle(FAMILY_KEY, Family, handle)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Program Files\GrampsAIO64-5.2.3\gramps\gen\db\generic.py", line 1341, in _get_from_handle
raise HandleError("Handle %s not found" % handle)
gramps.gen.errors.HandleError: Handle -8419 not found
Yes, this gives a lot of information. Specifically, this is Gramps 5.2.3. Did you convert this tree to Gramps 6.0 and then attempt to use it in 5.2? Or something else? In any event, the error shows that the handle for this Family is missing, and so your data does appear to be a bad state. Running the “Check” tool should catch and fix that.
I may have but I created a new tree and imported a backup from 16th of January 2025, untouched by the beta, and it shows the same ovals in the chat view.
Ocassionaly Gramps will say there is a problem with the tree and prompt for a fix, doing so it says all is well.
Manually doing the check also reveals no errors.
That why I was considering starting from scratch in 6.0.0 beta 2. I would happily lose the old datafile and transcribe the info over fresh, manually, so that there are zero errors in the new file going forward.
Ok, so in summary this doesn’t sound like it has anything to do with Gramps 6.0. Either the tree was already corrupted, or perhaps there is an bug in previous versions of Gramps. If you feel comfortable sharing your tree with me via direct message, I’d be glad to take a look.