-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Previously uninstalled zed zed incorrectly, but cannot run after reinstalling #19659
Comments
At the moment, you did not provide enough information for anybody to help resolve your issue. You might want to update your request with the following information:
|
If you are on Linux, which I am assuming because of
then ran
to open the app from the terminal ? |
The first time I used it, I installed it with flatpak and it was available. However, due to some system reasons, it crashed. After reinstalling the system, all flatpak applications disappeared, and there may still be some residual files in the home directory. After the second installation with flatpak, it was not available |
system
|
@micahasowata
|
What command were you trying to execute before you got this log output?
This is exactly the same system I run on. |
Does opening it from the Applications view, work? (i.e clicking the icon)
I can't find the file referenced in the logs. @SomeoneToIgnore @JosephTLyons, I need help locating the file referenced in that log. |
This is the log obtained by clicking on the icon. Opening from the command line will result in the same log. The phenomenon remains unresponsive |
It has something to do with a GPU adapter. This is not exactly a Zed issue. From what I understand, Zed needs to find some ray tracing extensions for your GPU which it did not find and that is stopping it from displaying the UI The installation is fine. Zed is probably fine. We just need to figure out the proper ray tracing extension to install to get it to work |
Do I need to provide anything else for you? I'm happy to do that |
Can this issue be resolved in the near future. I am currently unable to open it |
I don't know if this goes against the rules of the Zed community. It might or might not work 100% but this might be a solution This is installation instruction for Mesa which is the ray tracing extension for Vulkan |
try the installation, let me know teh result |
Complete the complete log. From opening to error ending
|
What is the content of this file
|
What is the result of running this command
|
|
From the logs and from searches, the issue seems to be that Intel UHD, which is your adapter, lacks support for ray tracing and Zed needs an adapter that supports ray tracing. Since it can't find one on your PC it crashes |
The obvious solution to the issue is figuring out how to run Zed on adapters that don't support ray tracing. I don't know anything about that. |
But it could have worked normally a long time ago |
Did it ever work? When did it stop working? |
long ago. I can't remember the exact time either. I was able to work about a month or two ago. My Ubuntu crashed due to other reasons. After reinstalling Ubuntu and then reinstalling Zed, it no longer works |
Okay. So if we figure out the version of Zed that worked and tweak the installer you might be able to get up and running with Zed. No guarantees. Do you want that? |
How to do it? |
Give me a few minutes to figure it out |
It seems like issue #14225 relates to your problem check it out? especially this #14225 (comment) this is also relevant https://zed.dev/docs/linux#zed-is-very-slow |
try the suggestions and let me know if the issue was resolved |
|
I don't think there's an optimal solution at the moment. The referenced issue hasn't been closed yet. For now, whatever works is best. |
Check for existing issues
Describe the bug / provide steps to reproduce it
log
Environment
flatpak
If applicable, add mockups / screenshots to help explain present your vision of the feature
No response
If applicable, attach your Zed.log file to this issue.
The text was updated successfully, but these errors were encountered: