Warp icon indicating copy to clipboard operation
Warp copied to clipboard

bug: cannot start on arch linux / wayland/ hyprland

Open JonnyLoughlin opened this issue 1 year ago • 9 comments

Discord username (optional)

No response

Describe the bug

Hi, I tried installing the pkg file from the website and when I try to run Warp, I get the following error:

libEGL warning: egl: failed to create dri2 screen
ERROR:             ICD associated with VkPhysicalDevice does not support GetPhysicalDeviceCalibrateableTimeDomainsKHR
zsh: IOT instruction (core dumped)  warp-terminal

I am running Arch/Hyprland on an nvida gpu and intel cpu.

To reproduce

  1. Download from https://app.warp.dev/get_warp

  2. run sudo pacman -U warp-terminal-v0.2024.02.20.08.01.stable_01-1-x86_64.pkg.tar.zst

  3. run warp-terminal

  4. program crashes with error above

Expected behavior

No response

Screenshots

No response

Operating system

Linux

Operating system and version

Arch kernal linux 6.7.5.arch1-1

Shell Version

No response

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

JonnyLoughlin avatar Feb 22 '24 16:02 JonnyLoughlin

Exactly same issue here on my setup with Arch + Hyprland. Attach my Nvidia information here in case related:

Driver Version: 545.29.06 CUDA Version: 12.3 Nvidia RTX A5000

TeddyHuang-00 avatar Feb 22 '24 16:02 TeddyHuang-00

Just checked the discord, downgrading mesa fixed my issue

sudo pacman -U /var/cache/pacman/pkg/mesa-1:23.3.3-1-x86_64.pkg.tar.zst

JonnyLoughlin avatar Feb 22 '24 16:02 JonnyLoughlin

This is most likely due to upstream issues: https://gitlab.freedesktop.org/mesa/mesa/-/issues/10624 https://github.com/KhronosGroup/Vulkan-Loader/issues/1443

Guess downgrading mesa before they get fixed would be the only solution for now.

TeddyHuang-00 avatar Feb 22 '24 17:02 TeddyHuang-00

It worked out-of-the-box for me on Arch+Hyprland (it uses XWayland). If you are on Arch Linux why not use use the AUR e.g. yay -S warp-terminal?

Edit:

% sudo pacman -Q mesa
mesa 1:24.0.1-1

regul4rj0hn avatar Feb 22 '24 19:02 regul4rj0hn

The AUR had the same issue. All that AUR package does is install the release package from warp so it shouldn't have made any difference.

Are you on nvidia or amd/integrated graphics?

JonnyLoughlin avatar Feb 22 '24 19:02 JonnyLoughlin

Yep, I thought as much. Just figured it was a bit weird to not use AUR (on top of that it worked for me). GeForce RTX 4070 Ti. Good that the workaround fixed it for you anyway.

regul4rj0hn avatar Feb 22 '24 19:02 regul4rj0hn

FYI @regul4rj0hn - we provide official packages for Arch, which we would recommend using over a package from the AUR. Installing the official package ensures you get the most timely updates, and that there are no issues with a bad/out-of-date package definition. (I'm chatting with people in the comments on the AUR package to figure out the best way to handle this.)

vorporeal avatar Feb 22 '24 22:02 vorporeal

@vorporeal Sure. Apologies for being slow here, but the AUR script does pull the official package; so what do you mean by "official" in this context exactly? Is it available on extra as other terminal emulators are? If so, under what name? As of this moment I am searching an up-to-date pacman DB and for the life of me I cannot find it.

regul4rj0hn avatar Feb 23 '24 18:02 regul4rj0hn

Is it available on extra as other terminal emulators are?

I guess they refer to this section: https://docs.warp.dev/getting-started/getting-started-with-warp#arch-linux-based-distributions

TeddyHuang-00 avatar Feb 23 '24 18:02 TeddyHuang-00

As @TeddyHuang-00 mentions above, this is unfortunately due to an upstream bug in mesa 24: https://gitlab.freedesktop.org/mesa/mesa/-/issues/10624

We're working on getting Warp to run natively on Wayland (i.e.: no Xwayland) ASAP.

In the meantime, as @ARKye03 says above, you can downgrade to mesa 23.x as a temporary workaround.

vorporeal avatar Feb 26 '24 22:02 vorporeal

Also experiencing this issue

Sophed avatar Feb 27 '24 17:02 Sophed