Posted on 01-19-2017 09:31 AM
I'm seeing an issue where SOME users who install Eclipse Neon 4.6.2 through Self Service get an error when launching the app.
You can’t open the application “Eclipse Neon 4.6.2.app” because PowerPC applications are no longer supported.
I built the package the same way I always have using Composer. I've never had problems until now. The weird part is that it's only happened on a handful of Macs AND if I delete the app from their Mac and then copy the working app from my Mac to theirs via ARD, the app I copied also gives the same error! The only way I've been able to get this version of Eclipse installed on the affected Macs is to download the .tar'd app from the eclipse website and expand it on their desktop and then copy it to /Applications. At that point it works. I can't find any information about how a definite intel Mac app could possibly identify itself as PPC other than possible file corruption, but if there was a problem with the package I have in self service, then it would happen on 100% of the Macs that install it - which isn't the case. So far, no other apps or Self Service packages appear to be affected.
Any ideas?
Solved! Go to Solution.
Posted on 01-19-2017 09:37 AM
5 seconds after I submitted this post, I discovered the problem. Somehow the /Applications/Eclipse Neon 4.6.2.app/Contents/MacOS/eclipse
file's permissions were set to rwxr-x---
and that made it only executable by admins and the owner (root). As soon as I did a chmod 755 to that file, it worked again. Very strange that this would happen in the first place!
Posted on 01-19-2017 09:37 AM
5 seconds after I submitted this post, I discovered the problem. Somehow the /Applications/Eclipse Neon 4.6.2.app/Contents/MacOS/eclipse
file's permissions were set to rwxr-x---
and that made it only executable by admins and the owner (root). As soon as I did a chmod 755 to that file, it worked again. Very strange that this would happen in the first place!