-
Notifications
You must be signed in to change notification settings - Fork 436
v1.9.2: EACCESS error on first install #102
Comments
+1 for the problem and for the work-around |
+1, for me at least, this seems to be an OS X 10.8 -> 10.9 (Mavericks) upgrade issue. |
Works fine for me on mavericks. What's the exact error you are seeing. |
Running PhantomJS via Karma:
Then load the console:
Then Karma is able to load PhantomJS:
Using |
If you run |
Yes, it gave me the same error as @sykopomp. Once I ran it once under sudo it runs fine as me. I confirmed I am the file's owner and it has permissions 755. This seems more like an OS X issue frankly. |
yeah, very strange. -- Dan On Tue, Dec 3, 2013 at 7:54 AM, Greg McGuire notifications@github.comwrote:
|
Running OSX 10.9 and have the same issue, launch with sudo and all is fine, thats an hour I'll never get back ;) |
Having this issue as well. Is there any workaround? I want to automate something and have it work OS-agnostic so we can't run sudo everytime :( |
+1 only works with sudo. |
The problem seems because it is installed in the not writable folder. Another workaround that works for me is having phantomjs installed in the writable folder, e.g.:
|
If I just run it once with sudo it works after that. I'm just running this after I install it: |
I don't have enough information to fix this so am going to close. If any of you can isolate the issue and propose a patch I'd happily review. |
I installed
phantomjs@1.9.2-0
globally withnpm
and got an error when I tried to run it as a user.Steps:
$ sudo npm install -g phantomjs@1.9.2-0
$ phantomjs
Results:
Notes
However, this works:
I can execute phantomjs normally from then on, without any problems.
I tested this
phantomjs@1.9.1-0
, and didn't get this error.The text was updated successfully, but these errors were encountered: