Open orome opened 4 months ago
Hi @orome, thanks for filing and sorry for the issues you're experiencing in Warp.
A few questions: 1) Could you send us the output of your Warp logs so we can debug further? https://docs.warp.dev/help/sending-us-feedback#gathering-warp-logs 2) Does this repro with an empty bashrc/bashprofile ? Running theory may be that there's something in your RC file that is preventing Warp from being able to successfully start.
Thanks for the quick reply!
.bashrc
and .bash_profile
but still get the same messageThanks! One more thing, if you don't mind.
Could you run:
defaults write dev.warp.Warp-Stable ShouldShowBootstrapBlock true
in another terminal, reopen Warp, and send a screenshot of what you see?
Lots of >
removed (where below are ...
):
bash-5.2$
>
>
bash-5.2$
bash-5.2$
bash-5.2$
>
>
>
>
>
>...
>
>
>
>
>
>
>
bash: syntax error near unexpected token `if'
bash-5.2$
bash: __bp_set_ret_value: command not found
bash-5.2$
bash: : command not found
bash-5.2$
bash: syntax error near unexpected token `fi'
bash-5.2$
bash: syntax error near unexpected token `done'
bash-5.2$
bash: __bp_set_ret_value: command not found
bash-5.2$
bash: syntax error near unexpected token `}'
bash-5.2$
>
>
bash-5.2$
>
>
>
>
>
>
>
bash: syntax error near unexpected token `__bp_trim_whitespace'
bash-5.2$
>
>
bash: return: can only `return' from a function or sourced script
bash-5.2$
bash: syntax error near unexpected token `done'
bash-5.2$
bash: return: can only `return' from a function or sourced script
bash-5.2$
bash: syntax error near unexpected token `}'
bash-5.2$
>
>
...
>
>
bash: syntax error near unexpected token `fi'
bash-5.2$
bash: local: can only be used in a function
bash-5.2$
>
>
>
bash-5.2$
>
>
bash-5.2$
bash: local: can only be used in a function
bash-5.2$
bash: local: can only be used in a function
bash-5.2$
bash: local: can only be used in a function
bash-5.2$
>
bash: syntax error near unexpected token `if'
bash-5.2$
bash-5.2$
bash: : command not found
bash-5.2$
bash-5.2$
>
>
bash-5.2$
bash: syntax error near unexpected token `fi'
bash-5.2$
bash: syntax error near unexpected token `done'
bash-5.2$
bash-5.2$
bash: syntax error near unexpected token `}'
bash-5.2$
>
>
...
>
>
>
>
>
bash-5.2$
>
>
>
>
>
>
>
>
bash-5.2$
bash: syntax error near unexpected token `}'
bash-5.2$
>
>
>
>
bash-5.2$
>
>
>
>
>
>
>
>
...
>
>
bash-5.2$
bash-5.2$ eval "$WARP_BOOTSTRAP_VAR" unset WARP_BOOTSTRAP_VAR
bash: syntax error near unexpected token `fi'
bash-5.2$
Note that neither WARP_BOOTSTRAP_VAR
nor __bp_trim_whitespace
are present in my .bashrc
or .bash_profile
.
Thanks for all of your patience and help debugging; I've never seen this before and I'm still trying to parse what could be happening.
Does this repro with other shells? i.e. zsh (/bin/zsh
) or bash 3.2 (/bin/bash
)?
You can change the default shell in Settings
/bin/zsh
works, /bin/bash
does not (my default, used above, is /opt/homebrew/bin/bash
)
Do you have anything in /etc/profile
, ~/.bash_login
or /.profile
?
/etc/profile
# System-wide .profile for sh(1)
if [ -x /usr/libexec/path_helper ]; then
eval `/usr/libexec/path_helper -s`
fi
if [ "${BASH-no}" != "no" ]; then
[ -r /etc/bashrc ] && . /etc/bashrc
fi
~/.bash_login
#!/usr/bin/env bash
# Script to be executed on login by /bin/bash if .bash_profile is not present
echo "Running .bash_login..."
printf "`date`:\tLogin to bash: executing ~/.bash_login...\n" >> ~/Library/Logs/Mine/bash.log
~/.profile
#!/usr/bin/env bash
# Script to be executed on login by /bin/sh; or by /bin/bash if .bash_profile and .bash_login are not present
echo "Running .profile..."
printf "`date`:\tLogin to bash: executing ~/.profile...\n" >> ~/Library/Logs/Mine/bash.log
This persists after updating to:
@alokedesai This persists after updating to:
Rebooting (and even updating macOS, to 14.6.1) doesn't fix it either.
Hey @orome, thanks for your patience here. It's still not exactly clear to me what's happening.
Would you be open to trying out a special version of Warp that includes extra logging about what the shell sends back to Warp so we can try to trace it down?
Thd built would write out all of the contents it receives from the shell into a warp.pty.recording
file, which you could then email to me to help us debug.
@alokedesai Sure. I'll give it a shot.
This persists with v0.2024.08.27.08.02.stable_02
@alokedesai This persists with v0.2024.09.03.08.02.stable_03
@alokedesai This persists with v0.2024.09.17.08.02.stable_01
@alokedesai This persists with v0.2024.09.24.08.02.stable_01
@alokedesai This persists with v0.2024.10.23.14.49.stable_00
@alokedesai This persists with v0.2024.11.12.08.02.stable_02
@alokedesai This persists with v0.2024.11.19.08.02.stable_03
Dupe Check
Describe the bug
I can't even start. I just get "seems like your shell is taking a while to start"
To reproduce
Expected behavior
Warp stars bash
Screenshots
No response
Operating system
MacOS
Operating system and version
Version 14.6 (23G80) - 15.1.1 (24B91)
Shell Version
Bash 5.2.26(1)-release (aarch64-apple-darwin23.2.0) - 5.2.37(1)-release (aarch64-apple-darwin24.0.0)
Current Warp version
v0.2024.07.23.08.02.stable_01 - This persists with
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 an issue only in Warp?
Yes, I confirmed that this only happens in Warp, not other terminals.
Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e
None