Skip to content

Autoupdate issue #6532

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

Open
3 tasks done
mdziczkowski opened this issue May 27, 2025 · 2 comments
Open
3 tasks done

Autoupdate issue #6532

mdziczkowski opened this issue May 27, 2025 · 2 comments
Labels
Bugs Bugs, Hangs, Crash, and Freezes

Comments

@mdziczkowski
Copy link

Pre-submit Checks

Describe the bug

When starting Warp, I see a banner telling:

A new version of Warp is avaliable but cannot be installed

and requesting to do it manually

To reproduce

  1. launch warp in given version
  2. see the message

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

@mdziczkowski mdziczkowski added the Bugs Bugs, Hangs, Crash, and Freezes label May 27, 2025
@dannyneira
Copy link
Member

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:

sudo apt-get install wget gpg
wget -qO- https://releases.warp.dev/linux/keys/warp.asc | gpg --dearmor > warpdotdev.gpg
sudo install -D -o root -g root -m 644 warpdotdev.gpg /etc/apt/keyrings/warpdotdev.gpg
sudo sh -c 'echo "deb [arch=amd64 signed-by=/etc/apt/keyrings/warpdotdev.gpg] https://releases.warp.dev/linux/deb stable main" > /etc/apt/sources.list.d/warpdotdev.list'
rm warpdotdev.gpg
sudo apt update && sudo apt install warp-terminal

@mdziczkowski
Copy link
Author

mdziczkowski commented Jun 2, 2025

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

I think it's more clean ;-p

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bugs Bugs, Hangs, Crash, and Freezes
Projects
None yet
Development

No branches or pull requests

2 participants