BusKill
Cannot open latest August MacOS release
Hello
I have error message when clicking on the app and therefore cannot start the application.
You can't open the application "buskill-1723151534" because it may be damaged or incomplete.
This is blocking testing fix for https://github.com/BusKill/buskill-app/issues/77
Here's the build in question
- https://github.com/BusKill/buskill-app/releases/tag/10136271901_mac
@samxplogs can you please run this from the command line and paste the output here?
open buskill-mac-1722214579-x86_64.dmg
The command line output should have more useful information (eg an error code) than the GUI popup window screenshot
I get an error when attempting to open this over ssh
maltfield@host ~ % wget https://github.com/BusKill/buskill-app/releases/download/10136271901_mac/buskill-mac-1722214579-x86_64.dmg
...
buskill-mac-1722214 100%[===================>] 27.34M 17.6MB/s in 1.6s
2024-09-29 22:28:44 (17.6 MB/s) - ‘buskill-mac-1722214579-x86_64.dmg’ saved [28668096/28668096]
maltfield@host ~ %
maltfield@host ~ % shasum --algorithm 256 buskill-mac-1722214579-x86_64.dmg
a908a1bdebd2c238c1edcc057485e19f1a083689ee801159bf13bdf3108b0813 buskill-mac-1722214579-x86_64.dmg
maltfield@host ~ %
maltfield@host ~ % open buskill-mac-1722214579-x86_64.dmg
maltfield@host ~ %
maltfield@host ~ % open -W /Volumes/buskill-*/buskill-*.app/Contents/MacOS/buskill
LSOpenURLsWithRole() failed with error -600 for the file /Volumes/buskill-1722214579/buskill-1722214579.app/Contents/MacOS/buskill.
maltfield@host ~ %
However, I cannot reproduce this when I execute these commands in the GUI terminal.
In my experience This LSOpenURLsWithRole() commonly translates to: you can't do that over the CLI; do it in the GUI.
Indeed, when I execute these commands in the GUI (well, inside the "Terminal" app in the GUI -- as opposed to my linux terminal's app on the MacMini via ssh), the app opens fine.
@samxplogs did you try this over ssh or some other CLI-only terminal by-chance? Can you please re-try with these commands in your Terminal App on macOS?
wget https://github.com/BusKill/buskill-app/releases/download/10136271901_mac/buskill-mac-1722214579-x86_64.dmg
shasum --algorithm 256 buskill-mac-1722214579-x86_64.dmg
open buskill-mac-1722214579-x86_64.dmg
open -W /Volumes/buskill-*/buskill-*.app/Contents/MacOS/buskill
Please paste the full output into a comment on this ticket.
See also
- https://apple.stackexchange.com/questions/453428/why-does-open-fail-with-lsopenurlswithrole-failed-with-error-610
user@host SDKs % grep -ir '\-610' *
...
#define procNotFound (-600) /* no eligible process with specified descriptor */
...
user@host SDKs %
See also
- https://web.archive.org/web/20191128225313/http://office.mvps.org/error/number.html#error-600
Error -600
An error occurred while launching. An unknown error (-600) occurred.This is the standard Macintosh error procNotFound. It is usually a response when trying to send an AppleEvent to a nonexistent target (or, more technically, when the mach port for AppleEvents for that target cannot be found). This would usually be generated by the toolbox, but Entourage generates that error in these cases:
(1) if Entourage cannot find the Alerts Daemon (usually found in the Office subfolder) to launch to show the "toasts" (notifications that new mail has been received),
(2) if Entourage is trying to open a document and cannot find the Finder application (this is usually when you're opening Entourage on a system that is too old, so probably not your case), and
(3) in some generic process code that tracks whether other processes (e.g., the Database Daemon) are running.
- It seems the shasum does not match
% shasum --algorithm 256 buskill-mac-1722214579-x86_64.dmg
a908a1bdebd2c238c1edcc057485e19f1a083689ee801159bf13bdf3108b0813 buskill-mac-1722214579-x86_64.dmg
- open buskill-mac-1722214579-x86_64.dmg
This mount right away the .dmg image and I have the exact same output as stated on top of this ticket.
- open -W /Volumes/buskill-/buskill-.app/Contents/MacOS/buskill
The application cannot be opened for an unexpected reason, error=Error Domain=NSOSStatusErrorDomain Code=-128 "userCanceledErr" UserInfo={_LSLine=4129, _LSFunction=_LSOpenStuffCallLocal}
@samxplogs did you obtain the file with this command?
wget https://github.com/BusKill/buskill-app/releases/download/10136271901_mac/buskill-mac-1722214579-x86_64.dmg
because if you get a different file than I get when I execute that command, we have a much bigger problem...
Apparently the problem still exists.
Anyone got this working on macOs 26 currently?
I now got a local build working after a lots of fixing wrong paths, versions etc. There were a lot of problems and unfortunately the GUI is still broken..
I dont know how useful this is going to prove. But I pushed it to a branch here: https://github.com/hexxone/buskill-app/tree/fix/mac-arm
Maybe someone can take a look and get it working. I'll be searching for other & easier ways to accomplish this... I dont really need a GUI, just an easy way to enable & disable this, there should be a way to do this with 2 scripts and some background "screen" task as well I assume...
@hexxone this bug should only be present on the prerelease (and I was never able to reproduce it). Do you have the same issue with the latest release v0.7.0
- https://github.com/BusKill/buskill-app/releases/tag/v0.7.0
I dont really need a GUI
Also, the app is both a GUI and a CLI. Have you tried executing it in CLI mode?
- https://docs.buskill.in/buskill-app/en/stable/software_usr/cli.html
If you'd like to help identify and squash this bug, can you please share your buskill debug log?
- https://docs.buskill.in/buskill-app/en/stable/support.html#debug-log
Hey there, thank you for the quick reply!
Do you have the same issue with the latest release v0.7.0
Fortunately I dont get the same error, but I also cannot start the 0.7. Version because it seems like it is not signed properly.
And I think with the last few updates Apple kept increasing restrictions, so you can basically no longer run unsigned apps or have to sign them yourself..
bug should only be present on the prerelease
P.S. regarding that, the "BUG" is actually pretty easy to explain:
Several last "macOS" Release files (E.g.) buskill-mac-1723151534-x86_64.dmg
Only has a size of 96.1 KB . It should be around 20 - 50 MB tho.
If you look at it, you can actually unzip the files and see inside of the ".App" there are NO binaries to execute at all.
So there is probably something wrong in the build step already.
I also cannot start the 0.7. Version because it seems like it is not signed properly.
We sign our apps with PGP, which we consider safer and freer (both as in speech and as in beer) to apple signatures.
And I think with the last few updates Apple kept increasing restrictions, so you can basically no longer run unsigned apps or have to sign them yourself..
Do you have a link with more information about this claim (official apple release info/docs or article saying this is no longer possible)? In the past, you just had to click somewhere in the Security Settings to confirm that you wanted to open the app. I would be incredibly surprised if they removed this process entirely...
And I think with the last few updates Apple kept increasing restrictions, so you can basically no longer run unsigned apps or have to sign them yourself..
Do you have a link with more information about this claim (official apple release info/docs or article saying this is no longer possible)? In the past, you just had to click somewhere in the Security Settings to confirm that you wanted to open the app. I would be incredibly surprised if they removed this process entirely...
Hey there, I just remembered that I had some issues approximately one year ago with the 15.1 Update, where they removed the ability to run unsigned apps easily: https://hackaday.com/2024/11/01/apple-forces-the-signing-of-applications-in-macos-sequoia-15-1/
After trying again now, I actually got the version 0.7.0 working, I just had to go to System "Privacy Settings" and explicitly allow Buskill after opening it once with above error. I guess the option wasnt showing up there when I tried to run the App directly from inside of the .dmg file, without first moving it into "Applications"... my bad 😅 The error message also didnt indicate that..