Not open (Linux, Pop-OS, NVIDIA)

[Mawfyy]

Discord username (optional)

mawfyy

Describe the bug

The app doesn't launch, i try_
$warp-terminal and returns
TermLog.txt

also i try:
$ WGPU_BACKEND=gl warp-terminal
wgpu.txt

To reproduce

Installing warp using .deb

Expected behavior

It open normally

Screenshots

No response

Operating system

Linux

Operating system and version

Pop OS

Shell Version

bash 5.1.16(1)-release

Current Warp version

v0.2024.02.23.08.02.dev_00

Regression

No, this bug or issue has existed throughout my experience using Warp

Recent working Warp date

Never, first try

Additional context

OS: Pop!_OS 22.04 LTS x86_64
Desktop: COSMIC Desktop
GPU: NVIDIA GeForce 210
CPU: Intel Pentium G2020 (2) @ 2.900GHz
Kernel: 6.6.10-76060610-generic
Drivers: NVIDIA legacy 340

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

[ARKye03]

Discord username (optional)

mawfyy

Describe the bug

The app doesn't launch, i try_ $warp-terminal and returns TermLog.txt

also i try: $ WGPU_BACKEND=gl warp-terminal wgpu.txt

To reproduce

Installing warp using .deb

Expected behavior

It open normally

Screenshots

No response

Operating system

Linux

Operating system and version

Pop OS

Shell Version

bash 5.1.16(1)-release

Current Warp version

v0.2024.02.23.08.02.dev_00

Regression

No, this bug or issue has existed throughout my experience using Warp

Recent working Warp date

Never, first try

Additional context

OS: Pop!_OS 22.04 LTS x86_64 Desktop: COSMIC Desktop GPU: NVIDIA GeForce 210 CPU: Intel Pentium G2020 (2) @ 2.900GHz Kernel: 6.6.10-76060610-generic Drivers: NVIDIA legacy 340

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

Downgrade Mesa drivers to 1:23.3.5-1, it should work, or wait for mesa to fix the issue

[dannyneira]

Hey folks! Thanks for your patience while trying Warp. Could you download the latest version of Warp at https://www.warp.dev/linux-terminal ?

If using Wayland, you can enable Wayland support by setting the WARP_ENABLE_WAYLAND envar (e.gWARP_ENABLE_WAYLAND=1 warp-terminal).

[ARKye03]

Hey folks! Thanks for your patience while trying Warp. Could you download this preview version of Warp and see if it fixes your issues:

deb rpm pacman appimage

If using Wayland, you can enable Wayland support by setting the WARP_ENABLE_WAYLAND envar (e.gWARP_ENABLE_WAYLAND=1 warp-terminal).

Can't download the pacman file for testing.

Arch Linux, Gnome, Wayland, Intel Graphics Xe:

AppImage on the other hand seems to work fine with the env var, but some gtk stuff doesnt work well, like the cursor, when my cursor it's over the term it turns to adwaita cursor, but it works natively on wayland (Tested visually with extramaus) and that's cool, even with AppImage.
I wanna try the official pacman pkg.

Note

The warp terminal in the AppImage got updated to v0.2024.02.20.08.01.stable_02 while being in a higher patch but I'm assuming this is just conflicts with the official stable pkg and the test AppImage from the link above

What returns when trying to download the pacman pkg

NoSuchKeyThe specified key does not exist.

[ARKye03]

Trying this testing on:
OS: Arch Linux x86_64
DE: Hyprland (Wayland)
Kernel: 6.7.5-zen1-1-zen
CPU: Intel(R) Core(TM) i5-10400 (12) @ 4.30 GHz
GPU: NVIDIA Geforce RTX 3050

With mesa 1:24.0.1-1(Latest stable repository)

$ WARP_ENABLE_WAYLAND=1 ./Warp-x86_64.AppImage
It open, but does nothing, even opened two instances.
WarpAppImageTest.txt

Tried this command:

$ WAYLAND_DEBUG=1 WARP_ENABLE_WAYLAND=1 ./Warp-x86_64.AppImage
returns:
WarpLogTest.txt
This is what happens if I launch warp and try to resize them, the are like completely frozen.

Both instances running on wayland natively I think (Checked with extramaus and hyprctl)

Once I had a problem similar with Alacritty here in Hyprland only (Compositor issue/bug)

alacritty/alacritty#7485

Hyprland suspends the process\visual part of alacritty (Somewhat normal, when it is not being focused) but never returned it to normal state when it was focused again. In this case the result of warp-terminal is visually similar, but this time it starts frozen from the beginning. It might help.

All of this was trying with warp-terminal-v0.2024.02.27.08.01.stable_00-1-x86_64.appimage and mesa 24