Can't run Monkey on Mac OS X Mavericks
Monkey Forums/Monkey Bug Reports/Can't run Monkey on Mac OS X Mavericks
| ||
| HI there, It's been a while since I've had time to work with Monkey. The last version I used is 75d which DID work, but trying it again, I click on the Monkey icon, the system tray moves a couple of pixels as though it's about to add the icon, but then goes back to normal. Monkey doesn't run. In the Console, it creates the following error log: 08/05/14 19:30:57,330 com.apple.launchd.peruser.501[155]: ([0x0-0x10e10e].Monkey[2180]) Job failed to exec(3) for weird reason: 13 08/05/14 19:30:57,332 Finder[169]: 8837325: Attempting to SIGCONT to pid #2180 failed, with errno=#3, or the process failed to actually start 08/05/14 19:30:57,333 loginwindow[63]: ERROR | -[Application setAppContext:] | Unable to get PID for context [0,1106190] 08/05/14 19:30:57,333 Dock[167]: no information back from LS about running process LSASN:{hi=0x0;lo=0x10e10e} 08/05/14 19:30:57,343 Finder[169]: 8837325: Attempting to SIGCONT to pid #2180 failed, with errno=#3, or the process failed to actually start The last error line is repeated at least 100 times(!). I decided to download the latest (77f), but the same problem occurs. I can't seem to find any details about this in the forum. (Especially the "weird reason" in the log!). I'm using Mac OS X 10.9.2 on an iMac Late 2009. I just tried it on MacBook Pro Late 2011 too (same OS version), same problem. Any thoughts? EDIT: It's not just Monkey (or more specifically, Ted) that doesn't want to run... mserver_macos doesn't run for the same reason (same sort of errors). makedocs_macos says "permission denied" when trying to run. / Boz. |
| ||
| It may be the 'unzip' app you're using - try unzipping with the 'official' mac os unzip tool, not a 3rd party one. |
| ||
| Yep, that was exactly it! Keka was being used to unzip the latest versions, and that was causing the problem (just used the built-in unarchiver instead). I had only recently read about this being a problem for another tool I was using, too. Heads-up Mac users: Use Mac OS's built-in unzipper! Thanks Mark! |
   |