I had the same problem on Mountain Lion. I was able to resolve it by temporarily changing the Gate Keeper security settings under 'Security&Privacy' in the system preferences to 'Anywhere'. After that you can open the JabRef app. When you have opened it once, you can change the security settings back and you'll still be able to open the app
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
That changed the behavior but didn't fix the problem (I'm also on Mountain Lion). Once I did that, it allowed me to double click, but the app didn't launch, and when I check the system log I found:
1/3/13 8:07:17.237 AM com.apple.launchd.peruser.501[164]: ([0x0-0x30ac0a9].JabRef[49918]) Job failed to exec(3) for weird reason: 13
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The reason was the non-executable flag of the JavaApplicationStub. One has to do a chmod 755 JavaApplicationStub, then it works. Just in case someone finds this bug report using google. Fixed in JabRef 2.9.2.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Just downloaded Jabref 2.9.2: still have the problem that this irritating error message appears. (on mountain lion)
After finding this thread, I set my security setting to anywhere and now I can start it.
So, this should probably be regarded as semi-fixed.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Actually, if Security & Privacy settings is set to "Allow applications downloaded from: Mac App Store and identified developers" and in case the Jabref developers could not be identified, I would expect a message like "Could not identify developers" and not "Jabref.app is damaged and can't be opened." I guess Apple is confusing things. Are the Jabref developers supposed to be identifiable by Apple? In that case maybe the wrong signature is being used?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well, my take is: the problem is the wrong error message - and I have seen the correct one: as far as I remember s.th. like security settings forbid to execute this , because developers cannot be identified - in some case.
Then, it is perfectly fine, because then one knows what to do..
But with this error message I first downloaded and tried it like three times and searched for a solution on the internet, until I found out.
As ML usually gives the appropriate error message, I assume that there is a weird interaction between ML security settings and JabRef (perhaps because it has problems with the certificate (if it is signed) and if this is not activated, it does not run into this problem..
I do not know, I can only say that with security setting ML is reacting differently to Jabref than to other systems..
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think, this still applies to the recent development version. We didn't release a Mac OS X binary for JabRef 2.11 as JabRef 2.11 does not start there. The jar itself, however, works.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I believe this is a case of a bad error message: what’s really happening is the security settings aren’t allowing it to run. If you go into Preferences and temporarily allow unsigned binaries to run, it ought to work. Worth checking, anyway…
I think, this still applies to the recent development version. We didn't release a Mac OS X binary for JabRef 2.11 as JabRef 2.11 does not start there. The jar itself, however, works.
Dr. Alan Grossfield
Associate Professor
Department of Biochemistry and Biophysics
University of Rochester Medical Center
610 Elmwood Ave, Box 712
Rochester, NY 14642
Phone: 585 276 4193 http://membrane.urmc.rochester.edu
I had the same problem on Mountain Lion. I was able to resolve it by temporarily changing the Gate Keeper security settings under 'Security&Privacy' in the system preferences to 'Anywhere'. After that you can open the JabRef app. When you have opened it once, you can change the security settings back and you'll still be able to open the app
Hi,
That changed the behavior but didn't fix the problem (I'm also on Mountain Lion). Once I did that, it allowed me to double click, but the app didn't launch, and when I check the system log I found:
1/3/13 8:07:17.237 AM com.apple.launchd.peruser.501[164]: ([0x0-0x30ac0a9].JabRef[49918]) Job failed to exec(3) for weird reason: 13
The reason was the non-executable flag of the JavaApplicationStub. One has to do a chmod 755 JavaApplicationStub, then it works. Just in case someone finds this bug report using google. Fixed in JabRef 2.9.2.
I just downloaded v 2.9.2, and that works correctly for me. So, I guess this bug can be closed.
Just downloaded Jabref 2.9.2: still have the problem that this irritating error message appears. (on mountain lion)
After finding this thread, I set my security setting to anywhere and now I can start it.
So, this should probably be regarded as semi-fixed.
Indeed, the original problem remains, as does the workaround. I'd like to reopen this bug, but don't see how.
I assume, the same thing happens with JabRef 2.10 beta?
Yes, 2.10b has the same problem.
Actually, if Security & Privacy settings is set to "Allow applications downloaded from: Mac App Store and identified developers" and in case the Jabref developers could not be identified, I would expect a message like "Could not identify developers" and not "Jabref.app is damaged and can't be opened." I guess Apple is confusing things. Are the Jabref developers supposed to be identifiable by Apple? In that case maybe the wrong signature is being used?
Well, my take is: the problem is the wrong error message - and I have seen the correct one: as far as I remember s.th. like security settings forbid to execute this , because developers cannot be identified - in some case.
Then, it is perfectly fine, because then one knows what to do..
But with this error message I first downloaded and tried it like three times and searched for a solution on the internet, until I found out.
As ML usually gives the appropriate error message, I assume that there is a weird interaction between ML security settings and JabRef (perhaps because it has problems with the certificate (if it is signed) and if this is not activated, it does not run into this problem..
I do not know, I can only say that with security setting ML is reacting differently to Jabref than to other systems..
Does this still apply to JabRef 2.11 and the newest development version?
I think, this still applies to the recent development version. We didn't release a Mac OS X binary for JabRef 2.11 as JabRef 2.11 does not start there. The jar itself, however, works.
I believe this is a case of a bad error message: what’s really happening is the security settings aren’t allowing it to run. If you go into Preferences and temporarily allow unsigned binaries to run, it ought to work. Worth checking, anyway…
Alan
Dr. Alan Grossfield
Associate Professor
Department of Biochemistry and Biophysics
University of Rochester Medical Center
610 Elmwood Ave, Box 712
Rochester, NY 14642
Phone: 585 276 4193
http://membrane.urmc.rochester.edu
Related
Bugs: #1099