SSH wrapper hangs at "Starting shell..."

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
bash, linux, zsh
Domain
cli, networking

Research direction

No source file, test, or entry point is identified in the report; start by reproducing the SSH connection with the supplied Zsh, Bash, Ubuntu, and Warp versions and inspect where startup stops after the xtrace output. Done means the SSH wrapper reaches an interactive shell instead of hanging at “Starting shell...”.

Written by the indexing model from the issue text.

Description

area:ssh bug needs-info ready-to-implement SSH triaged
Discord username (optional)

No response

Local Shell and Version

Zsh 5.8.1

Remote Shell and Version

Bash 4.4.20(1)-release

Operating System and Version

Ubuntu 18.04.5 LTS

Warp Version

v0.2023.01.24.08.03.stable_01

I have tried commenting out my system & user rcfiles and warp still will not bootstrap
  • Yes
Screenshots
image
Include shell xtrace output
+ '[' -z '\s-\v\$ ' ']'
+ shopt -s checkwinsize
+ '[' -z '' ']'
+ '[' -r /etc/debian_chroot ']'
+ '[' -n '' -a -n '' ']'
+ PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w\$ '
+ '[' '!' -e /home/<retracted>/.sudo_as_admin_successful ']'
+ '[' -x /usr/lib/command-not-found -o -x /usr/share/command-not-found/command-not-found ']'
+ set -o vi
+ set +o vi
+ HISTCONTROL=ignorespace
+ HISTIGNORE=' *'
+ printf '
Does this block you from using Warp daily?

No

Warp Internal (ignore) - linear-label:e7dfaa84-5fdb-4a00-b754-d8912da923fa

None

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.