search

warpdotdev / Warp

Warp is a modern, Rust-based terminal with AI built in so you and your team can build great software, faster.
https://warp.dev
Other
21.11k stars 361 forks source link

Window isn't opening #5062

Open Jumima67 opened 3 months ago

Jumima67 commented 3 months ago

Dupe Check

Describe the bug

If I start warp per command line I get two error, maybe just one, I don't really know.

To reproduce

  1. Install
  2. Launch

Expected behavior

No response

Screenshots

IMG_0844

Operating system

Linux

Operating system and version

Arch Linux

Shell Version

I'm trying to start the terminal from fish.

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

So when I first launch it, I get to the picture. After I press "Cancel". It proceeds to do something. Log below

19:44:32 [INFO] Spawning terminal server process... 19:44:32 [INFO] Running terminal server... 19:44:32 [INFO] Running app with windowing system: X11 19:44:32 [WARN] Unable to fetch Linux system color scheme: FDO( ServiceUnknown( "The name is not activatable", ), ) 19:44:35 [INFO] Failed to read User from secure storage NotFound 19:44:35 [INFO] Initializing crash reporting Some("linux_stable_release") with tag "v0.2024.06.18.08.02.stable_04"... 19:44:35 [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.18.08.02.stable_04") 19:44:35 [INFO] Start to flush telemetry events to Segment 19:44:35 [INFO] Performance metrics collector started 19:44:35 [INFO] Initializing app services 19:44:35 [WARN] EGL context: -robust access 19:44:35 [ERROR] enumerate_adapters: Initialization of an object has failed 19:44:35 [INFO] Connecting to SQLite database 19:44:35 [INFO] fetching team tester status 19:44:35 [INFO] Checking for update on channel stable_release. Update id is OViX4yt 19:44:35 [INFO] Fetching channel versions (without changelogs) from Warp server 19:44:35 [INFO] dispatching global action for root_view:open_from_restored 19:44:35 [INFO] dispatching global action for root_view:open_new 19:44:35 [INFO] Received channel versions from Warp server: dev: ChannelVersion { version_info: VersionInfo { version: "v0.2024.06.24.08.02.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.06.24.08.02.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.06.18.08.02.beta_00", update_by: None, soft_cutoff: None }, overrides: [] }; stable: ChannelVersion { version_info: VersionInfo { version: "v0.2024.06.18.08.02.stable_03", update_by: None, soft_cutoff: Some("v0.2024.05.07.08.02.stable_02") }, overrides: [VersionOverride { predicate: TargetOS(Linux), version_info: VersionInfo { version: "v0.2024.06.18.08.02.stable_04", update_by: None, soft_cutoff: None } }] } 19:44:35 [WARN] error getting team tester status: Failed to get access token for GraphQL request. Falling back to in-memory state. 19:44:35 [INFO] No update available 19:44:35 [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 19:44:35 [WARN] EGL context: -robust access 19:44:35 [INFO] Enabled wgpu backends: Backends(VULKAN | GL | METAL | DX12 | DX11 | BROWSER_WEBGPU) 19:44:35 [INFO] Available wgpu adapters (in priority order): 19:44:35 [ERROR] enumerate_adapters: Initialization of an object has failed 19:44:35 [INFO] Other: NVA5 Backend: Gl Driver: Unknown Can present: true Supported texture format: Some(Rgba8UnormSrgb) 19:44:35 [INFO] Verifying adapter "NVA5" is valid... 19:44:35 [WARN] Failed to create a logical device: Limit 'max_inter_stage_shader_components' value 64 is better than allowed 60 19:44:35 [ERROR] Failed to open window: No usable wgpu adapter was found 19:44:35 [INFO] WindowId(0) will close 19:44:35 [INFO] dispatching global action for workspace:save_app 19:44:35 [WARN] Redraw requested for a window for which we have no state 19:44:35 [INFO] active window changed: None 19:44:35 [INFO] dispatching global action for root_view:update_quake_mode_state 19:44:35 [INFO] dispatching global action for workspace:save_app 19:44:35 [INFO] application will terminate 19:44:35 [INFO] Shutting down SQLite writer thread 19:44:35 [INFO] Shut down SQLite writer in 4.323522ms 19:44:35 [INFO] Writing queued events to disk because telemetry is enabled. 19:44:35 [INFO] Successfully wrote telemetry events to disk 19:44:35 [INFO] Tearing down terminal server... 19:44:35 [INFO] Received empty message; assuming the connection has been closed. 19:44:35 [INFO] Tearing down app services... 19:44:35 [INFO] Uninitializing crash reporting... 19:44:36 [INFO] Flushed telemetry events.

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

Jumima67 commented 3 months ago

Forgot that I'm on Wayland

acarl005 commented 3 months ago

Hi @Jumima67 thanks for reporting the issue. Are you using the Nouveau graphics drivers?

dannyneira commented 3 months ago

@Jumima67 You may be able to work around this by forcing the use of integrated GPU vs the dedicated GPU. To use the Low Power (integrated) GPU put the following settings in your ~/.config/warp-terminal/user_preferences.json file: {"prefs":{"PreferLowPowerGPU": "true",}}

Jumima67 commented 3 months ago

Yes, I am using nouveau.

Jumima67 commented 3 months ago

{ "prefs" : { "ExperimentId": "9298320e-e9c6-4c3f-9edf-c70524bce479", "CrashReportingEnabled": "true", "PreferLowPowerGPU": "true", "TelemetryEnabled": "true" } }

This is how my config currently looks and it didn't work.

Jumima67 commented 3 months ago

By the way I don't have the GPG error anymore.

Jumima67 commented 2 months ago

Was that the answer, that I should use a NVIDIA driver instead?