alacritty: Fail to launch from Spotlight
Mac OSX Sierra 10.12.6 (16G1314)
Running the alacritty
binary works for me, running the .app
bundle from a terminal works, but running the .app
bundle from Spotlight does not.
I built alacritty
with: git clone https://github.com/jwilm/alacritty.git && cd alacritty && make app && cp -r target/release/osx/Alacritty.app /Applications/
- running
/Applications/Alacritty.app/Contents/MacOS/alacritty
from another terminal session works - running
open /Applications/Alacritty.app
from another terminal session works - running
Alacritty.app
by opening spotlight, searching for alacritty, and hitting enter fails silently - running
open /Applications/Alacritty.app
from another terminal session, pinning the opened version to the taskbar, closing the original instance, and then launching by clicking the taskbar pin fails silently
Is there any way to provide additional debug info? The best I’ve got is the following, which is the syslog output from attempting to launch alacritty through spotlight.
The IOFB failure line is probably a red herring, since it seems to be occurring regularly on my system regardless of alacritty.
default 19:09:51.701711 -0700 kernel [alacritty pid:4121 mux-aware] starting, non-mux-aware app count 0, switch-state 0 IG FBs 1 EG FBs 0:0 power-state 6 3D idle HDA idle
default 19:09:51.709483 -0700 kernel [alacritty pid:4121 non-mux-aware] starting, non-mux-aware app count 1, switch-state 0 IG FBs 1 EG FBs 0:0 power-state 6 3D idle HDA idle
default 19:09:51.709505 -0700 kernel PEG (usr IGD extdisp 0 capture 0 non-mux-aware app 1 ac 0)
default 19:09:51.709527 -0700 kernel -------> Switching from IGD to PEG
default 19:09:51.725709 -0700 kernel :::::::> PEG start powerup [0m 7.653s downtime]
default 19:09:52.128407 -0700 kernel *******> PEG powerup took: 0.403s
default 19:09:52.223467 -0700 kernel kPEEnableScreen 1
default 19:09:52.242026 -0700 kernel + IOAudioDevice[<private>]::protectedSetPowerState(1, <private>)
default 19:09:52.242034 -0700 kernel + IOAudioDevice[<private>]::initiatePowerStateChange(<private>) - current = 0 - pending = 1
default 19:09:52.243878 -0700 kernel +- IOAudioDevice[<private>]::flushAudioControls()
default 19:09:52.243897 -0700 kernel + IOAudioDevice[<private>]::protectedCompletePowerStateChange() - current = 0 - pending = 2
default 19:09:52.243902 -0700 kernel - IOAudioDevice[<private>]::protectedCompletePowerStateChange() - current = 2 - pending = 2 returns 0x0
default 19:09:52.243907 -0700 kernel + IOAudioDevice[<private>]::protectedCompletePowerStateChange() - current = 2 - pending = 2
default 19:09:52.243910 -0700 kernel - IOAudioDevice[<private>]::protectedCompletePowerStateChange() - current = 2 - pending = 2 returns 0x0
default 19:09:52.243912 -0700 kernel - IOAudioDevice[<private>]::initiatePowerStateChange(<private>) - current = 2 - pending = 2 returns 0x0
default 19:09:52.243914 -0700 kernel - IOAudioDevice[<private>]::protectedSetPowerState(1, <private>) returns 0x0
error 19:09:52.263661 -0700 WindowServer [ERROR] - Unable to find display pipe for IOFB service: 18439
default 19:09:52.316740 -0700 loginwindow token = 1000323
default 19:09:52.316909 -0700 loginwindow token = 1000324
default 19:09:52.320319 -0700 sharingd Display added (id 69733378)
default 19:09:52.327274 -0700 kernel =======> Switch completed, PEG active
default 19:09:52.420811 -0700 PowerChime PowerChime: 1736.966409: handleDisplayHardwareChanged ENTERED
default 19:09:52.487951 -0700 kernel FB0 Conection status change: Connected --> Disconnected
default 19:09:52.643145 -0700 kernel [alacritty pid 4121 mux-aware] exiting, non-mux-aware app count 1, runtime: 0:00:00.942
default 19:09:52.643351 -0700 kernel [alacritty pid 4121 non-mux-aware] exiting, non-mux-aware app count 0, runtime: 0:00:00.934
About this issue
- Original URL
- State: open
- Created 6 years ago
- Reactions: 5
- Comments: 35 (6 by maintainers)
Hello there,
I have the same problem, which started to appear when I added
tmux
to myalacritty.yml
Here is the relevant snippet:
This issue is not bugging me too much, but it’s indeed weird 👀 !
EDIT 3 month later: this is really terrible. I’ve stopped using tmux because of that
So, I spotted the problem:
My objective here is to make Alacritty always start Tmux connected to a session called
main
(and create it, if it doesn’t exist).For some reason,
new-session
doesn’t work in Spotlight and makes Alacritty crash immediately. Running from the terminal (e.g.open -a Alacritty
) works, however.Logs from Alacritty doesn’t provide anything useful about this crash, so flying blind here 😕