Open hmnd opened 9 months ago
Hey there, thanks for letting us know!
Two things:
RUST_BACKTRACE=1 warp-terminal
to get it.We've added a list of workarounds here: https://docs.warp.dev/help/known-issues#linux-workarounds
Also, make sure to download the latest version as we release fixes every week. https://docs.warp.dev/getting-started/changelog
Please let me know if that helped on this tracker issue.
Same problem here. I am using Manjaro Gnome, here is the stack trace. My Alacritty works good.
Kernel: 6.6.46-1-MANJARO Version: v0.2024.08.20.08.02.stable_00
❯ RUST_BACKTRACE=full warp-terminal
14:00:57 [INFO] Spawning terminal server process...
14:00:57 [INFO] Running terminal server...
14:00:57 [WARN] Tried to initialize the wayland data control protocol clipboard, but failed. Falling back to the X11 clipboard protocol. The error was: Unknown error while interacting with the clipboard: A required Wayland protocol (zwlr_data_control_manager_v1 version 1) i
s not supported by the compositor
14:00:57 [INFO] Running app with windowing system: X11
14:00:57 [INFO] Failed to read User from secure storage NotFound
14:00:57 [INFO] Initializing crash reporting Some("linux_stable_release") with tag "v0.2024.08.20.08.02.stable_00"...
14:00:57 [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.20.08.02.stable_00")
14:00:57 [INFO] Start to send telemetry events to RudderStack
14:00:57 [INFO] Performance metrics collector started
14:00:57 [INFO] Start to send telemetry events to RudderStack
14:00:57 [INFO] Initializing app services
14:00:58 [INFO] Flushed telemetry events.
thread 'main' panicked at /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/khronos-egl-6.0.0/src/lib.rs:1779:38:
called `Option::unwrap()` on a `None` value
stack backtrace:
0: 0x5633d2d9d48b - <unknown>
1: 0x5633d240fd1b - <unknown>
2: 0x5633d2d98633 - <unknown>
3: 0x5633d2d9d1fe - <unknown>
4: 0x5633d2d9f496 - <unknown>
...
34: 0x5633d2d8edf3 - <unknown>
35: 0x5633d2d7097c - <unknown>
36: 0x7f9923945e08 - <unknown>
37: 0x7f9923945ecc - __libc_start_main
38: 0x5633d2185b0e - <unknown>
39: 0x0 - <unknown>
Discord username (optional)
No response
Describe the bug
When attempting to start Warp, I get the following error:
To reproduce
warp-terminal
from aurwarp-terminal
Expected behavior
Warp starts normally
Screenshots
No response
Operating system
Linux
Operating system and version
Manjaro Linux, kernel v6.6.10
Shell Version
bash 5.2.21, zsh 5.9
Current Warp version
v0.2024.02.20.08.01.stable_01
Regression
No, this bug or issue has existed throughout my experience using Warp
Recent working Warp date
No response
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