called Result::unwrap() on an Err value: TypeMismatch(0)

[psilospore]

Discord username (optional)

No response

Describe the bug

I installed warp via pacman on Arch and ran it. It seems that it errors out.

❯ warp-terminal
19:49:09 [INFO] Spawning terminal server process...
19:49:09 [INFO] Running terminal server...
19:49:09 [WARN] Unable to fetch system color scheme: FDO(
    ServiceUnknown(
        "The name is not activatable",
    ),
)
19:49:09 [INFO] Failed to read User from secure storage NotFound
19:49:09 [INFO] Initializing crash reporting Some("linux_stable_release") with tag "v0.2024.03.05.08.02.stable_01"...
19:49:09 [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.05.08.02.stable_01")
19:49:09 [INFO] Performance metrics collector started
19:49:09 [INFO] Initializing app services
19:49:09 [INFO] Start to flush telemetry events to Segment
19:49:10 [WARN] Detected skylake derivative running on mesa i915. Clears to srgb textures will use manual shader clears.
19:49:10 [INFO] Connecting to SQLite database
19:49:10 [INFO] fetching team tester status
19:49:10 [INFO] Checking for update on channel stable_release. Update id is QGdRV0g
19:49:10 [INFO] Fetching channel versions (without changelogs) from Warp server
19:49:10 [INFO] dispatching global action for root_view:open_from_restored
19:49:10 [INFO] dispatching global action for root_view:open_new
19:49:10 [WARN] error getting team tester status: Failed to get access token for GraphQL request. Falling back to in-memory state.
19:49:10 [INFO] Received channel versions from Warp server: dev: ChannelVersion { version_info: VersionInfo { version: "v0.2024.03.08.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.03.08.08.01.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.03.05.08.02.beta_00", update_by: None, soft_cutoff: None }, overrides: [] }; stable: ChannelVersion { version_info: VersionInfo { version: "v0.2024.03.05.08.02.stable_01", update_by: None, soft_cutoff: Some("v0.2024.01.16.16.31.stable_00") }, overrides: [] }
thread 'main' panicked at /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/winit-0.29.13/src/platform_impl/linux/x11/xsettings.rs:42:14:
called `Result::unwrap()` on an `Err` value: TypeMismatch(0)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
19:49:10 [INFO] Shutting down SQLite writer thread
19:49:10 [INFO] Shut down SQLite writer in 863.953µs
19:49:10 [INFO] Received empty message; assuming the connection has been closed.

To reproduce

Install with pacman -U
Run executable

Expected behavior

No response

Screenshots

No response

Operating system

Linux

Operating system and version

Arch

Shell Version

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

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

[dannyneira]

Hi @psilospore sorry to hear about this. It may have to do with several factors, but based on your logs it could be due to the mesa drivers installed. 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.

[alokedesai]

Hi @psilospore We believe we just merged a fix for this. It should be in next week's release, which will be available on Thursday.

[psilospore]

Thanks this worked for me!