Re: [Gramps-users] 4.2.3 merging places causes Gramps crash

[Enno B. <enn...@gm...>]

Op 24-09-16 om 03:55 schreef Rich:
> Gramps 4.2.3 running on Linux Mint 18 Cinnamon.
> Received another failure today.
> Merged maybe 8 - 10 places and had one failure.
> Message:
> Gramps has experienced an unexpected error.
> I selected Report
>  Window came up to report a bug. This first window just tells me it is 
> the Bug Reporting Assistant and a little about how it works..
> I selected Next to go to the next page and Gramps hung up.  I believe 
> it is what I call a soft lock up as the system was still ok to do 
> anything but Gramps. I had to use the System Monitor to close Gramps.
> Could I be missing an optional module for the Bug Report Assistant to 
> work?
Not that I know of. I refuse to upgrade to Mint 18 myself, because it 
breaks Gramps 3.4.9, and the lock up that you see may have a similar cause.

Normally, an error message has a little more text than what you wrote 
above, and you may be able to copy paste some text from the first window 
you see, i.e. before you move on to the bug reporting assistant. Did you 
see anything more than what you wrote above?

If not, and you still have places to merge, or a backup that you can try 
the merging on, I suggest that you start a terminal window, and type 
'gramps' in that, instead of starting 4.2.3 from the menu. This may help 
you to see more error info, and if something happens, there's hardly a 
lock up that would stop you from copy pasting info from that terminal 
window. It has the extra advantage that if Gramps locks up, you can type 
Ctrl-\ to kill it in a very effective way.

It would be nice for developers if you can try this on a backup that you 
made before merging, so that we can see whether it happens again after a 
dozen places or so, and whether there is a pattern here.

thanks,

Enno