On 10/5/2014 1:44 PM, Michael Shell wrote:
On Sun, 05 Oct 2014 07:59:46 -0400
Alan Feuerbacher <[email protected]> wrote:
"Fatal Python error: Invalid thread state for this thread . . ."
Google found this:
http://lists.freedesktop.org/archives/libreoffice/2013-April/050229.html
It seems the debug option --enable-dbgutil can cause it by detecting
a failed assertion. The next step would be to start disabling extensions
(removing --enable-ext- stuff) to find which one triggers it.
When changing the status of --enable-dbgutil, be sure and do a make
clean before recompiling or else there will be problems:
http://lists.freedesktop.org/archives/libreoffice/2011-October/019329.html
Lastly, based on my past experience with problems with Abiword, very often
a crash a few seconds after the startup of a word processor (which often
really means, jsut after something is typed in) can be caused by problems
with the spell checker and/or the main text font. Try to change the font
and disable the spell checker before typing anything in and see if that
stops the crash.
Thank you! I didn't try the switch --enable-dbgutil, but that helped to
spur me to look in a direction that eventually solved the problem --
more or less. More on that later.
Basically, I had to change the configure switch --enable-python=system
to --enable-python=fully-internal. I haven't fully sorted out the other
issues, but the various LibreOffice programs fire up without crashing
and seem to function properly.
Alan
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
