Shell on remote server will not load

Open
#1,922 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
bash, linux, macos

Research direction

Start by reproducing the SSH connection from macOS 12.6 to the TurrisOS 5.4.4 server using the reported shell versions, then inspect the included bash xtrace output. Done means the remote shell bootstraps successfully and commands such as od, whoami, and hostname are available.

Written by the indexing model from the issue text.

Description

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

No response

Local Shell and Version

5.9

Remote Shell and Version

5.0.17(1)-release

Operating System and Version

Local - MacOS 12.6; remote - TurrisOS 5.4.4

Warp Version

v0.2022.09.27.08.11.stable_00

I have tried commenting out my system & user rcfiles and warp still will not bootstrap
  • Yes
Screenshots
HsCLO

When logging on to my remote server using ssh, it would complete all the way to the end of the authentication process, but shell wouldn't start, resulting in what you see in the screenshot.

LocalForward set up for this remote server works though, even though I can't get to the shell

Include shell xtrace output

Host key fingerprint is SHA256:j1hT4AWYe2Ok3TzNAsFGCocT81K8RAtJWBKgJRmK/B4
+--[ED25519 256]--+
|+++=B*+==o. |
|*o..+B=+=o |
|+. .o+B.+.o |
| . .+ =.= o |
| E oS. o |
| . . o + |
| . . . . |
| |
| |
+----[SHA256]-----+
bash: line 1: od: command not found
bash: line 1: whoami: command not found
bash: line 1: hostname: command not found

  • set -o vi
  • set +o vi
  • HISTCONTROL=ignorespace
  • printf '
Warp Internal (ignore) - linear-label:e7dfaa84-5fdb-4a00-b754-d8912da923fa

No response

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.