SSH does not seem to use .profile on DSM

Discord username (optional)

joggienl

Operating System

MacOS

Operating System and Version

14.2

Local Shell Version

ZSH: 5.9

Remote Shell Version

Bash: 4.4.23(1)-release

Warp Version

v0.2023.12.12.08.02.stable_04

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

• Yes

Screenshots

I have a ~/.profile on my Synology NAS, running DSM version DSM 7.2.1-69057 Update 3.
Using a .profile file is the way to change the user shell when login via ssh and not using the default /bin/sh.

This is the content of ~/.profile

# synology - uses /bin/sh, should reload to /bin/bash
if [  "$SHELL" == "/bin/sh" -a -x /bin/bash ]; then
    export SHELL=/bin/bash
    exec /bin/bash --login
fi

Login via iTerm or regular Terminal.app works as expected, login via Warp ends up with /bin/sh.

You can opt out of this functionality by invoking /usr/bin/ssh directly.
Using the method to not use the ssh wrapper from this page works: https://docs.warp.dev/features/ssh#implementation

A screenshot:

Include shell xtrace output

There is no output.

Does this block you from using Warp daily?

No

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:e7dfaa84-5fdb-4a00-b754-d8912da923fa

None

Warp Internal (ignore): linear-label:b8107fdf-ba31-488d-b103-d271c89cac3e

None

Start with the SSH implementation described at https://docs.warp.dev/features/ssh#implementation and reproduce the DSM 7.2.1 behavior using the supplied ~/.profile. Compare Warp's SSH path with invoking /usr/bin/ssh directly; done means the profile is honored in Warp as it is in iTerm and Terminal.app.