Bitbar: Couldn`t posix_spawn: error 8

Created on 26 Jan 2016  ·  12Comments  ·  Source: matryer/bitbar

And 2 yellow triagle in status bar

Most helpful comment

This will also happen if you're missing an interpreter at the head of the file (I.E. #!/bin/bash or #!/usr/bin/ruby)

All 12 comments

If you downloaded the script by Download Linked File As, it will download the HTML... you need to download the script by clicking on the Get Plugin button and copy and pasting the code on a text editor like Atom and saving it to the folder for your plugins.

I just tried this because I had gotten the same error and that is the result.

Thanks bro. Thats works!
))

On 27 янв. 2016 г., at 23:26, Gilbert Palau [email protected] wrote:

If you downloaded the script by Download Linked File As, it will download the HTML... you need to download the script by clicking on the Get Plugin button and copy and pasting the code on a text editor like Atom and saving it to the folder for your plugins.

I just tried this because I had gotten the same error and that is the result.


Reply to this email directly or view it on GitHub https://github.com/matryer/bitbar/issues/196#issuecomment-175861650.

yw

Also check your system load, if it's too high you might not be able to launch a legitimately downloaded plugin.

This will also happen if you're missing an interpreter at the head of the file (I.E. #!/bin/bash or #!/usr/bin/ruby)

hi, i've installed the slack plugin and it seems to work fine once the python version problem solved on OSX but it keeps showing a yellow triangle saying posix_spawn error 8. I have a shebang .
any idea on how to investigate ?

Is the plugin marked as executable?

yes it is, i solved (more like a workaround) it using a simple bash wrapper. so i can have a slack notification in my bar
EDIT
#!/bin/sh
echo $(/path/to/python/bin /path/to/plugin.py)

i cannot click the icon once launched though. i have to install some other plugin so i can click refresh when needed

@gingerbeardman Did you manage to make it work ?

This is becoming a very serious problem for me. I was relying on bitbar and now I can't use it at all.

I didn't download my script, I wrote it by hand, and it does have the bash interpreter specified as the first line. In fact, it seems completely random as to whether I get this error or not. A script that has worked fine for years suddenly gets this error when I change it, but when I revert the changes back, the error doesn't go away.

It appears related to trying to put a duration in the script name... like scriptName.2s.sh instead of scriptName.sh. This causes the problem to start. However, renaming it back doesn't solve the problem, neither does rebooting my computer or reinstalling Bitbar.

Today it appears Bitbar doesn't work at all for me, it only ever gives this error no matter what I do, which is frustrating, as up until yesterday I was relying on it. I put in several hours getting everything right with my script yesterday, only to have bitbar fail on me completely today with this unexplained error.

For anyone finding this in the future with the same problem, I found a solution not yet mentioned:

xattr -d com.apple.quarantine /path/to/script.sh

Fill in the correct script path for /path/to/script.sh and enter this in terminal. It's OS X's "helpful" quarantine system preventing the script from running. This fixed it for me.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

JayBrown picture JayBrown  ·  6Comments

JayBrown picture JayBrown  ·  9Comments

dzg picture dzg  ·  4Comments

javray picture javray  ·  11Comments

reteps picture reteps  ·  5Comments