Bug 98956 - "Unidentified developer" error when trying to install Russian language pack in OS X
Summary: "Unidentified developer" error when trying to install Russian language pack i...
Status: RESOLVED DUPLICATE of bug 93331
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Localization (show other bugs)
Version:
(earliest affected)
5.0.5.2 release
Hardware: All macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-29 13:51 UTC by Tele
Modified: 2016-05-20 07:25 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tele 2016-03-29 13:51:01 UTC
Hi,

when trying to install LibreOffice_5.0.5_MacOS_x86-64_langpack_ru.dmg ,
I see the "Unidentified developer" error in OS X 10.11.4.

Are your language packs signed with a valid digital signature?

Thanks.
Comment 1 Buovjaga 2016-04-07 10:58:33 UTC
See the answer in https://ask.libreoffice.org/en/question/27774/osx-maverick-unidentified-developer/

Have you tried right-clicking the app, and then choosing 'Open'? That is the basic small step to open apps from unidentified developers introduced with OSX 10.7 or 10.8. If that doesn't help, setting the security option in the system preferences for allowed software to "all sources (App Store, identified developers and unidentified developers)" should do the trick.
Comment 2 Alex Thurgood 2016-05-18 08:52:06 UTC
(In reply to Tele from comment #0)
> Hi,
> 
> when trying to install LibreOffice_5.0.5_MacOS_x86-64_langpack_ru.dmg ,
> I see the "Unidentified developer" error in OS X 10.11.4.
> 
> Are your language packs signed with a valid digital signature?
> 
> Thanks.

The answer to that question is "No, the lang-packs are not signed." You need to bypass Gatekeeper security in order to install them. Then when you restart LO, you also need to do so via the Open context menu at least the first time, as installation of the lang-packs modifies the bundle and will trigger Apple's "the file is damaged, put it in the bin", bla message.
Comment 3 raal 2016-05-19 09:23:22 UTC
setting to new. Workaround as Alex explained looks weird for me, but I'm not familiar with OSX, so revert my decision if I'm wrong.
Comment 4 Alex Thurgood 2016-05-20 07:25:25 UTC

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