Fail to launch from Spotlight #1388
Comments
|
Which
All of them except the one from assets work for me (and that's as intended as it isn't a complete app yet, just the skeleton). Which one do you find? |
|
@simmel I just confirmed: it is finding the |
|
And you can't launch it?
Tried `rm -rf /Applications/Alacritty.app && make clean install` ?
…On Thu, 2018-06-21 at 17:44:54 -0700, Kevin James wrote:
@simmel I just confirmed: it is finding the `/Applications/Alacritty.app` one. As far as I see, neither `release` nor `assets` show up in my Spotlight results.
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#1388 (comment)
|
|
@simmel as far as I can tell, that is behaving exactly the same. Good find on the |
|
Have you tried to find it in Finder, hold shift, right-click on Alacritty.app and click Open? This circumvents the thing that requires applications to be signed. |
|
Looks like its control-click rather than shift-click but thanks for making me aware of that option, TIL! No such luck, no behavior change. |
|
I'm out of ideas then. Maybe someone else will chime in.
…On Thu, 2018-06-28 at 11:09:01 -0700, Kevin James wrote:
Looks like its [control-click rather than shift-click](https://support.apple.com/kb/ph25088?locale=en_US) but thanks for making me aware of that option, TIL!
No such luck, no behavior change.
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#1388 (comment)
|
|
@TheKevJames have you tried with LTO disabled? I had an issue (I haven't looked into further) where an LTO-enabled, rust 1.27 build of |
|
@ijl thanks for the suggestion. Unfortunately, that doesn't seem to be the issue. Does anyone know if there's some way to capture more debug information? I feel like we're throwing random darts at this point. |
|
@TheKevJames Hey, after debugging a different issue I've noticed that Alacritty will crash when it can't log its output, to fix that issue this PR has been opened. Would you mind giving it a shot to test if this fixes your problem? |
|
Closing this since #1459 should have fixed this. If it is not the case, please let me know and I will re-open. |
|
@chrisduerr seems I am getting the exact same behavior. I ran: The results are as described above (eg. only opening from another terminal seems to work). I do have one additional log message now which I did not see before! Note that the above only occurs when running the binary directly, but not when running |
|
I thought this issue might be caused by no stdout/stderr being available when running the app. Thanks for getting back on this issue, I'm going to re-open this for now. |
|
At least for me, running the actual binary path gets me: Changing the |
|
@jmoses-ds Please see the notice in the README.md about this. That's one of the reasons why we provide the |
|
Sigh. I'll even pretend I don't clearly remember reading that now that you've mentioned it. |
|
Just to be clear: my original issue (which still persists) was using the vanilla |
|
I'm also having this issue, I don't know how I can help debugging this |
Can you please:
Thank you for trying to solve the issue @gagbo! |
|
I'm using Alfred, but I suppose it's just to check that the correct executable is chosen.
I'm accessing the first each time (the one in Cmd + Enter goes to the /Applications folder, but I'm not sure what the Cmd+left click is supposed to do, because nothing happens. Edit : in case the goal was to see the contents of the |
|
Just to be complete : |
|
cmd+click on the title just to get the path where Alacritty is but you already see that in Alfred. Well, I don't know anything else. But just to verify:
|
|
|
Try to remove Alacritty.app and make install and copy Alacritty from the dmg again.
…On Mon, 6 May 2019, at 16:02, Gerry Agbobada wrote:
* `open /Applications/Alacritty.app` works (and is much better than my `/Applications/Alacritty.app/Contents/MacOS/alacritty; ^Z; bg; disown %1` that I used before
* The "app install" thing did not appear when I tried to use it, but I think the app is authorized (I Ctrl-clicked opened the app in /Applications and nothing appeared, my security settings are as follows)
Capture d’écran 2019-05-06 à 15 57 40 <https://user-images.githubusercontent.com/10496163/57230234-298ad080-7018-11e9-823f-1a09b3324369.png>
- Doublie clicking in finder doesn't work. Still very silently :(
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#1388 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABOU7DWS5CQB6D4FS56LN3PUA25FANCNFSM4FGFFXGA>.
|
|
I tried, same behaviour. I used syslog to check what happened, and I think I'll to find a more intrusive logging method, as all I have is : EDIT : I also discovered that after hiding the window (using |
|
I'm facing the exact same behavior. MacOS Catalina 10.15.7.
My error is this one:
|
|
Have you launched it through Finder first using right click -> open? |
|
Thanks for your reply @chrisduerr Yes, via Finder |
|
Based on a suggestion in #3880, after signing the app, the error is different:
Pattern is still the same |
|
Update from my case: I just removed my I'll share here once I discover the root cause, since it might help others 👍 |
|
So, I spotted the problem: shell:
program: /usr/local/bin/fish
args:
- --command="/usr/local/bin/tmux" # This works!
- --command="/usr/local/bin/tmux new-session -A -s main" # This doesn't work!My objective here is to make Alacritty always start Tmux connected to a session called For some reason, Logs from Alacritty doesn't provide anything useful about this crash, so flying blind here 😕 |
|
Ideas are welcome here ☝️🙂 Since the command works fine running from another shell, I suppose it might be related to how Alacritty start the shell internally |
|
Hello there, I have the same problem, which started to appear when I added Here is the relevant snippet: shell:
program: /bin/bash
args:
- -l
- -c
- "tmux"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 |
Solution is here: #5419 (comment) |
|
Ohh, thank you very much!
Le ven. 15 juil. 2022 à 19:58, UFO-101 ***@***.***> a écrit :
… Hello there,
I have the same problem, which started to appear when I added tmux to my
alacritty.yml
Here is the relevant snippet:
shell:
program: /bin/bash
args:
- -l
- -c
- "tmux"
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
Solution is here: #5419 (comment)
<#5419 (comment)>
—
Reply to this email directly, view it on GitHub
<#1388 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADKG2SUAPVELA5WQ4B7QYPTVUGRFNANCNFSM4FGFFXGA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Running the
alacrittybinary works for me, running the.appbundle from a terminal works, but running the.appbundle from Spotlight does not.I built
alacrittywith:git clone https://github.com/jwilm/alacritty.git && cd alacritty && make app && cp -r target/release/osx/Alacritty.app /Applications//Applications/Alacritty.app/Contents/MacOS/alacrittyfrom another terminal session worksopen /Applications/Alacritty.appfrom another terminal session worksAlacritty.appby opening spotlight, searching for alacritty, and hitting enter fails silentlyopen /Applications/Alacritty.appfrom another terminal session, pinning the opened version to the taskbar, closing the original instance, and then launching by clicking the taskbar pin fails silentlyIs 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.
The text was updated successfully, but these errors were encountered: