zoxide: unsupported version (got 0, supports 3)

[JRJacoby]

Hi all, I'm receiving a warning/error every time I use z to change directories:

yoda[0]:~$ z /space/yoda/2/users/datasets/AABC_data_freeze_1/
zoxide: unsupported version (got 0, supports 3)
yoda[0]:AABC_data_freeze_1$ z
zoxide: unsupported version (got 0, supports 3)
yoda[0]:~$

It also happens with 'cd' when zoxide is installed:
yoda[0]:~$ cd /space/yoda/2/users/datasets/AABC_data_freeze_1/
zoxide: unsupported version (got 0, supports 3)

It doesn't happen when changing to the directory I'm already in:
yoda[0]:AABC_data_freeze_1$ cd /space/yoda/2/users/datasets/AABC_data_freeze_1/
yoda[0]:AABC_data_freeze_1$ z /space/yoda/2/users/datasets/AABC_data_freeze_1/
yoda[0]:AABC_data_freeze_1$

An exact-string Google search reveals only one other issue that mentions this: #807

The poster was able to fix the issue by deleting their database, but for me even a complete uninstall-reinstall did not fix the issue.

[levibeeching]

I have same issue on zoxide 0.9.4
It worked beautifully for months.
Now it is broken. I also tried deleting db.zo. This made no difference

[share]$ cd .
/home/110/ljb110/.local/share
[share]$ cd ..
/home/110/ljb110/.local
zoxide: unsupported version (got 0, supports 3)
[.local]$ cd -
/home/110/ljb110/.local/share
zoxide: unsupported version (got 0, supports 3)
[share]$ cd ~
/home/110/ljb110
zoxide: unsupported version (got 0, supports 3)
[~]$

db.zo only is 110bytes and does not get bigger as I would expect.
Please help. This is a wonderful tool.

[levibeeching]

Note: I am using bash on Rocky Linux.

\LSB Version: :core-4.1-amd64:core-4.1-noarch
Distributor ID: Rocky
Description: Rocky Linux release 8.10 (Green Obsidian)
Release: 8.10
Codename: GreenObsidian

[kmkurn]

I had the same issue, and it was because my disk had no more free space. Deleting some large files fixed it in my case.

[levibeeching]

Thanks @kmkurn !!!!
It was a weird space issue. I emptied the Trash folder that is also in ~/.local/Share/ and it now all works again.
It looks like it was getting to 100bytes then breaking. This was enough to hold about 2 entries in the database.
I am running on a supercomputer account that must have limits on certain directories. I had some stupidly big files sitting in the Trash folder.
I would have never have found this issue, so thank you.

[kmkurn]

Glad that it worked for you too @levibeeching. I was also running it on a HPC server with a disk quota. A more accurate error message would be really helpful here.