zellij: ERROR IN PLUGIN - check logs for more info - v0.41.0
2. Issues with the Zellij UI / behavior / crash
Issue description
After update from prev version I get ERROR IN PLUGIN - check logs for more info when zellij starts, with default config.
ERROR IN PLUGIN - check logs for more info
┌ status-bar ───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
│Loading status-bar... │
│Attempting to load from memory... NOT FOUND │
│Attempting to load from cache... NOT FOUND │
│Compiling WASM │
│ERROR: failed to start plugin 1 for client 1 │
│ │
│Caused by: │
│ 0: failed to recover cache dir │
│ 1: WebAssembly translation error │
│ 2: Invalid input WebAssembly code at offset 712955: reference-types not enabled: zero byte expected │
│ERROR IN PLUGIN - check logs for more info
Minimal reproduction
- remove all configs for zellij
- start zellij (without any parameter)
Other relevant information
- using https://github.com/zellij-org/zellij/releases/download/v0.41.0/zellij-x86_64-unknown-linux-musl.tar.gz
- zellij is in
/usr/local/bin - PopOS running on Intel CPU
- terminal is wezterm, but the same happens in other terminals
Distributor ID: Pop
Description: Pop!_OS 22.04 LTS
Release: 22.04
Codename: jammy
How can I find the logs with the error?
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 7
- Comments: 15 (9 by maintainers)
Can confirm this fixes it for me locally - thanks for the super quick assist! Trying to figure out a way to place these binaries in the release.
EDIT: workaround for now is to compile from source:
cargo install zellij --locked- apologies for the inconvenience. Working on fixing this ASAP.Thanks for the super quick report @pdanpdan and others. And @bjorn3 for the assist. Looks like the root cause was our CI ignoring the rust-toolchain for some reason. The explicit
gcwasmtime feature fix from @bjorn3 did the trick - thanks again.To others: this is fixed in the 0.41.1 patch.
Clearing cache changes nothing. Log:
same/similar on macOs (ARM), install via pre-built binaries:
Update: I nuked the cache, still no joy