Warp
Warp copied to clipboard
warpdotdev
Arch Linux, Nvidia(Proprietary Drivers), Wayland(Hyprland)
Discord username (optional)
arkangel3132
Describe the bug
Can't run warp-terminal, returns this from the terminal: The same here, Arch Linux, Nvidia, Hyprland(As wayland compositor), the app just doesnt launch: I try: $ warp-terminal returns TermLog.txt
If I try $ WGPU_BACKEND=gl warp-terminal returns WGPU_WARP.txt
To reproduce
Install warp-terminal from AUR with yay, $ yay -S warp-terminal $ warp-terminal
I tried downloading the official pkg, and # pacman -U warp-terminal-v0.2024.02.20.08.01.stable_01-1-x86_64.pkg.tar.zst Didn't work either, same results.
Expected behavior
It open normally
Screenshots
No response
Operating system
Linux
Operating system and version
Arch Linux
Shell Version
zsh 5.9 (x86_64-pc-linux-gnu)
Current Warp version
Can't open the terminal, but "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
Never, first try
Additional context
WAYLAND_DEBUG=1 warp-terminal --print-events returns: WarpLog.txt
Arch Linux: Desktop: Hyprland (Wayland) Kernel: 6.7.5-zen1-1-zen Nvidia Drivers: NVIDIA 545.29.06 CPU: Intel i5-10400 (12) GPU: NVIDIA Geforce RTX 3050
Environment var: LIBVA_DRIVER_NAME=nvidia XDG_SESSION_TYPE=wayland GBM_BACKEND=nvidia-drm __GLX_VENDOR_LIBRARY_NAME=nvidia WLR_NO_HARDWARE_CURSORS=1 QT_QPA_PLATFORM=wayland WLR_RENDERER_ALLOW_SOFTWARE=1 GDK_BACKEND=wayland
Extra NOTE!!!! Warp works fine in Arch Linux + Wayland + Gnome + Intel Graphics Xe, so that up there can be Nvidia issues
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
Downgrading Mesa to mesa 1:23.3.5-1 Fix the problem for me at least, anyway, the login didn't work, sign in/up, neither of them worked, but I have found a workaround to solve this issue, and now trying the terminal, seems pretty awesome using Alacritty and Warp, lets see which one becomes my daily term
I'm having the same problem. I recieve the following error message when I try to run the official pacman package (or the app image). I'm also running arch + hyplrand + nvidia proprieary drivers.
stdout is a tty true, in CI false. using logfile: false
13:50:16 [INFO] Spawning terminal server process...
13:50:16 [WARN] Unsupported locale "en_IN". Restoring default locale "C".
xkbcommon: ERROR: couldn't find a Compose file for locale "en_IN" (mapped to "en_IN.ISO8859-1")
13:50:16 [INFO] Running terminal server...
13:50:16 [WARN] Unable to fetch system color scheme: FDO(
UnknownMethod(
"No such interface “org.freedesktop.portal.Settings” on object at path /org/freedesktop/portal/desktop",
),
)
13:50:16 [INFO] Failed to read User from secure storage NotFound
13:50:16 [INFO] Initializing crash reporting Some("stable_release") with tag "v0.2024.02.20.08.01.stable_01"...
13:50:16 [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://[email protected]/5658526", logfile_name: "warp.log", show_autoupdate_menu_items: true, skip_login: false } and version Some("v0.2024.02.20.08.01.stable_01")
13:50:16 [INFO] Performance metrics collector started
13:50:16 [INFO] Start to flush telemetry events to Segment
13:50:16 [INFO] Initializing app services
13:50:16 [INFO] Start to flush telemetry events to Segment
libEGL warning: egl: failed to create dri2 screen
ERROR: ICD associated with VkPhysicalDevice does not support GetPhysicalDeviceCalibrateableTimeDomainsKHR
[1] 4355 IOT instruction (core dumped) warp-terminal
EDIT: I've tried out other DM/WMs and for me it only works with Gnome + Xorg
I'm having the same problem. I recieve the following error message when I try to run the official pacman package (or the app image). I'm also running arch + hyplrand + nvidia proprieary drivers.
stdout is a tty true, in CI false. using logfile: false 13:50:16 [INFO] Spawning terminal server process... 13:50:16 [WARN] Unsupported locale "en_IN". Restoring default locale "C". xkbcommon: ERROR: couldn't find a Compose file for locale "en_IN" (mapped to "en_IN.ISO8859-1") 13:50:16 [INFO] Running terminal server... 13:50:16 [WARN] Unable to fetch system color scheme: FDO( UnknownMethod( "No such interface “org.freedesktop.portal.Settings” on object at path /org/freedesktop/portal/desktop", ), ) 13:50:16 [INFO] Failed to read User from secure storage NotFound 13:50:16 [INFO] Initializing crash reporting Some("stable_release") with tag "v0.2024.02.20.08.01.stable_01"... 13:50:16 [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://[email protected]/5658526", logfile_name: "warp.log", show_autoupdate_menu_items: true, skip_login: false } and version Some("v0.2024.02.20.08.01.stable_01") 13:50:16 [INFO] Performance metrics collector started 13:50:16 [INFO] Start to flush telemetry events to Segment 13:50:16 [INFO] Initializing app services 13:50:16 [INFO] Start to flush telemetry events to Segment libEGL warning: egl: failed to create dri2 screen ERROR: ICD associated with VkPhysicalDevice does not support GetPhysicalDeviceCalibrateableTimeDomainsKHR [1] 4355 IOT instruction (core dumped) warp-terminalEDIT: I've tried out other DM/WMs and for me it only works with Gnome + Xorg
It works fine under Xorg, actually works natively, the errors I've encountered are only because XWayland + Nvidia it's pretty bad, as I said, in Gnome with wayland but intel graphics works almost perfect out of the box, I'm really waiting for them to support wayland natively, nowadays people are using wayland, all major distros are dropping X11
This error at the end of your log:
libEGL warning: egl: failed to create dri2 screen ERROR: ICD associated with VkPhysicalDevice does not support GetPhysicalDeviceCalibrateableTimeDomainsKHR [1] 4355 IOT instruction (core dumped) warp-terminal
Comes from Mesa graphics, dowgrade to 23.5, or 23.2, only if you wanna use warp at all cost like me, or wait for mesa to fix those bugs because warp isn't the only one.
Yeah, 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.
Going to close this out as a dupe of https://github.com/warpdotdev/Warp/issues/4214, and use that as the tracking issue for this crash.