Bug 97680 - LibreOffice not correctly signed? (OS X only)
Summary: LibreOffice not correctly signed? (OS X only)
Status: RESOLVED DUPLICATE of bug 89657
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
(earliest affected) release
Hardware: All Mac OS X (All)
: medium critical
Assignee: Not Assigned
: 97453 (view as bug list)
Depends on:
Reported: 2016-02-09 09:52 UTC by steve -_-
Modified: 2016-02-09 13:42 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

LO error msg (33.40 KB, image/png)
2016-02-09 09:56 UTC, steve -_-
osx security settings (78.80 KB, image/png)
2016-02-09 09:57 UTC, steve -_-

Note You need to log in before you can comment on or make changes to this bug.
Description steve -_- 2016-02-09 09:52:56 UTC
User-Agent:       Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:44.0) Gecko/20100101 Firefox/44.0
Build Identifier: LibreOffice


1. install LO from current fresh channel: http://www.libreoffice.org/download/libreoffice-fresh/
2. opening that program via double click works fine *But*
3. download german (or any?) language pack
4. install language pack
5. double click LO app after successful language pack installation

Resulting in error message "LibreOffice is damaged and can't be opened. You should move it to the Trash.
Cancel | Move to Trash

LibreOffice should open.

Something is very wrong here. This seems to be related to signature becoming invalidated or corrupted after using the language pack installer since before that, LibreOffice opens just fine.

High priority since that would affect surely all german language pack LO users and potentially other language pack users as well (didn't test).

Reproducible: Always

[Information automatically included from LibreOffice]
Locale: de
Module: StartModule
[Information guessed from browser]
OS: Mac OS X (All)
OS is 64bit: no

Reset User Profile?No
Comment 1 steve -_- 2016-02-09 09:56:18 UTC
more info: if then changing osx security settings to open any application (not signed), LO opens up fine. But this should not be necessary.

adding screenshots
Comment 2 steve -_- 2016-02-09 09:56:33 UTC
Created attachment 122476 [details]
LO error msg
Comment 3 steve -_- 2016-02-09 09:57:00 UTC
Created attachment 122477 [details]
osx security settings
Comment 4 steve -_- 2016-02-09 12:21:41 UTC
Setting to NEW as we have another report describing this.
Comment 5 steve -_- 2016-02-09 12:21:52 UTC
*** Bug 97453 has been marked as a duplicate of this bug. ***
Comment 6 Christian Lohmaier 2016-02-09 13:42:42 UTC

you need to launch LO at least once before installing a languagepack.

bug#89657 has some proposals on how this could be solved.

*** This bug has been marked as a duplicate of bug 89657 ***