Downloaded file LibreOffice_5.0.2_MacOS_x86-64.dmg directly from site. DMG file verified as usual before opening, installed, then tried to execute - OSX reports LibreOffice broken and aborts (and erases it from /Application). I've had this before with LibreOffice_5.0.1_MacOS_x86-64.DMG, but that typically happened if I applied the language pack LibreOffice_5.0.1_MacOS_x86-64_langpack_en-GB.dmg before once opening LibreOffice, so avoided the Langpack completely, to no avail. Fresh download, tried again, same result. Reverted to 5.0.1 (D/L via torrent), works fine, langpack applied, still works as expected. I have not tried the 5.0.2 version that is available in the Apple App Store. System: OSX 10.11 (El Capitan), 16GB RAM, 2.5 GHz Intel Core i7.
hmmm. 10.11 and LO vanilla latest from MAS as well as latest nightly (both as of today 2015-10-01) do run fine here. no language packs.
I am rebuilding this OSX 10.11 MBP from the ground up this weekend, and after that I will try again with a straight download from the LO site, just to be sure.
No repro for me either with OSX 10.11
@Fred : try removing/renaming your LO user profile to see if that makes a difference
OK, the Mac involved has been rebuilt from the ground up, just in case (it needed a cleanup anyway) - problem no longer present. This was even with a user profile ported from the old system. Rebuilt under OSX 10.11 with all the trimmings, installed 5.0.1 + en-gb lang pack, no problem. Downloaded 5.0.2 from libreoffice.org, started OK. Added en-gb lang pack, no problem starting and adjusting to UK. Apropos user profile (as per suggestion), I zapped then it so LO could recreate it, also works. As existing profile was 65M in 1024 files and fresh profile is 1.6MB in 125 files I'll leave the new one as it holds no traces of legacy. Conclusion: more likely an issue with OSX installation. Closed bug (if that breaks any protocol, apologies, please amend).
Fred thanks a lot for the update. Setting to worksforme since we don't know what fixed things on your end. Might have still been LOs fault. Glad things are now working as expected.