https://bugs.documentfoundation.org/show_bug.cgi?id=95957
--- Comment #19 from Keith Refson <[email protected]> ---
I found this bug report when investigating near identical symptoms with LO
5.1.3
under OpenSuse Leap 42.1
Linux PHTCM1001 4.1.27-27-default #1 SMP PREEMPT Fri Jul 15 12:46:41 UTC 2016
(84ae57e) x86_64 x86_64 x86_64 GNU/Linux
rpm -qa | grep office
libreoffice-templates-en-3.3-15.6.noarch
libreoffice-branding-upstream-5.1.3.2-8.1.noarch
libreoffice-calc-extensions-5.1.3.2-8.1.x86_64
libreoffice-filters-optional-5.1.3.2-8.1.x86_64
patterns-openSUSE-kde_office-20150918-12.1.x86_64
libreoffice-l10n-en-5.1.3.2-8.1.noarch
libreoffice-icon-theme-sifr-5.1.3.2-8.1.noarch
patterns-openSUSE-office-20150918-12.1.x86_64
libreoffice-templates-labels-a4-1.0.1-12.1.noarch
libreoffice-writer-5.1.3.2-8.1.x86_64
libreoffice-base-drivers-mysql-5.1.3.2-8.1.x86_64
libreoffice-icon-theme-breeze-5.1.3.2-8.1.noarch
libreoffice-pyuno-5.1.3.2-8.1.x86_64
libreoffice-math-5.1.3.2-8.1.x86_64
I have a partial diagnosis and a cure. I generated a valgrind trace which
pointed to "Invalid Read"s in a Python library.
Starting LO with an empty PYTHONPATH cures the crash. So it seems that the
problem was an interaction with one of the components - quickly narrowed down
to
/usr/local/lib/python2.7/site-packages and the file "setuptools.pth".
-rw-r--r-- 1 root root 33 Sep 12 2012 setuptools.pth
Rather incredibly stupidly I managed to nuke the file in the act of narrowing
among the files in the directory. So I can't see the contents. D'oh. My guess
was that this was a link to a directory which no longer exists.
In any case it seems clear that (at least in my case) the cause was LO picking
up bad data from the Python environment.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
