search

ShogunPanda / alfred-chrome

Alfred Chrome workflow
https://sw.cowtech.it/alfred-chrome
MIT License
74 stars 14 forks source link

Unable to run task! #5

Closed nicolinden closed 3 years ago

nicolinden commented 4 years ago

On Mac OS Big Sur when calling the workflow I get the error "Unable to run task!". The full error is:

Reason: Couldn't posix_spawn: error 85

The external script may not exist, or doesn't have execute (+x) permissions.

Related Workflow Info... Name: 'Alfred Chrome' Folder:/Users/nico/Dropbox/Applications/Alfred/Alfred.alfredpreferences/workflows/user.workflow.2B739210-964E-4692-8471-955FFA57E07C

Any Idea if there is a solution for this or on which files I might try to give permissions so that it works again? I already gave execute permission to the "alfred-chrome" file in this directory but that does not solve it. I haven't found any issues with other Alfred workflows on Big Sur.

Screenshot 2020-11-25 at 09 04 07
paradox2222 commented 4 years ago

I second this! It's one of my most used Alfred items as I bounce between personal and educator chrome profiles. Any help in this matter is greatly appreciated.

nickxma commented 4 years ago

Thrid it!

cocobriclot commented 3 years ago

Same problem here..

aaronmeder commented 3 years ago

Seems to be a general bug, at least since Big Sur. Would love to get it back :)

fredlemieux commented 3 years ago

Bummer :-(. Was looking forward to using this.

Seems to be a general bug, at least since Big Sur. Would love to get it back :)

kmthorsnes commented 3 years ago

Anyone who have other working solutions?

carsonjones commented 3 years ago

Super sad about this. Anyone found an alternative or have an idea of how to fix?

oguzgelal commented 3 years ago

I solved this by adding #!/bin/bash to the beginning of the script file

joseinazusa commented 3 years ago

The issue appears to be caused by the executable being compiled with older libraries. I compiled and repackaged the workflow. The spawn issue appears to be fixed. I forked the project so I could do a pull request. You can recompile alfredchrome.go. If you want to just get the workflow, you can go to the forked project. No code was changed, only recompiled with updated libraries.

nicolinden commented 3 years ago

The issue appears to be caused by the executable being compiled with older libraries. I compiled and repackaged the workflow. The spawn issue appears to be fixed. I forked the project so I could do a pull request. You can recompile alfredchrome.go. If you want to just get the workflow, you can go to the forked project. No code was changed, only recompiled with updated libraries.

Wow this seems to work indeed, I'll will keep trying it the coming days but I believe you are a life saver :-)

kmthorsnes commented 3 years ago

The issue appears to be caused by the executable being compiled with older libraries. I compiled and repackaged the workflow. The spawn issue appears to be fixed. I forked the project so I could do a pull request. You can recompile alfredchrome.go. If you want to just get the workflow, you can go to the forked project. No code was changed, only recompiled with updated libraries.

Thank you so much for this! This save my day! (and probably a lot of days ahead) :)

nicolinden commented 3 years ago

Problem is solved by the suggestion of @joseinazusa thanks all for looking into this, I am glad that this workflow works again!