Address Already in Use Error and Failure to Open Window

Dupe Check

• I have searched Warp bugs and there are no duplicates

Describe the bug

When attempting to launch the Warp terminal on Arch Linux, I encountered several issues, including an address already being in use, initialization failures, and problems with opening a window. The terminal server process fails to start correctly, and no usable wgpu adapter is found. Below are the relevant logs that provide more detail on the issue.

Logs:

15:25:50 [INFO] Spawning terminal server process...
15:25:50 [INFO] Running terminal server...
Error: Address already in use (os error 98)
15:25:50 [INFO] Running app with windowing system: X11
15:25:50 [INFO] Failed to read User from secure storage NotFound
15:25:50 [INFO] Initializing crash reporting Some("linux_stable_release") with tag "v0.2024.08.27.08.02.stable_02"...
15:25:50 [INFO] Starting warp with channel state ChannelState { channel: Stable, app_id: AppId { qualifier: "dev", organization: "warp", application_name: "Warp" }, additional_features: {}, firebase_api_key: "AIzaSyBdy3O3S9hrdayLJxJ7mriBR4qgUaUygAs", server_root_url: "https://app.warp.dev", ws_server_url: "wss://rtc.app.warp.dev/graphql", session_sharing_server_url: Some("wss://sessions.app.warp.dev"), rudderstack_write_key: "2iyG8S1RaV4XTX6SEypetFSEbLK", rudderstack_root_url: "https://warpianwzlfqdq.dataplane.rudderstack.com", releases_base_url: "https://releases.warp.dev", sentry_url: "https://0195a81da0714f55a93ee4624825f9ec@o540343.ingest.sentry.io/5658526", logfile_name: "warp.log", show_autoupdate_menu_items: true } and version Some("v0.2024.08.27.08.02.stable_02")
15:25:50 [INFO] Start to send telemetry events to RudderStack
15:25:50 [INFO] Start to send telemetry events to RudderStack
15:25:50 [INFO] Performance metrics collector started
15:25:50 [INFO] Initializing app services
15:25:50 [ERROR] enumerate_adapters: Initialization of an object has failed
15:25:50 [INFO] Connecting to SQLite database
15:25:50 [INFO] fetching team tester status
15:25:50 [INFO] dispatching global action for root_view:open_from_restored
15:25:50 [INFO] dispatching global action for root_view:open_new
15:25:50 [INFO] Checking for update on channel stable_release. Update id is 9aLcBi6
15:25:50 [INFO] Fetching channel versions (without changelogs) from Warp server
15:25:50 [INFO] Start to send telemetry events to RudderStack
15:25:50 [WARN] error getting team tester status: Failed to get access token for GraphQL request. Falling back to in-memory state.
15:25:50 [WARN] Failed to retrieve initial request limit info: Failed to get access token for GraphQL request

Caused by:
    Attempted to retrieve access token when user is logged out
15:25:50 [ERROR] enumerate_adapters: Initialization of an object has failed
15:25:50 [INFO] Enabled wgpu backends: Backends(VULKAN | GL | METAL | DX12 | BROWSER_WEBGPU)
15:25:50 [INFO] Available wgpu adapters (in priority order):
15:25:50 [ERROR] Failed to open window: No usable wgpu adapter was found
15:25:50 [INFO] WindowId(0) will close
15:25:50 [INFO] dispatching global action for workspace:save_app
15:25:50 [INFO] active window changed: None
15:25:50 [INFO] dispatching global action for root_view:update_quake_mode_state
15:25:50 [INFO] dispatching global action for workspace:save_app
15:25:50 [WARN] Redraw requested for a window for which we have no state
15:25:50 [INFO] application will terminate
15:25:50 [INFO] Shutting down SQLite writer thread
15:25:51 [INFO] Shut down SQLite writer in 179.907951ms
15:25:51 [INFO] Writing queued events to disk because telemetry is enabled.
15:25:51 [INFO] Successfully wrote telemetry events to disk
15:25:51 [INFO] Tearing down terminal server...
15:25:51 [INFO] Received empty message; assuming the connection has been closed.
15:25:51 [INFO] Tearing down app services...
15:25:51 [INFO] Uninitializing crash reporting...
15:25:51 [INFO] Received channel versions from Warp server: dev: ChannelVersion { version_info: VersionInfo { version: "v0.2024.09.04.15.25.dev_00", update_by: None, soft_cutoff: Some("v0.2023.05.12.08.03.dev_00") }, overrides: [] }; preview: ChannelVersion { version_info: VersionInfo { version: "v0.2024.09.04.15.25.preview_00", update_by: None, soft_cutoff: None }, overrides: [] }; canary: ChannelVersion { version_info: VersionInfo { version: "v0.2022.09.29.08.08.canary_00", update_by: None, soft_cutoff: None }, overrides: [] }; beta: ChannelVersion { version_info: VersionInfo { version: "v0.2024.09.03.08.02.beta_00", update_by: None, soft_cutoff: None }, overrides: [] }; stable: ChannelVersion { version_info: VersionInfo { version: "v0.2024.08.27.08.02.stable_02", update_by: None, soft_cutoff: Some("v0.2024.07.16.08.02.stable_03") }, overrides: [] }

To reproduce

1. Launch the Warp terminal using the command warp-terminal.
2. Observe the error messages and logs produced.

Expected behavior

The Warp terminal should start without errors and open the window successfully.

Screenshots

No response

Operating system

Linux

Operating system and version

Arch Linux x86_64

Shell Version

GNU bash, version 5.2.32(1)-release (x86_64-pc-linux-gnu)

Current Warp version

v0.2024.08.27.08.02.stable_02

Regression

Yes, this bug started recently or with an X Warp version

Recent working Warp date

No response

Additional context

• The error Address already in use (os error 98) suggests a possible conflict with another process using the same address.

• The Failed to open window: No usable wgpu adapter was found indicates an issue with the graphics backend.

Does this block you from using Warp daily?

Yes, this issue prevents me from using Warp daily.

Is this an issue only in Warp?

Yes, I confirmed that this only happens in Warp, not other terminals.

Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e

None

Start with the warp-terminal launch path and reproduce the failure on Arch Linux, focusing on the terminal server's address-in-use error and the wgpu adapter/window initialization logs. Done means the terminal server starts and Warp opens a usable window without these errors.