Open Keshayen opened 4 months ago
Can you run warp-terminal
from a different terminal and share the output here?
Can you run
warp-terminal
from a different terminal and share the output here?
here is what came in the output:
20:59:22 [INFO] Spawning terminal server process...
20:59:22 [INFO] Running terminal server...
20:59:22 [WARN] Unable to fetch system color scheme: FDO(
ServiceUnknown(
"The name is not activatable",
),
)
20:59:22 [INFO] Failed to read User from secure storage NotFound
20:59:22 [INFO] Initializing crash reporting Some("linux_stable_release") with tag "v0.2024.03.12.08.02.stable_02"...
20:59:22 [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://session-sharing-server-o3mgmiurkq-uk.a.run.app"), 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, skip_login: false } and version Some("v0.2024.03.12.08.02.stable_02")
20:59:22 [INFO] Performance metrics collector started
20:59:22 [INFO] Start to flush telemetry events to Segment
20:59:22 [INFO] Initializing app services
20:59:22 [ERROR] enumerate_adapters: Initialization of an object has failed
20:59:23 [INFO] Connecting to SQLite database
20:59:23 [INFO] Checking for update on channel stable_release. Update id is yYiA1d6
20:59:23 [INFO] Fetching channel versions (without changelogs) from Warp server
20:59:23 [INFO] fetching team tester status
20:59:23 [INFO] dispatching global action for root_view:open_from_restored
20:59:23 [INFO] dispatching global action for root_view:open_new
20:59:23 [WARN] error getting team tester status: Failed to get access token for GraphQL request. Falling back to in-memory state.
20:59:23 [INFO] Guessed window scale factor: 1.0833333333333333
20:59:23 [INFO] Enabled wgpu backends: Backends(VULKAN | GL | METAL | DX12 | DX11 | BROWSER_WEBGPU)
20:59:23 [INFO] Available wgpu adapters (in priority order):
20:59:23 [ERROR] enumerate_adapters: Initialization of an object has failed
20:59:23 [INFO] Other: AMD PALM (DRM 2.50.0 / 6.8.1-arch1-1, LLVM 17.0.6)
Backend: Gl
Driver: Unknown
Can present? true
Supported texture format: Some(Rgba8UnormSrgb)
20:59:23 [INFO] Verifying adapter "AMD PALM (DRM 2.50.0 / 6.8.1-arch1-1, LLVM 17.0.6)" is valid...
20:59:23 [INFO] Using Other (AMD PALM (DRM 2.50.0 / 6.8.1-arch1-1, LLVM 17.0.6)) for rendering new window.
Illegal instruction (core dumped)
Can you run eglinfo
and share the contents?
Discord username (optional)
No response
Describe the bug
Every time I try to launch warp on archlinux with wayland, it won't no anything
To reproduce
Expected behavior
No response
Screenshots
No response
Operating system
Linux
Operating system and version
Arch linux 6.8.1-arch1-1
Shell Version
bash version 5.2.26(1)-release
Current Warp version
No response
Regression
No, this bug or issue has existed throughout my experience using Warp
Recent working Warp date
No response
Additional context
here is the log
2024-03-21T16:20:25Z [INFO] Spawning terminal server process... 2024-03-21T16:20:25Z [INFO] Running terminal server... 2024-03-21T16:20:25Z [WARN] Unable to fetch system color scheme: FDO( ServiceUnknown( "The name is not activatable", ), ) 2024-03-21T16:20:25Z [INFO] Failed to read User from secure storage NotFound 2024-03-21T16:20:25Z [INFO] Initializing crash reporting Some("linux_stable_release") with tag "v0.2024.03.12.08.02.stable_02"... 2024-03-21T16:20:25Z [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://session-sharing-server-o3mgmiurkq-uk.a.run.app"), 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, skip_login: false } and version Some("v0.2024.03.12.08.02.stable_02") 2024-03-21T16:20:25Z [INFO] Performance metrics collector started 2024-03-21T16:20:25Z [INFO] Start to flush telemetry events to Segment 2024-03-21T16:20:25Z [INFO] Initializing app services 2024-03-21T16:20:25Z [ERROR] enumerate_adapters: Initialization of an object has failed 2024-03-21T16:20:25Z [INFO] Connecting to SQLite database 2024-03-21T16:20:25Z [INFO] fetching team tester status 2024-03-21T16:20:25Z [INFO] Checking for update on channel stable_release. Update id is oZDh0Wu 2024-03-21T16:20:25Z [INFO] Fetching channel versions (without changelogs) from Warp server 2024-03-21T16:20:25Z [INFO] dispatching global action for root_view:open_from_restored 2024-03-21T16:20:25Z [INFO] dispatching global action for root_view:open_new 2024-03-21T16:20:25Z [WARN] error getting team tester status: Failed to get access token for GraphQL request. Falling back to in-memory state. 2024-03-21T16:20:25Z [INFO] Guessed window scale factor: 1.0833333333333333 2024-03-21T16:20:25Z [INFO] Enabled wgpu backends: Backends(VULKAN | GL | METAL | DX12 | DX11 | BROWSER_WEBGPU) 2024-03-21T16:20:25Z [INFO] Available wgpu adapters (in priority order): 2024-03-21T16:20:25Z [ERROR] enumerate_adapters: Initialization of an object has failed 2024-03-21T16:20:25Z [INFO] Other: AMD PALM (DRM 2.50.0 / 6.8.1-arch1-1, LLVM 17.0.6) Backend: Gl Driver: Unknown Can present? true Supported texture format: Some(Rgba8UnormSrgb) 2024-03-21T16:20:25Z [INFO] Verifying adapter "AMD PALM (DRM 2.50.0 / 6.8.1-arch1-1, LLVM 17.0.6)" is valid... 2024-03-21T16:20:25Z [INFO] Using Other (AMD PALM (DRM 2.50.0 / 6.8.1-arch1-1, LLVM 17.0.6)) for rendering new window.
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