-
Notifications
You must be signed in to change notification settings - Fork 383
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't start on Arch Linux + Wayland + KDE + NVIDIA #4241
Comments
Hey there, thanks for letting us know! Two things:
|
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. |
Same problem here. I am using Manjaro Gnome, here is the stack trace. My Alacritty works good. Kernel: 6.6.46-1-MANJARO
|
Discord username (optional)
No response
Describe the bug
When attempting to start Warp, I get the following error:
To reproduce
warp-terminal
from aurwarp-terminal
Expected behavior
Warp starts normally
Screenshots
No response
Operating system
Linux
Operating system and version
Manjaro Linux, kernel v6.6.10
Shell Version
bash 5.2.21, zsh 5.9
Current Warp version
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
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
The text was updated successfully, but these errors were encountered: