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
Initialization failed due to unrecognized device #4390
Comments
Hi, there. Could you please provide more info to troubleshoot the issue?
Thank you. |
Hi @LFd3v. Here's the output of the two commands.
It looks like that I can't always reproduce the issue following the steps provided, but here's the error logs from yesterday when Warp crashed:
Hope it's helpful enough. |
@LFd3v actually, I was able to reproduce the issue just now. Here's the very latest logs from
|
Hi, there. Thank you for your feedback. Could you please test one of the preview versions here to check if it fixes the problem? Also, it seems that Warp is trying to use NVidia GPU for rendering, you can also try to force it use the iGPU in Settings > Features > bottom most option and see if it helps. |
Hi @LFd3v. I tried installing and using a preview version but it looks like the issue is still occurring. Here are the latest logs.
One detail that might actually be helpful is that it only happened when I closed and try to reopen it after running a few commands. When I tried to reproduce the issue without using the terminal too much but just closing and reopening, it didn't happen. Thanks. |
@LFd3v I also tried reinstalling Warp completely (without rebooting the device) and it looks like the issue keeps happening. Only a shutdown fixes the problem. |
@smonolo Have you tried the suggestion above as well? You can also try to boot the system using only the integrated GPU, since it seems that you have a hybrid graphics system. |
@LFd3v I just tried that and it looks like Warp is always opening correctly. If it happens again using this configuration, I'll let you know. Anyways I believe it's still an issue that could be looked into as it's quite blocking for a user that does not know about the fix. What do you think? |
@smonolo Sure, it indeed looks like a problem with NVidia drivers. I am glad it is working fine with this workaround. Cheers. |
I believe the error is due to this (still open) nVidia driver bug: NVIDIA/egl-wayland#94 I'm following up there to see if there's any good way for us to work around this at the application level. |
@vorporeal I see, thanks for the update! |
Discord username (optional)
stefano
Describe the bug
Sometimes, apparently after closing down the app once, Warp won't fully initialize and close down right after opening it. I checked the logs and it looks like it fails to recognize the device.
To reproduce
exit
)Expected behavior
Warp should open up and run correctly
Screenshots
Screencast.from.2024-02-28.10-02-36.webm
Operating system
Linux
Operating system and version
Ubuntu 23.10
Shell Version
bash 5.2.15
Current Warp version
No response
Regression
No, this bug or issue has existed throughout my experience using Warp
Recent working Warp date
2028-02-28 09:30
Additional context
No response
Does this block you from using Warp daily?
Yes, this issue prevents me from using Warp daily.
Is this a Warp specific issue? (i.e. does it happen in Terminal, iTerm, Kitty, etc.)
Yes, this I confirmed this only happens in Warp, not other terminals.
Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e
None
The text was updated successfully, but these errors were encountered: