Strider does not work on MacOS Sonoma 14.2.1

[jigypeper]

Issues with the Zellij UI / behavior / crash

Issue description

Cannot run strider plugin.

Minimal reproduction

Steps:

1. install zellij via 'brew install zellij'
2. run 'zellij -l strider'
3. crashes with 'Received empty message from server'

Other relevant information

I think it's just a strider issue. Tried on wsl2 with work laptop and had no issues, very odd and frustrating.

[jimmyjansen93]

yup can confirm, I have the same problem.

[mbhutton]

Same with macOS Ventura lastest (13.6.3) with lasted zellij (0.39.2).

zellij --layout compact always works, zellij --layout strider always exits within about 200ms with Received empty message from server.

zellij -d --layout strider shows no additional output.

Possibly related issue: #2170

Deleting the caches as suggested in that issue does not work as a workaround.

[bowentan]

Same issue here. Loading each plugin I got ran into a crash with message Received empty message from server.

[devsecopshomelearning]

Getting this issue also, issue is present in all three scenarios: Homebrew: homebrew install zellij Cargo: cargo install --locked zellij Try Zellij Without Installing: bash <(curl -L zellij.dev/launch)

The following are ways I attempted to load the strider layout resulting in zellij crashing and displaying the message: Received empty message from server

Method 1, external from a zellij session: zellij --layout strider Method 2, within a zellij session: zellij action new-pane --plugin zellij:strider

Version: zellij 0.39.2 Hardware: Apple M3 Pro Sonoma 14.3 (arm64)

[devsecopshomelearning]

I just tested Zellij 0.38.2 and the issue is not present in that version. Strider loaded with no issues right away.

[jigypeper]

I've just tried the 0.38.2 binary and strider seems to work fine on that one...

[mbhutton]

Appears to be fixed in the newly released 0.40.0 on my Sonoma system. Was failing with Zellij 0.39.2, but now works fine.

[jigypeper]

Really! I'll give that a shot tonight. 🤞

[jigypeper]

0.40.0 does appear to fix this issue :)