Sideband immediately quits at launch with no error message

[xa4hf8]

M1 Mac
Mac OS Sequoia 15.1.1
Python 3.12.1
Sideband 1.2

admin console log

assistant analysis

[markqvist]

Is this running from Sideband.app provided in the dmg file, or installed via pip?

[markqvist]

If it is running from the app package, could you try launching it via the terminal, and see if any additional error messages are output? Open a terminal, cd to the directory that the Sideband.app package is stored in, and run:

./Sideband.app/Contents/MacOS/Sideband

There may be additional error messages there, that can shed some light on what is going on.

[xa4hf8]

./Sideband.app/Contents/MacOS/Sideband

There may be additional error messages there, that can shed some light on what is going on.

I should have thought of that before reporting: turns out that it does not like the space in the path name.
Sorry for the trouble.

% ./Sideband
/Applications/Conferencing/Wireless off-grid/Reticulum/Sideband.app/Contents/Resources/script: line 10: cd: /Applications/Conferencing
off-grid/Reticulum/Sideband.app/Contents/Resources: No such file or directory
/Applications/Conferencing/Wireless off-grid/Reticulum/Sideband.app/Contents/Resources/script: line 13: pushd: /Applications/Conferencing
off-grid/Reticulum/Sideband.app/Contents/Resources/venv/bin: No such file or directory
/Applications/Conferencing/Wireless off-grid/Reticulum/Sideband.app/Contents/Resources/script: line 15: activate: No such file or directory
/Applications/Conferencing/Wireless off-grid/Reticulum/Sideband.app/Contents/Resources/script: line 50: exec: python: not found

[liamcottle]

Can confirm it also crashes for me with similar error messages when launching Sideband.app by either double clicking, or running via CLI when a parent directory contains a space.

I'd say it's probably best to move it to /Applications/Sideband.app.

[markqvist]

Aha! So that's what's happening. Good catch. It occurs because the process needs to change working directory into the virtual python environment included in the app, but for some reason can't handle spaces in the name then.

I'll see if I can implement a workaround in the next release.

[markqvist]

Ok, to investigate, I just launched a fresh macOS Sequoia instance running on Mac M1 hardware via EC2, and downloaded and installed the latest Sideband release. Everything runs as intended.

It could be that you simply have errors in your Reticulum configuration file, that prevents startup. Or a bit more unlikely, that you've upgraded from a very old version of Sideband, and the new version can't properly migrate database version and configuration files from that old version.

In that case, you can try moving the existing Sideband configuration folder (~/.config/sideband) to a backup location, which will make Sideband re-initialise config and database files on startup. If that works, you will have to manually import your old encryption key into the new config folder to use your existing address.

Moving this to the forums, since it currently does not appear to be an issue.

[liamcottle]

Working for me on:

• Sideband v1.2.0
• macOS Sonoma 14.2.1 (23C71)
• 2019 MacBook Pro, Intel

I don't have an M1 Mac, nor Mac OS Sequoia 15.x install to test with

[markqvist]

Thanks!