Open sebastiancarlos opened 1 year ago
I have the same issue
(although my Serde
message warns about a "trailing characters" in a different column number :/)
@sebastiancarlos downgrading, then rebooting did the trick for me.
The code that is in the stack trace points to loading of a status-bar-tips.cache
file. from the code, I seem to find that it should be in /tmp
https://github.com/zellij-org/zellij/blob/204c41e63f5a134e2f371ee56e0fb29acea64672/default-plugins/status-bar/src/tip/consts.rs#L1
however I have no such file in /tmp
nor does the error change if I create one and put garbage inside.
ok, so it's because /tmp
goes to $TMPDIR/zellij-xxx
. I found the file. I'm going to do a few tests
well, I'm not reproducing the issue.
@sebastiancarlos I suspect that this cache file got some inconsistent data at some point the last time you executed zellij and it prevents it from restarting.
find the file inside $TMPDIR
in the zellij folder that is called status-bar-tips.cache
and delete it. that should do the trick
You could also try to empty ~/.cache/zellij/
...
Removing the status-bar-tips.cache fixed the issue for me.
echo $TMPDIR
rm /<tmpdir>/zellij-<number>/status-bar-tips.cache
I just had this issue right now, and yup, aparrently the status-bar-tips.cache
file got corrupted at some point yesterday in my machine but idk why or how.
My status-bar-tips.cache
file for reference:
{"zellij_version":"0.36.0","cached_data":{"floating_panes_mouse":1,"edit_scrollbuffer":1,"zellij_setup_check":1,"sync_tab":1,"move_focus_hjkl_tab_switch":1,"compact_layout":1,"use_mouse":1,"quicknav":2}}inal":1,"floating_panes_mouse":1}}
For me it was as easy as removing the last corrupted portion of the file:
inal":1,"floating_panes_mouse":1}}
Error on running
zellij
. (It got fixed after system reboot, so feel free to close)Logs:
Basic information
zellij --version
: zellij 0.36.0stty size
: 45 178uname -av
orver
(Windows): Darwin XXX 21.6.0 Darwin Kernel Version 21.6.0: Thu Mar 9 20:08:59 PST 2023; root:xnu-8020.240.18.700.8~1/RELEASE_X86_64 x86_64Further information no custom layout, no custom config. it happened randomly after trying to change som keybindings, but problem persists after restoring original.