Can't reset local shell on new install

[officiallymarky]

Describe the bug
Downloaded AppImage for Linux, immediately unable to do do anything as it requests I reset the shell, but it fails trying to find .cargo/env which does not exist.

To Reproduce
Steps to reproduce the behavior:
Download AppImage, run.

Expected behavior
Use terminal

Screenshots

Desktop (please complete the following information):
PikaOS (Ubuntu Spin) 3

Additional context
New install.

[glexposito]

I am having the same issue on Fedora 40 (rpm package)

[glexposito]

Fedora 40, rpm package, new install

Steps to reproduce:

• Download and install rpm package from web
• Run Wave
• Connect to local[{user}@{host}] or run reset command

Error:

error: error reinitializing remote: error initializing shell: cannot parse bash declare output: bash-declare-output:6:2049: - must be followed by an expression
ocal[{user}@{host}] or run reset command

Error:

error: error reinitializing remote: error initializing shell: cannot parse bash declare output: bash-declare-output:6:2049: - must be followed by an expression

Additional notes:
It works when I connect to sudo[sudo@{user}@{host}]

Please note that "user" and "host" are just variables. For my desktop, they are displayed as local[guille@fedora] and sudo[sudo@guille@fedora].

[trashyms]

Hello.
I just discovered the app. Wanted to try and see. But ...
I am having the same problem on macos monterey 12.7.5
Any idea for a solution?
Thanks in advance.

[antogg]

Hello. I just discovered the app. Wanted to try and see. But ... I am having the same problem on macos monterey 12.7.5 Any idea for a solution? Thanks in advance.

This could be related to #710?
I was having the same problem on MacOS Sonoma and commenting the Amazon-Q entries in .zshrc and .zprofile allows WaveTerm to finally start

[ZaLiTHkA]

just discovered Wave Terminal just now, but I'm stuck at this same issue..

in my case, all I get is the following:

FWIW: I do have a heavily customised .bashrc file though.. I've replaced it's contents with a loop that loads all sh files from a custom ~/.bashrc-parts directory, which is where I define all my shell configuration.

just to test, I disabled this "source loop" and then Wave started a new terminal session with no issue at all. then I copied over some of my explicit tool config into .bashrc directly and Wave still worked perfectly.

but the moment I try and "source" any other file from inside .bashrc, Wave fails to start a new terminal session.

---

This could be related to #710? I was having the same problem on MacOS Sonoma and commenting the Amazon-Q entries in .zshrc and .zprofile allows WaveTerm to finally start

also just to note: I do not have Amazon-Q, so I highly doubt these issues are related.

[ZaLiTHkA]

I also just tried launching Wave from a different terminal session, which does show some "startup logging", but no errors are shown when this issue comes up..

is there any way to run Wave with additional logging output? I tried --verbose and --debug arguments, but neither seemed to do anything.