xbar: launch path not accessible

Just updated to the latest version and I’m getting ‘launch path not accessible’ errors in my status bar. There is one for each file in my plugins folder. These files are not scripts, but are included and used by the other plugins.

Previously, Bitbar just ignored these files (maybe because they didn’t have the {name}.{time}.{ext}) format?)

Is there a way for bitbar to ignore these files? Or can we put them in a sub-dir that will be ignored?

Thanks

About this issue

  • Original URL
  • State: closed
  • Created 8 years ago
  • Comments: 15 (6 by maintainers)

Most upvoted comments

@jemus42 Try chmod +x plugin_name

chmoding the script does it for me (:

Not entirely related, but wanted to post this in case it helps anyone with a similar issue. I got the same error “launch path not accessible” on a fresh install on Sierra. I searched and only found this thread. By default my plugin folder was my Documents folder. Sierra moves Documents out to iCloud which makes them inaccessible to some programs. My solution was to change my Plugin folder to a non iCloud folder.

To be specific… e.g.

chmod +x /path/to/your-script.30s.sh

edit: sorry @BradleyJohnson, I didn’t scroll up. I see you posted the same answer a while ago.

I still have this issue, my bitbar plugins dir is ~/bitbar, so I don’t think iCloud is an issue. I can’t get any plugin to work 😦