Regression between v0.168 and v0.169, crash due to PlatformNotSupported
              
              #36528
            
            Replies: 10 comments
-
| 
         Thanks for running the bisect and connecting this to #20853. Also, seems like you're not the only one affected by this :(. From the original PR, it seems that updating your drivers may help? Could you or @vinifrancosilva confirm if that helps either of you? I'll also take a look to see if we can add some way to tell Zed which GPU to use/not use (so you don't have to blacklist the kernel modules in  Maybe @kvark has some input on workarounds here as well?  | 
  
Beta Was this translation helpful? Give feedback.
-
| 
         Would be great to see the logs!  | 
  
Beta Was this translation helpful? Give feedback.
-
| 
         There is nothing much interesting in the logs though: Logs from one run built from 387281fIs there something I can run to pin it down more specifically?  | 
  
Beta Was this translation helpful? Give feedback.
-
| 
         Could you add   | 
  
Beta Was this translation helpful? Give feedback.
-
| 
         Sure! I built in debug mode this time as well, in case that helps to uncover anything. Logs from one run built from 387281f, this time with 
 | 
  
Beta Was this translation helpful? Give feedback.
-
| 
         @ruuda Looks like this is a relatively modern GPU (NVIDIA GeForce RTX 3050 Ti Laptop GPU) with a recent driver  
  | 
  
Beta Was this translation helpful? Give feedback.
-
        
 Do you mean ‘should’ as in, it ought to be supported, but it is not currently, or do you mean that you expect Zed to already work on my system? It did work until 298b9df, when what looks like an intentional change related to Blade broke it. Now that you mention it, I tried again with latest  Following the steps at https://zed.dev/docs/linux#forcing-zed-to-use-a-specific-gpu, it lists my GPU as and running Zed with  Still, it would be nice if it worked out of the box like it did before, no other text editor I use requires me to set environment variables just to get a window on the screen.  | 
  
Beta Was this translation helpful? Give feedback.
-
        
 
 I meant   | 
  
Beta Was this translation helpful? Give feedback.
-
| 
         I'm going to move this to a discussion. There isn't anything immediately actionable here, other users are able to use these devices without specifying  Happy to revisit if you (or anyone else) has suggestions for how to proceed.  | 
  
Beta Was this translation helpful? Give feedback.
-
| 
         Re-reading this discussion. Here is what I see in short: 
 It's totally unclear why NV is not able to present to our surface, it's unexpected. Would be interesting to see if   | 
  
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Summary
I used to be able to run Zed on my Dell XPS 15 9510, but recently it refuses to start. Bisecting shows it broke in v0.169 due to #20853, which I suppose is an intended side-effect of that change.
Steps to trigger the problem:
zeditor --foregroundActual Behavior:
Expected Behavior:
The editor starts.
After bisecting, the first bad commit is 298b9df, introduced in #20853. There is some discussion there that it breaks Intel + Nvidia systems … well, the Dell XPS 15 9510 is apparently one of the affected systems. I don’t use the Nvidia GPU though, and I blacklist the
nvidiaandnvidia_uvmkernel modules in/etc/modprobe.d; everything runs fine on just the integrated Intel graphics. (It is possible that something recently changed on my system — I tried loading the module to see if it helped Zed to start, so during the bisection process it was loaded, but I think I just haven’t used Zed since mid-December on this laptop.)I have a different, slightly older Dell XPS with Intel + Nvidia GPU, and Zed runs fine on that laptop. (I think I don’t have the Nvidia drivers installed at all on that one, but I’m not sure from the top of my head.)
I suppose this breakage was expected, though it would be nice if I could run Zed again. No other software I use (Gnome desktop, editors, IDEs, browsers, video players, games) has issues with the Nvidia GPU being present in the laptop. I’m happy to help diagnose this further.
Zed Version and System Specs
Zed: v0.168.0 (Zed Dev 56d20fc)
OS: Linux Wayland arch unknown (It’s kernel 6.13.5-arch1-1)
Memory: 31.1 GiB
Architecture: x86_64
GPU: Intel(R) UHD Graphics (TGL GT1) || Intel open-source Mesa driver || Mesa 24.3.4-arch1.1
If applicable, attach your
~/Library/Logs/Zed/Zed.logfile to this issue.No response
Beta Was this translation helpful? Give feedback.
All reactions