Open MEHREGANKBI opened 3 months ago
The screenshots I took from the broken window, resource usage, and the editor not creating the file:
Image1: high resource usage
Image2: That little white window in the middle is supposed to be the zed window.
Image3: Zed window showing corrupted image of my other windows.
Image4: Zed not even creating the file passed by the command above. This could be the expected behavior, many other editors don't create the file until it's saved by the user. I still tried this to see if this'd fix the issue.
I got somehow the same issue with my Nvidia GPU.
We're not yet sure why this happens.
We have seen some people have success with mesa
drivers; I'm not sure about NVIDIA drivers.
Are you able to test out different drivers and see whether any work?
I see this as well on an up to date Manjaro installation. I will try to change drivers but I am not sure what that will do to the rest of the system since it was a while ago since I was mucking around with graphics drivers.
I am experiencing the same issue. For context I want to add that I did install Zed from binary prior to when it was available on the website - and it was working. Then I removed it, and today I discovered that it was "released" and wanted to try - and here we are, empy windowing
Same issue on Linux Mint 22 / NVIDIA proprietary driver. Zed sometimes just appears to be a screenshot of the desktop. Doesn't always happen, never happens with using free drivers (but then the performance is awful)
Check for existing issues
Describe the bug / provide steps to reproduce it
I have tried to use versions 0.143.6 and 0.143.7, both stable releases on Linux. Upon entering the terminal command "zed", a broken window pops up (screenshots below), CPU usage goes up to 100% on all cores, and the fans are cranked to max speed. But nothing happens. The CPU and the fans calm down after 10 seconds, but as soon as I try to move the window the CPU and the fans start running at 100% again. Again, nothing ever happens. there is an X button above the window but it doesn't close the app so I'm forced to use kill (with the default signal). I tried using the command along with a file name i.e. "zed sth.txt", which caused the same broken window to pop up, and the sth.txt file was never created. No logs were created either. I tried installing the app using the shell script provided on the website, and I also tried to use the app by downloading an unzipping the tar.gz file. No difference. Both broken.
The system is healthy and runs other apps and IDEs like VS code without issues. I tried to isolate the zed-related syslog which shows lots of things related to the GPU driver and gnome-shell. Those errors, esp the gnome-shell ones only happen when running zed. (There's also this buggy client warning from gnome-shell). I will paste the logs in the logs section below.
Environment
output of uname: 5.15.0-116-generic #126-Ubuntu SMP Mon Jul 1 10:14:24 UTC 2024 x86_64 x86_64 GNU/Linux
output of neofetch: Distro: Ubuntu 22 LTS DE: GNOME WM: Mutter WM theme: Adawaita Theme and icons: Yaru-blue CPU: dual-core Intel Core i5-2430M RAM: 8GB 1300MHz GPU: Nvidia GeForce 410m with 1GB of VRAM. Monitors: Dual-monitor with Resolutions: 1440x900 and 1366x768
If applicable, attach your
~/Library/Logs/Zed/Zed.log
file to this issue.Zed.log