I installed 4.2.0beta1 on OS X and upon starting it I get the followin pop-up window:
"LibreOfficeDev.app" is damaged and can't be opened. You should move it to the Trash.
I remember seeing that with 4.2.0alpha, but then I reinstalled it and it worked. I tried deleting, reinstalling several times, but beta1 does not start properly on my system.
FYI, I have OS X 10.9.
could you please try the latest nightly? Works for me on 10.9.
And re-open this bug should that not be the case.
Yes, it works.
But it took a lot of time to open the first time, maybe because it is alpha, I do not know. The icon just jumped down below. Then I killed it and it again took some time but it finally prompted to allow running it as it was downloaded from Internet.
All subsequent starts were fast.
Also, this is for another bug report, the "developer is not identified" so one must visit the Security settings on OS X 10.9 to allow running it.
Yes, stable releases should be properly signed I think so won’t be an issue then.
Will beta1 be respun with this fix? Otherwise this is shoud remain a blocker for OSX.
Tried LO 4.2.0 Beta 2 on my system and the problem is back, same messagge.
This is a blocker for beta2, I guess.
I am also getting that error message on OS X 10.9.
(In reply to comment #7)
> I am also getting that error message on OS X 10.9.
Should have said: using Beta2.
Adding whiteboard tag for repro status.
builds for beta2 have been replaced by unsigned ones, this will avoid the "is damaged" problem, but to run it you have to use open from the context-menu (instead of double-clicking) to get the option to open it despite not being signed.
I'm having the same problem with the RC1: "damaged and can't be opened". OS X 10.9
My problem was with the 32-bit version, which is what the download page suggested and what I have been using for previous LO versions. When I tried the 64-bit version of 188.8.131.52, it opened as it should.
updated the title for 4.2RC2 and 32-bit
Should be fixed in RC3 - can you try from: http://dev-builds.libreoffice.org/pre-releases/mac/x86/
Can't help testing since I never ran into the issue. Both 32bit and 64bit OSX builds of 4.2RC3 do mount and install as expected here.
It seems to work now, cannot reproduce anymore.
I must unfortunately reopen this bug - this happened again with 4.4.1RC1, it must be a regression of some kind!
Please do check, this is a blocker for OSX.
The only difference with the primary report is that now it is a 64-bit build (as there are no 32-bit OS X builds anymore).
Should I change the version number (to 4.4.1RC1) and hardware (to 64-bit) in the bug report?
(In reply to miles from comment #17)
> I must unfortunately reopen this bug - this happened again with 4.4.1RC1, it
> must be a regression of some kind!
I don't see a specific fix mentioned for this bug in the comments below, and this was never marked as independently confirmed (Although perhaps Jean in comment 7 was suggesting as much?), so correct status should be UNCONFIRMED.
> Please do check, this is a blocker for OSX.
> The only difference with the primary report is that now it is a 64-bit build
> (as there are no 32-bit OS X builds anymore).
> Should I change the version number (to 4.4.1RC1) and hardware (to 64-bit) in
> the bug report?
If it's exactly the same issue, then potentially this bug report will be helpful (especially as existing commenters might be helpful for repro). If several variables have changed (architecture, etc..), then please file a new bug report.
Well, Robinson, I do not know if it is the same bug from the developer's standpoint, it sure looks the same bug from the user's one (the error message is exactly the same and renders the installed LO441RC1 unusable).
(In reply to miles from comment #19)
> Well, Robinson, I do not know if it is the same bug from the developer's
> standpoint, it sure looks the same bug from the user's one (the error
> message is exactly the same and renders the installed LO441RC1 unusable).
Sounds good -- let's go with this bug report :-)
Thankfully for us, the total number of combinations of OSX hardware is quite limited, so hopefully we can get repro on this issue.
Miles: What version of OSX are you currently running?
(Updating hardware and Summary)
I currently use Yosemite (10.10.2).
Have you tried resetting the user profile?
Yes, even after deleting/renaming the existing profile it still does not want to start.
this bug was about 32-bit 4.2 builds and now it suddenly talks about 64-bit 3.3 builds? this is very confusing, please file a *new* bug!
sigh... could we *please* have a check in bugzilla that random users are not allowed to re-open bugs resolved years ago?
Random user? Which country do you live in so I can sue you?
This bug report is reopened because the symptoms are the same even if the OSX architecture changed - it is believed for now that this is a regression from the first bug.
Since some commenters have mentioned it has been fixed for 4.2 it gives an opportunity to find that fix and see if with 4.4 there were some unwanted changes in that part of code that could trigger a regression.
apologies for any excessive grumpiness in my previous comment - it was caused by looking at bugzilla before breakfast, which is clearly something i should not be doing.
(if you re-open a 4.2 most-annoying bug like this one then a mail is sent to the developer mailing list)
probably the 4.4 issue is about the known digital signature problem that came up not via any change in LO but by OS X 10.9.5 suddenly changing the rules; that should be fixed for 184.108.40.206, see bug 84352.