Initialization failed due to unrecognized device

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

1. Open the app
2. Close it down (I experienced it by using exit)
3. Try to open it again

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

Start by reproducing the failure on Ubuntu 23.10: open Warp, exit it with exit, then reopen it and inspect the logs for the device-recognition error. Done means Warp initializes and remains open normally after being closed and relaunched.