alacritty: Alacritty Doesn't Open on MacOS Big Sur
MacOS: 11.0 Beta (20A4299v) Alacritty Version: fresh 0.4.3 from the Releases page.
Issue:
Clicking on the application icon and launching from Spotlight does nothing.
open -a Alacritty
: LSOpenURLsWithRole() failed for the application /Applications/Alacritty.app with error -1.
I am able to Show Package Contents and launch the binary directly, so creating a dock shortcut works for now. Most of my other apps work so I wonder if there’s something that needs to be updated here?
This is a very low priority issue since this is such an early beta but I’m just creating it to track the progress. Thanks!
Similar to #943
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 7
- Comments: 30 (7 by maintainers)
@mauricioklein I install Alacritty through Homebrew
brew install --cask alacritty --no-quarantine
, but here are two options that might help you:sudo codesign -f -s - "/Applications/Alacritty.app/Contents/MacOS/alacritty"
(ad-hoc signs the executable with your user,-f
= force-replaces any bad signature,-s -
= ad-hoc signs)and/or
xattr -d com.apple.quarantine /Applications/Alacritty.app
(tells macOS not to warn you about lack of signature, etc.)touch info.plist
does not change the error message fromopen -a Alacritty
or the behavior when double-clicked from Finder.Thanks for your help!
interesting, did you upgrade your command line tools also? I had to do it manually to fix brew https://developer.apple.com/download/more
Alacritty.dmg.zip
for whatever reason, most things on Big Sur report the version as 10.16 (e.g
sw_vers -productVersion
), changingMACOSX_DEPLOYMENT_TARGET
to 10.16 and building made it work for me.I’ve the same issue on Big Sur 11.3.1 This
sudo xattr -r -d com.apple.quarantine ./target/release/osx/Alacritty.app
solved an issue.@mcansh ahh. yes, it works after I fixed brew by
sudo xcode-select --switch /Applications/Xcode-beta.app
👍Thanks @mcansh , I usually build by
make clean app
, I missed thebinary
! Will try later, cheersThanks for finding that out. In general, I’d like to wait for apple to release their new macOS, so we can update
MACOSX_DEPLOYMENT_TARGET
to a proper version based off the system we’re compiling to. I feel like it’s a bit related to their new ARM support to some point, so that’s why different deployment target should be used?Thanks @4cm4k1 !
I had Alacritty installed via Homebrew before and was having the same problem as now.
None of the commands above worked, unfortunately 😕
I’m, however, getting a different error now:
you can check my conf of tmux https://github.com/imjma/dotfiles/blob/master/tmux.conf#L126
Since macOS 11 is still so fresh, the best bet is probably to give it some time and see if that helps with things. Hopefully they’ll figure it out.