Ask Your Question

LibreOffice 5.2.1 & 5.1.5 crashing after upgrading to macOS Sierra (10.12)

asked 2016-09-23 16:23:30 +0200

Blanksheet gravatar image

updated 2016-10-14 09:25:32 +0200

David gravatar image
  • MacBook Pro late 2011
  • macOS Sierra

Upgraded the OS to macOS Sierra and LO 5.2.1 crashed on startup with message application quit unexpectedly.

LO worked before the upgrade and all other programs are working fine with the new OS.

I downgraded LO to 5.1.5 and have the same problem.


Renaming the user folder to see if that would correct the problem, same results.

Installed LO 5.1.5 to see if that would resolve the issue. LO opened the first time I started the program and then crashed the next time with the above error message.

First part of the crash report from the 5.1.5 version installation:

Process:               soffice [831]
Path:                  /Applications/
Identifier:            org.libreoffice.script
Version:               5.1.5002 (5.1.5002)
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           soffice [831]
User ID:               501

Date/Time:             2016-09-21 10:44:45.709 -0400
OS Version:            Mac OS X 10.12 (16A323)
Report Version:        12
Anonymous UUID:        1243F49C-597B-4A22-4C0A-07CF2E4C5270

Time Awake Since Boot: 4700 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue:

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Segmentation fault: 11
Termination Reason:    Namespace SIGNAL, Code 0xb
Terminating Process:   exc handler [0]

Any suggestion on how to fix this?

edit retag flag offensive close merge delete


Alex Thurgood gravatar imageAlex Thurgood ( 2016-09-23 16:39:30 +0200 )edit

Someone is trying to work on a fix, but it doesn't appear to be working yet.

Alex Thurgood gravatar imageAlex Thurgood ( 2016-09-23 16:43:23 +0200 )edit

Anyone have any information on when an update will be released to fix the macOS Sierra problems ?

Will a patch be released or do we have to wait for the next release cycle?

Blanksheet gravatar imageBlanksheet ( 2016-10-03 22:46:33 +0200 )edit

Open a Terminal-Session and start it with /Applications/

works for me.

cd ~/Desktop ln -sf /Applications/ ./LibreOffice and as a workaround you should be able to start LO by double-click

Knut_HH gravatar imageKnut_HH ( 2016-11-14 00:06:32 +0200 )edit

12 Answers

Sort by » oldest newest most voted

answered 2016-09-24 18:05:30 +0200

tonyf gravatar image

No answer, but I have the same problem but only with the word processor. The spreadsheet seems to work OK. These are the two I used most and a fix for the word processor would be very welcome.

edit flag offensive delete link more


This would be more appropriate as a comment below the original question, because it is not an answer.

EasyTrieve gravatar imageEasyTrieve ( 2016-10-08 03:19:38 +0200 )edit

answered 2016-10-07 21:03:02 +0200

I have a macbook pro 15" mid 2010 with discrete invidia graphic card (nvidia 330M).

The issue arises when the discrete graphic card is not engaged. When it is, everything goes fine. You can check it by yourself with GfxCardStatus. I hade a similar problem with "Preview" app, but Apple's developer were been able to fix it. Now is DocumentFoundation turn.

The strange things are that: 1) Usually LibreOffice never engaged the discrete graphic card but now it does; 2) When it does the card is switched on and off two or three times.

I can send any information needed to LibreOffice developer, if they think I might help.

edit flag offensive delete link more


I have a similar issue on a MacBook Pro (Retina 13-inch late 2013 GPU Intel Iris 1536 MB + ). LO works fine when the Mac is connected only to an Apple Thunderbolt Display. LO Writer crashes when opening any new or existing document when the internal Retina display is set as primary/only display. Same problem on all recent LO versions 5.2.2, 5.2.1 and 5.1.5 . Strangely, this problem is inexistent on a recent MacBook Pro (Retina, 15-inch, Mid 2015 PGU Intel Iris Pro + AMD Radeon R9 M370X)

MHOHEN gravatar imageMHOHEN ( 2016-10-10 11:34:06 +0200 )edit
Login/Signup to Answer

Question Tools



Asked: 2016-09-23 16:23:30 +0200

Seen: 11,350 times

Last updated: Nov 13 '17