Can you reproduce the bug with the example database?
You normally find it after install as:
Then exactly say what I have to do to get this problem. Just tried, no
problems to be seen, also not after delete
If it is only with your dataset, you will have to send me that privately so
I can try the dataset here to see if I obtain the bug.
2008/1/18, Wally Murdoch <henrysforkrvr@...>:
> I apologize if this isn't sufficient information. Lockup of Gramps was
> such that the usual OS/program data was not available.
> I am using Ubuntu 7.10 as recent as can be obtained using the update
> feature. I was using Gramps 2.2.9, upgraded to 2.2.10-1, last night I
> fired up 3.0 hoping that would cure my slow database update problem but
> no luck.
> What follows is a description of a lockup that occurred using 3.0.
> Below is information about my slow database update problem that may be
> related to the 3.0 lockup
> I created several Family Trees. I imported .gramps XML data into one.
> All okay.
> Opened second FT, expected action is for Gramps is to save and close
> first FT, then open second.
> In saving first FT, progress dialog in lower left corner gets to 87%,
> screen cursor continues to indicate that Gramps is working.
> After approximately 2 minutes Error Report dialog screen appears.
> Following data is the detail of that dialog.
> 379433: ERROR: gramps.py: line 162: Unhandled exception
> Traceback (most recent call last):
> File "/usr/share/gramps/DisplayModels/_PeopleModel.py", line 476, in
> return self.mapper.first_child(node)
> File "/usr/share/gramps/DisplayModels/_PeopleModel.py", line 166, in
> return self.top_path2iter
> IndexError: list index out of range
> When I click on Report in the Error Report dialog, gramp.py opens.
> Clicking on Forward button does not work, nor does the cancel button.
> Moving focus back to Gramps, cursor still shows that it is working.
> Cannot exit Gramps normally, I have to reboot.
> There is a bug here with the action of the Error Report dialog, but I am
> not so sure about the indexing problem. Please read the following which
> I posted to Gramps-User 17 Jan 2008. I may have some unknown computer
> problem causing this action and therefore the problem is unique to my
> Message posted to Gramps-User regarding slow database update.
> 2008/1/18, Wally Murdoch <henrysforkrvr@...>:
> Would someone please tell me how a grdb database should react to
> a delete person request.
> When I delete a person from the database the action takes 3 -
> 3.5 minutes to complete. I think that the entire database of 250
> individuals is being parsed. Is this normal for the current
> state of the GRAMPS program?
> This problem seemed to start with 2.2.9. Seeing that 2.2.10-1
> was available I upgraded but no change to the problem.
> I might add that somewhere prior to noticing the problem in
> 2.2.9 I reformatted my hard drives and reconfigured data folder
> names. As if this isn't enough, I upgraded my operating system
> from Ubuntu Feisty (7.04) to Gutsy (7.10) and I continue to
> upgrade as notifications arrive to my computer. I have done
> these reconfigs many times in the past with very little
> I don't know how long this problem with deletion has been going
> on as I do not use the delete feature very often as for most
> part I really do get along with my relatives. I should also say
> that I am not aware of any other problems with GRAMPS and my
> Appreciate any input one would have about this problem.
> If you need more information regarding this bug report for 3.0, please
> contact me.
> Wally Murdoch
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> Gramps-bugs mailing list