New install of Zed will not Launch #9805
Labels
defect
[core label]
needs info / awaiting response
Issue that needs more information from the user
panic / crash
[core label]
Comments
AurorahHarmony
added
admin read
AurorahHarmony
changed the title
|
When you launch it from .dmg directly, do you see anything in the terminal? |
|
Nothing happens whatsoever. I get the warning that The only thing i'm able see is that it fails notarization in Console |
|
Could you try to run a Preview release instead? E.g. from https://zed.dev/api/releases/preview/0.128.3/Zed.dmg |
JosephTLyons
added
needs info / awaiting response
|
I have tried the Preview Release located here: https://zed.dev/api/releases/preview/0.128.3/Zed-aarch64.dmg as well as the one linked above (https://zed.dev/api/releases/preview/0.128.3/Zed.dmg). Unfortunately the same thing occurs for both, with neither opening. Screen.Recording.720p.2024-03-27.at.11.42.09.AM.movScreen.Recording.720p.2024-03-27.at.11.44.01.AM.mov |
|
Hi, experiencing the same for: |
|
I also have the same problem， |
|
What about older releases like: https://zed.dev/api/releases/stable/0.124.7/Zed.dmg ? Can you run that successfully? |
I can successfully run using the old version of 0.124.7 😄 |
|
Thanks @2577873863, |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This version doesn't work for me either
I followed the steps to open Zed here from within the Applications folder using Running Zed once with I'm using a fresh out of the box MacBook. It might be good looking into why Zed doesn't always launch the first time, and gets stuck with permission issues after that. |
|
I'm gonna keep this open as a tracking issue. We know that using @AurorahHarmony thank you for a thorough report! Is that backtrace from 0.127.4 or did you download a different version prior to trying with sudo? |
|
@osiewicz Unfortunately I forgot to capture the specific version number when I managed to get Zed to launch using sudo. After doing that once, multiple versions seem to launch just fine. Through process of deduction, I can tell you the only two versions I downloaded on that date are Running while running the same command on 0.128.3 yields a different output: TLDR, i'm 99% sure the exact version for the traces in my previous comment was 0.124.7 |
|
After having a quick look at the stack trace, and the code it refers to I've been able to get the same permission error again by doing the following things on version
To fix, launch with Sudo. I'm wondering if there may need to be something that requests elevation if this fails due to a permission error. https:/zed-industries/zed/blob/v0.128.3/crates/zed/src/main.rs#L467 |
|
Yeah, that sounds like a permission problem then @AurorahHarmony ; thank you so much for the stack traces and thorough investigation, I'll take look at it as soon as possible. |
|
Any updates? |
|
As of #10326 we should show these errors on boot. Is that working for you? We don’t yet have a way to automatically fix the permissions, but in the meantime the suggestions from #9036 (comment) should work. |
Yes, thank you. After updating and manually removing the permissions to get it back to its original state, it no longer silently fails to launch, and I get the expected visual feedback
Unfortunately the fix you linked does not fix the issue in my circumstance: (base) aurorah@AurorahZephyrus ~ % ls -la .cache
total 0
drwxr-xr-x@ 4 aurorah staff 128 30 Mar 12:13 .
drwxr-x---+ 51 aurorah staff 1632 2 May 19:05 ..
drwxr-xr-x@ 3 aurorah staff 96 22 Mar 23:00 cycles
drwx------ 2 aurorah staff 64 30 Mar 12:13 zed
(base) aurorah@AurorahZephyrus ~ % sudo chown -R $(whoami):staff ~/.cache
(base) aurorah@AurorahZephyrus ~ % ls -la .cache
total 0
drwxr-xr-x@ 4 aurorah staff 128 30 Mar 12:13 .
drwxr-x---+ 51 aurorah staff 1632 2 May 19:05 ..
drwxr-xr-x@ 3 aurorah staff 96 22 Mar 23:00 cycles
drwx------ 2 aurorah staff 64 30 Mar 12:13 zedBut my initial fix of running |
|
Looks like your |
|
for me, the sudo /Application//zed launched it and then install on CLI got things to run smooth onwards |
|
For me this works - #9805 (comment). Thank you |
|
@hello1101n What version of macOS are you running? Currently we only support Catalina and above |
|
For what it's worth, this is the output I received in terminal when running it by |
|
@seantiz You should probably not run Zed as root, but instead fix the permission errors we're encountering. It looks like that error is probably an error loading themes - can you post the output of |
I'm not sure I understand what you mean by both as user and root but I assumed that means run the
please let me know if there's anymore feedback I can post |
|
It looks like the problem here is that you have a bunch of files owned by root in your home directory. You should be able to fix this with And then Zed should boot fine without sudo again. |
Ok yes, thanks for that. I'd already gotten around the issue of installing it, but at least now i've fixed the problem of every directory being open to root access. Thanks again. my copy of Zed is still unable to install extensions so either that saves to another directory outside of config or cache, or it it's a connection problem. |
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Check for existing issues
Describe the bug / provide steps to reproduce it
Download any version of Zed and install it by dragging it to the application folder. Then try to launch it. It will not start.
I have tried multiple versions, as well as launching it from the DMG directly.
Environment
Zed: v0.127.4 (Zed)
OS: macOS 14.4.0
Memory: 36 GiB
Architecture: aarch64 (Apple M3 Pro)
If applicable, add mockups / screenshots to help explain present your vision of the feature
Screen.Recording2.2024-03-26.at.10.09.04.PM.mov
If applicable, attach your
~/Library/Logs/Zed/Zed.logfile to this issue.This file does not exist
The text was updated successfully, but these errors were encountered: