Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't install on OS X El Capitan 10.11 #147

Closed
beeatriz opened this issue Jul 23, 2015 · 11 comments
Closed

Can't install on OS X El Capitan 10.11 #147

beeatriz opened this issue Jul 23, 2015 · 11 comments

Comments

@beeatriz
Copy link

Problem

On install, Prey throws the following line on OSX El Capitan 10.11

Humax-Living-Room:~ stewartdunn$ /usr/lib/prey/current/bin/prey config gui -f

-bash: /usr/lib/prey/current/bin/prey: No such file or directory

Humax-Living-Room:~ stewartdunn$

How it was detected.

User feedback.

References

https://secure.helpscout.net/conversation/104576542/25324/

@mauricioschneider
Copy link
Contributor

This is because Prey is not installed. The issue must be a different one.

@mauricioschneider
Copy link
Contributor

According to one of our users, the problem is related to a change in permissions in El Capitan. It appears that applications are unable to being installed under /usr/lib, which is the case of Prey. Instead, they should be installed under /usr/local/lib. I will have to look further into the issue.

@crockpotveggies
Copy link

+1

@lookfirst
Copy link

Yup, my console log is being filled up with error messages:

9/18/15 12:42:51.594 AM com.apple.xpc.launchd[1]: (com.prey.agent[68228]) Service could not initialize: Unable to set current working directory. error = 2: No such file or directory, path = /usr/lib/prey/current: 15A282a: xpcproxy + 12028 [1353][19011403-4854-3CCD-9FCF-49C36302EB40]: 0x2
9/18/15 12:42:51.594 AM com.apple.xpc.launchd[1]: (com.prey.agent) Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

@lookfirst
Copy link

Screenshot of install failure with 1.4.1: http://take.ms/1LcaW

@stewacide
Copy link

This is because of the new rootless / system integrity model. Look in /Library/SystemMigration/History/ and you'll find where Prey was moved on installing El Capitan: seems it hasn't been working for me for about a month, since I installed the public beta. Good thing my Macbook wasn't stolen in that time!!!

Hopefully the developers find a work around.

@wachunei
Copy link

wachunei commented Oct 1, 2015

screen shot 2015-10-01 at 12 40 40 pm

I don't know if this is related at all but MacTeX distribution had to [https://tug.org/mactex/UpdatingForElCapitan.pdf](release a guide) to link correctly the binaries used in software to the right paths in El Capitan. Could this be a way to workaround this by specifying binaries in a different location?

@mauricioschneider
Copy link
Contributor

The fix to this issue will be included in the release 1.4.2, which is about to be published.

@asadowski
Copy link

So is prey in /usr/local/lib now?

@mauricioschneider
Copy link
Contributor

Yes, it is.
On Oct 3, 2015 10:47 PM, "asadowski" [email protected] wrote:

So is prey in /usr/local/lib now?


Reply to this email directly or view it on GitHub
#147 (comment)
.

@escapone
Copy link

escapone commented Aug 1, 2016

it is impossible to install EL CAPITAN mac on prey, it sais outdated config file all time. Anyone a solution?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants