Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 1355598

Summary: Libreoffice crash using libreoffice-TexMaths
Product: [Fedora] Fedora Reporter: Kevin Lynch <klynch>
Component: libreofficeAssignee: Caolan McNamara <caolanm>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: caolanm, dtardon, erack, klynch, mstahl, orion, sbergman
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-13 18:29:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Description Flags
Backtrace taken with 'libreoffice --backtrace'
valgrind output none

Description Kevin Lynch 2016-07-12 03:45:45 UTC
Created attachment 1178639 [details]
Backtrace taken with 'libreoffice --backtrace'

Description of problem:

Attempting to use the fedora packaged texmaths for libreoffice results in a double free within soffice.bin, leading to a crash that frequently brings down GNOME Shell in addition to libreoffice.

Version-Release number of selected component (if applicable):

libreoffice-TexMaths.x86_64            0.41-3.fc24                 @fedora   
libreoffice-core.x86_64                1:            @updates     

How reproducible:

95+% of time; It has happened every time when I enter more than one character in the equation entry box, but only almost always with one character (which typically isn't very useful).  

Steps to Reproduce:
1. Create empty Impress or Writer document
2. Click 'TexMaths Equations' on toolbar
3. In popup window, enter an equation ('a' is nearly always sufficient)
4. Click 'Latex' button

Actual results:

Some form of crash, up to and including taking down GNOME Shell and killing the user session.

Expected results:

Creates TexMaths object in document

Additional info:

Attached backtrace created with 'libreoffice --backtrace' from one of the crashes that didn't take down the user session.

Does not seem to depend on stale user configuration data: I can also reproduce this in a freshly created user account that has never run an application.

Comment 1 Orion Poplawski 2016-07-12 16:33:27 UTC
Can you see if helps at all?

Comment 2 Orion Poplawski 2016-07-12 16:35:05 UTC
If not, the output of a crash when run under valgrind might be helpful.

Comment 3 Kevin Lynch 2016-07-13 16:05:11 UTC
(In reply to Orion Poplawski from comment #1)
> Can you see if
> helps at all?

Unfortunately, no.  I see the same behavior.

Comment 4 Kevin Lynch 2016-07-13 16:13:17 UTC
Created attachment 1179338 [details]
valgrind output

Comment 5 Kevin Lynch 2016-07-13 16:14:16 UTC
(In reply to Orion Poplawski from comment #2)
> If not, the output of a crash when run under valgrind might be helpful.

When run under valgrind, it doesn't crash.  Even worse, it works as expected.  It would be a viable solution for my immediate needs if it wasn't as slow as molasses :-)   

Again, I created a new user account that hadn't done anything else.  I followed the instructions here to launch libreoffice from the command line to produce the valgrind report:, adding the flag "--leak-check=full" to the command line.  I created an empty Impress presentation, immediately clicked on the "TexMaths Equations" in the toolbar, and created a short equation, then exited libreoffice.

It produces the attached report valgrind-bug1355598-20160713.log reference in comment #4.  I hope this helps.  If not, let me know what else I can try.

Comment 6 Kevin Lynch 2016-07-13 18:23:37 UTC
dnf just picked up an update to the libreoffice suite ( with updates to lots of packages.  With this update, I no longer see the crash behavior I reported here.  So, I don't know what the problem was, or what fixed it, but the issue appears to have gone away for me.  I'd mark it closed and apologize for wasting your time, but I don't know what the right closed status is for "intervening fix".

Comment 7 Orion Poplawski 2016-07-13 18:29:58 UTC
Thanks for the update.