This version of gramps crashes for me with the following C stack trace: *** glibc detected *** /usr/bin/python: munmap_chunk(): invalid pointer: 0x0000000001abc5a0 *** ======= Backtrace: ========= /lib/libc.so.6[0x7f1b0aafd2ed] /lib/libc.so.6(closedir+0xd)[0x7f1b0ab21d3d] /usr/lib/libglib-2.0.so.0(g_dir_close+0x11)[0x7f1b089401e1] /usr/lib/enchant/libenchant_myspell.so(_ZN14MySpellChecker17requestDictionaryEPKc+0x314)[0x7f1af9400784] /usr/lib/enchant/libenchant_myspell.so[0x7f1af9400a50] /usr/lib/libenchant.so.1[0x7f1af9608b35] /usr/lib/libenchant.so.1(enchant_broker_request_dict+0x67)[0x7f1af9608cf7] /usr/lib/libgtkspell.so.0[0x7f1af9811cd9] /usr/lib/libgtkspell.so.0(gtkspell_set_language+0x24)[0x7f1af9812114] /usr/lib64/python2.5/site-packages/gtk-2.0/gtkspell.so[0x7f1af9a152a0] /usr/lib/libpython2.5.so.1.0(PyEval_EvalFrameEx+0x5415)[0x7f1b0b0a96e5] /usr/lib/libpython2.5.so.1.0(PyEval_EvalCodeEx+0x6b5)[0x7f1b0b0ab1e5] /usr/lib/libpython2.5.so.1.0(PyEval_EvalFrameEx+0x5606)[0x7f1b0b0a98d6] Given that it is a C backtrace I'm not sure if gramps really is to blame, but at least I do get this with gramps consistently.
What action is needed to get it crashed? Which version of libenchant do you have installed and does unmerging pyenchant help you to get it started?
It crashes on startup. I have app-text/enchant-1.4.2 installed. I don't have pyenchant installed at all, I probably passed on that due to its test failures reported in bug 261908. Installing pyenchant 1.1.5 causes gramps to hang on startup instead of crashing to the point that it doesn't react to Ctrl-C.
Ok, maybe you can have a look at Gramps 3.1.1 which should be reworked in many parts.
Just upgraded to gramps-3.1.1 and that works as expected with USE flags (gnome reports spell -debug)
Gramps 3.1.1 is stable
