warpdotdev / warpdotdev/warp

Warp terminal launch stuck at the first time

Open
#4,543 8 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area:terminal-input bug ready-to-implement triaged
Dominant language
Rust
Stars
65.1k
Forks
5.6k
PR merge metrics
PR metrics pending

Description

Discord username (optional)

No response

Describe the bug

Dear all,
It's my first time using warp. I just downloaded it from website and installed it. However, it stuck forever when I try to launch it.

To reproduce
  1. download 0.2024.03.05.08.02stable.01.01_amd64.deb from website
  2. run apt install 0.2024.03.05.08.02stable.01.01_amd64.deb in the folder and wait for it finish.
  3. launch it and stuck.

Sorry for the picture, there is something wrong with my ubuntu screenshoot. But you can clearly see there is a "warp" inthe middle which get stuck in launch.
IMG_20240312_163201

Expected behavior

I just wanted to launch it.

Screenshots

No response

Operating system

Linux

Operating system and version

Ubuntu 20.04

Shell Version

zsh5.8; I also tried with bash, no difference.

Current Warp version

0.2024.03.05.08.02stable.01.01

Regression

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

Recent working Warp date

never

Additional context

I remember when I reinstall it, the terminal shows something like "repository is broken“ but I failed to save that information.

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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the launch failure with the 0.2024.03.05.08.02stable.01.01_amd64.deb package on Ubuntu 20.04, using the reported apt installation steps. Inspect the launch and installation diagnostics, including the reported broken-repository message. Done means identifying the cause and confirming that Warp launches successfully after the fix.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux, rust
Domain
cli, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.