Skip to content

Yazi snap ships too old fzf #2731

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
3 tasks done
thriveth opened this issue May 6, 2025 · 2 comments
Open
3 tasks done

Yazi snap ships too old fzf #2731

thriveth opened this issue May 6, 2025 · 2 comments
Labels
bug Something isn't working good first issue Good for newcomers help wanted Extra attention is needed

Comments

@thriveth
Copy link

thriveth commented May 6, 2025

What system are you running Yazi on?

Linux X11

What terminal are you running Yazi in?

kitty v. 0.35.2

yazi --debug output

Yazi
    Version: 25.4.8 (99ea3b74 2025-04-08)
    Debug  : false
    Triple : x86_64-unknown-linux-gnu (linux-x86_64)
    Rustc  : 1.86.0 (05f9846f 2025-03-31)

Ya
    Version: No such file or directory (os error 2)

Emulator
    TERM                : Some("xterm-kitty")
    TERM_PROGRAM        : None
    TERM_PROGRAM_VERSION: None
    Brand.from_env      : Some(Kitty)
    Emulator.detect     : Emulator { kind: Left(Kitty), light: false, cell_size: Some((10, 21)) }

Adapter
    Adapter.matches    : Kgp
    Dimension.available: WindowSize { rows: 67, columns: 154, width: 1540, height: 1407 }

Desktop
    XDG_SESSION_TYPE           : Some("x11")
    WAYLAND_DISPLAY            : None
    DISPLAY                    : Some(":0")
    SWAYSOCK                   : None
    HYPRLAND_INSTANCE_SIGNATURE: None
    WAYFIRE_SOCKET             : None

SSH
    shared.in_ssh_connection: false

WSL
    WSL: false

Variables
    SHELL           : Some("/bin/zsh")
    EDITOR          : Some("nvim")
    VISUAL          : Some("nvim")
    YAZI_FILE_ONE   : None
    YAZI_CONFIG_HOME: None
    YAZI_ZOXIDE_OPTS: None
    FZF_DEFAULT_OPTS: None

Text Opener
    default     : Some(OpenerRule { run: "nvim \"$@\"", block: true, orphan: false, desc: "", for_: None, spread: true })
    block-create: Some(OpenerRule { run: "nvim \"$@\"", block: true, orphan: false, desc: "", for_: None, spread: true })
    block-rename: Some(OpenerRule { run: "nvim \"$@\"", block: true, orphan: false, desc: "", for_: None, spread: true })

Multiplexers
    TMUX               : false
    tmux version       : No such file or directory (os error 2)
    tmux build flags   : enable-sixel=Unknown
    ZELLIJ_SESSION_NAME: None
    Zellij version     : 0.16.0

Dependencies
    file          : 5.44
    ueberzugpp    : No such file or directory (os error 2)
    ffmpeg/ffprobe: ExitStatus(unix_wait_status(32512)), "ffmpeg: error while loading shared libraries: libxcb-present.so.0: cannot open shared object file: No such file or directory\n" / ExitStatus(unix_wait_status(32512)), "ffprobe: error while loading shared libraries: libxcb-present.so.0: cannot open shared object file: No such file or directory\n"
    pdftoppm      : 24.02.0
    magick        : ExitStatus(unix_wait_status(32512)), "magick: error while loading shared libraries: libgomp.so.1: cannot open shared object file: No such file or directory\n"
    fzf           : 0.44.1
    fd/fdfind     : 9.0.0 / 8.6.0
    rg            : 14.1.0
    chafa         : 1.14.0
    zoxide        : 0.9.3
    7zz/7z        : 23.01 / 16.02
    jq            : 1.5

Clipboard
    wl-copy/paste: 2.2.1 / 2.2.1
    xclip        : 0.13
    xsel         : 1.2.0

Routine
    `file -bL --mime-type`: text/plain


See https://yazi-rs.github.io/docs/plugins/overview#debugging on how to enable logging or debug runtime errors.

Describe the bug

The latest Snap build of Yazi ships wit fzf version 0.44, which according to the documentation is too old, and leads to the bug with the zoxide dialogs not showing up.

I have fzf v. 0.62 installed in my path, but the Snap build uses the shipped version.

Minimal reproducer

Install yazi using sudo snap install yazi, open yazi and press z or Z.

Anything else?

I haven't actually tried the latest nightly build, given that this is about a specific different build. Still, I have made sure that this is the latest version of the Snap build.

Checklist

  • I tried the latest nightly build, and the issue is still reproducible
  • I updated the debug information (yazi --debug) input box to the nightly that I tried
  • I can reproduce it after disabling all custom configs/plugins (mv ~/.config/yazi ~/.config/yazi-backup)
@thriveth thriveth added the bug Something isn't working label May 6, 2025
Copy link

github-actions bot commented May 6, 2025

Hey @thriveth, I noticed that you did not correctly follow the issue template. Please ensure that:

  • The bug can still be reproduced on the newest nightly build.
  • The debug information (yazi --debug) is updated for the newest nightly.
  • The non-optional items in the checklist are checked.

Issues with needs info will be marked ready once edited with the proper content, or closed after 2 days of inactivity.

@sxyazi
Copy link
Owner

sxyazi commented May 7, 2025

It seems that the Snap build is using the version from the Snap store here:

Maybe the version of fzf in the Snap store is too old. In this case, ideally, it would be best to update it in the Snap store so that Yazi can use the updated version, if that isn't possible, maybe we can package it together in the Snap with Yazi.

Since I'm not familiar with snap — I don't use it myself, I'll add a "help wanted" label and count on the community to help with this.

@sxyazi sxyazi added help wanted Extra attention is needed good first issue Good for newcomers and removed needs info labels May 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants