crash on startup

Dupe Check

• I have searched Warp bugs and there are no duplicates

Describe the bug

After working flawless for several weeks I can't start warp-terminal any more.
[yogi@LanzaroteI9 ~]$ warp-terminal&
[1] 27133
warp-terminal: /lib64/libcurl.so.4: no version information available (required by warp-terminal)
[yogi@LanzaroteI9 ~]$ 15:36:26 [INFO] Spawning terminal server process...
/opt/warpdotdev/warp-terminal/warp: /lib64/libcurl.so.4: no version information available (required by /opt/warpdotdev/warp-terminal/warp)
15:36:26 [INFO] Running terminal server...
15:36:26 [INFO] Running app with windowing system: X11
15:36:26 [ERROR] Failed to acquire default Secret Service collection: unknown error
15:36:26 [INFO] regenerating access token
15:36:26 [INFO] Initializing crash reporting Some("linux_stable_release") with tag "v0.2024.06.25.08.02.stable_01"...
15:36:26 [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"), segment_write_key: "sTT9ZajzIaQ0phzLFOnqZ6VOqplJTlaJ", segment_root_url: "https://api.segment.io", 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.06.25.08.02.stable_01")
15:36:26 [INFO] Performance metrics collector started
15:36:26 [INFO] Start to flush telemetry events to Segment
15:36:26 [INFO] Dropping empty telemetry batch
15:36:26 [INFO] Flushed telemetry events.
15:36:26 [INFO] Initializing app services
thread 'main' panicked at /home/runner/.cargo/git/checkouts/wgpu-163ac9f6133c4ea6/70ade4c/wgpu-hal/src/gles/egl.rs:798:88:
called Option::unwrap() on a None value
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

[1] + 27133 exit 101 warp-terminal

To reproduce

enter warp-terminal at the shell prompt

Expected behavior

No response

Screenshots

No response

Operating system

Linux

Operating system and version

OpenSuSe Tumbleweed VERSION="20240419"

Shell Version

zsh 5.9 (x86_64-suse-linux-gnu)

Current Warp version

latest from warp web page

Regression

No, this bug or issue has existed throughout my experience using Warp

Recent working Warp date

2024-07-10

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 with warp-terminal on OpenSUSE Tumbleweed and inspect the panic reported at wgpu-hal/src/gles/egl.rs:798:88. Check the startup log around the GLES/EGL initialization failure; done means Warp starts successfully without the Option::unwrap panic.