Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Cannot use zsh in remote #1649

Open
3 tasks
Yefee opened this issue Dec 28, 2024 · 3 comments
Open
3 tasks

[Bug]: Cannot use zsh in remote #1649

Yefee opened this issue Dec 28, 2024 · 3 comments
Labels
bug Something isn't working triage Needs triage

Comments

@Yefee
Copy link

Yefee commented Dec 28, 2024

Current Behavior

After SSHing into the remote machine, the terminal defaults to using bash instead of zsh. The remote machine has WSH installed. The default SHELL is set to zsh and functions well in other terminals.

CleanShot 2024-12-28 at 11 19 52@2x

Expected Behavior

using zsh.

Steps To Reproduce

after connecting to remote machine, the terminal shows
process finished with exit code = -1

Wave Version

0.10.4 (202412210242)

Platform

macOS

OS Version/Distribution

macOS 15.2

Architecture

arm64

Anything else?

No response

Questionnaire

  • I'm interested in fixing this myself but don't know where to start
  • I would like to fix and I have a solution
  • I don't have time to fix this right now, but maybe later
@Yefee Yefee added bug Something isn't working triage Needs triage labels Dec 28, 2024
@esimkowitz
Copy link
Member

esimkowitz commented Dec 28, 2024

What type of remote are you connecting to? For Linux, we default to /bin/bash if we can't read your shell info out of /etc/passwd, do you have this file?

@Yefee
Copy link
Author

Yefee commented Dec 29, 2024

It is a cluster. We change our default SHELL in a web environment.

I am able to access the /etc/passwd

root:x:0:0:root:/root:/bin/bash
ldap:x:76:70:User for OpenLDAP:/var/lib/ldap:/bin/false
messagebus:x:499:499:User for D-Bus:/run/dbus:/usr/bin/false
wwwrun:x:498:497:WWW daemon apache:/var/lib/wwwrun:/usr/sbin/nologin
nobody:x:65534:65534:nobody:/var/lib/nobody:/bin/bash
man:x:13:62:Manual pages viewer:/var/lib/empty:/usr/sbin/nologin
mail:x:497:496:Mailer daemon:/var/spool/clientmqueue:/usr/sbin/nologin
lp:x:496:495:Printing daemon:/var/spool/lpd:/usr/sbin/nologin
daemon:x:2:2:Daemon:/sbin:/usr/sbin/nologin
bin:x:1:1:bin:/bin:/usr/sbin/nologin
srvGeoClue:x:495:480:User for GeoClue D-Bus service:/var/lib/srvGeoClue:/usr/sbin/nologin
mysql:x:60:60:MySQL database admin:/var/lib/mysql:/usr/sbin/nologin
at:x:25:25:Batch jobs daemon:/var/spool/atjobs:/usr/sbin/nologin
lldpd:x:494:479:LLDP daemon:/var/run/lldpd:/sbin/nologin
chrony:x:493:478:Chrony Daemon:/var/lib/chrony:/usr/sbin/nologin
systemd-network:x:476:476:systemd Network Management:/:/usr/sbin/nologin
systemd-timesync:x:475:475:systemd Time Synchronization:/:/usr/sbin/nologin
polkitd:x:474:474:User for polkitd:/var/lib/polkit:/sbin/nologin
scard:x:473:473:Smart Card Reader:/run/pcscd:/usr/sbin/nologin
systemd-coredump:x:472:472:systemd Core Dumper:/:/usr/sbin/nologin
munge:x:471:471:MUNGE authentication service:/run/munge:/usr/sbin/nologin
named:x:44:44:Name server daemon:/var/lib/named:/usr/sbin/nologin
sshd:x:470:470:SSH daemon:/var/lib/sshd:/usr/sbin/nologin
svn:x:469:469:user for Apache Subversion svnserve:/srv/svn:/usr/sbin/nologin
rpc:x:467:65534:user for rpcbind:/var/lib/empty:/sbin/nologin
statd:x:466:65533:NFS statd daemon:/var/lib/nfs:/sbin/nologin
dhcpd:x:465:65533:DHCP server daemon:/var/lib/dhcp:/bin/false
vnc:x:464:466:user for VNC:/var/lib/empty:/sbin/nologin
gdm:x:463:463:Gnome Display Manager daemon:/var/lib/gdm:/usr/sbin/nologin
nvidia-persistenced:x:985:208:nvidia-persistenced service account:/home/nvidia-persistenced:/sbin/nologin
cmk-agent:x:462:462:Checkmk agent system user:/var/lib/cmk-agent:/bin/false

Can I manually set the shell in certain configuration files?

@oneirocosm
Copy link
Member

We haven't added remote shells to configuration files, but i don't think it would be that hard to do. I'll see if I can get a PR open for that, at least as a workaround.

Otherwise, do you know what is being used to set the SHELL variable for you? I have personally always used the chsh command which changes the value in the /etc/passwd file, but if you have it set up a different way, it would be great for us to be able to support it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working triage Needs triage
Projects
None yet
Development

No branches or pull requests

3 participants