You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @mdziczkowski sorry about this issue. This typically happens when Warp cannot auto-update due to one of the following reasons:
The package repository is not set up correctly, so apt cannot find the latest version.
The installed package is outdated, and the update mechanism cannot fetch or apply the new version.
There may be permission issues or a mismatch between the installed package name and the one Warp expects (for example, the package name changed from warp to warp-terminal).
The recommended solution is to manually add the Warp repository and update the package. Here’s how you can do it:
Hello. I have the gpg and repository correctly set-up. However, instead of the ".list" file format (the one You gave), it's easier for me to use the ".sources" format because it's make the management easier.
In this format, the given by You entry would look following:
Types: deb
URIs: https://releases.warp.dev/linux/deb
Suite: stable
Components: main
Signed-By: /etc/apt/keyrings/warpdotdev.gpg
Arch: amd64
Pre-submit Checks
Describe the bug
When starting Warp, I see a banner telling:
and requesting to do it manually
To reproduce
Expected behavior
No response
Screenshots, videos, and logs
No response
Operating system (OS)
Linux
Operating system and version
Debuan - derriative of Debian (bookworm)
Shell Version
No response
Current Warp version
No response
Regression
Yes, this bug started recently or with an X Warp version
Recent working Warp date
No response
Additional context
No response
Does this block you from using Warp daily?
No
Is this an issue only in Warp?
Yes, I confirmed that 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: