--- Comment #25 from Keith Refson <> ---
Sorry about the delay with this.  I was not yet able to get debugging symbol

However I have managed to narrow down the cause a lot further, after recovering
the "setuptools.pth" in my Python 2.7 local site-packages.  This allowed me to
identify the single Python package at the root of the crash.

Skipping any more tedious details, the conclusion is

If my installation of the Python package "enum" is in the PYTHONPATH, LO fails
on startup with std::Bad_Alloc.

If the installation of the Python package "enum" is NOT in PYTHONPATH, LO
startup succeeds.

I will upload a tarball containing the offending Python package.  Perhaps
others can try to see if adding this to your Pythonpath replicates the failure?

You are receiving this mail because:
You are the assignee for the bug.
Libreoffice-bugs mailing list

Reply via email to