warp unable to start a shell, displays "Seems like your shell takes a while to start"

Open
#3,931 9 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
bash, macos, rust
Domain
cli, desktop

Research direction

The report names no source file, test, or entry point; begin by reproducing startup on macOS 12.6.3 with GNU bash 3.2.57. Done means Warp starts bash normally without displaying the delay message, while behavior in Terminal or iTerm remains unaffected.

Written by the indexing model from the issue text.

Description

area:shell-terminal bug ready-to-implement triaged
Discord username (optional)

No response

Describe the bug

On startup, warp attempts to start bash, but apparently does not succeed. After few seconds, message "Seems like your shell takes a while to start" is displayed.

To reproduce

Just start warp

Expected behavior

No response

Screenshots

image

Operating system

MacOS

Operating system and version

Monterey v12.6.3

Shell Version

GNU bash, version 3.2.57(1)-release (x86_64-apple-darwin21)

Current Warp version

v0.2023.11.28.08.02

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:b8107fdf-ba31-488d-b103-d271c89cac3e

None

Dominant language
Rust
Stars
65.1k
Forks
5.6k
PR merge metrics
PR metrics pending

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.

More from warpdotdev/warp

All issues in warpdotdev/warp

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.