yazi 0.4.1-1 not works in arch linux

[siuyutpang]

What system are you running Yazi on?

Linux X11

What terminal are you running Yazi in?

kitty v0.37.0-1

yazi --debug output

Yazi
    Version: 0.4.1 (Arch Linux 2024-12-19)
    Debug  : false
    Triple : x86_64-unknown-linux-gnu (linux-x86_64)
    Rustc  : 1.83.0 (90b35a62 2024-11-26)

Ya
    Version: 0.4.1 (Arch Linux 2024-12-19)

Emulator
    Brand.from_env      : Some(Kitty)
    Emulator.detect     : Emulator { kind: Left(Kitty), light: false, cell_size: Some((13, 32)) }
    Emulator.detect_full: Ok(Emulator { kind: Left(Kitty), light: false, cell_size: Some((13, 32)) })

Adapter
    Adapter.matches: Kgp

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

SSH
    shared.in_ssh_connection: false

WSL
    WSL: false

NVIM
    NVIM          : false
    Neovim version: 0.10.2

Variables
    SHELL           : Some("/usr/bin/zsh")
    EDITOR          : Some("nvim")
    VISUAL          : None
    YAZI_FILE_ONE   : None
    YAZI_CONFIG_HOME: None
    YAZI_ZOXIDE_OPTS: None
    FZF_DEFAULT_OPTS: Some(" --height 40% --border --reverse --inline-info --pointer=👉 --border --color=dark\n--color=fg:-1,bg:-1,hl:#5fff87,fg+:-1,bg+:-1,hl+:#ffaf5f\n--color=info:#af87ff,prompt:#5fff87,pointer:#ff87d7,marker:#ff87d7,spinner:#ff87d7\n")

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

Multiplexers
    TMUX               : 0
    tmux version       : tmux 3.5a
    tmux build flags   : enable-sixel=Unknown
    ZELLIJ_SESSION_NAME: None
    Zellij version     : 0.41.2

Dependencies
    file          : 5.46
    ueberzugpp    : 2.9.6
    ffmpeg/ffprobe: 7.1 / 7.1
    pdftoppm      : 24.11.0
    magick        : 7.1.1-41
    fzf           : 0.56.3
    fd/fdfind     : 10.2.0 / No such file or directory (os error 2)
    rg            : 14.1.1
    chafa         : 1.14.5
    zoxide        : 0.9.6
    7z/7zz        : 17.05 / No such file or directory (os error 2)
    jq            : 1.7.1

Clipboard
    wl-copy/paste: No such file or directory (os error 2) / No such file or directory (os error 2)
    xclip        : 0.13
    xsel         : 1.2.1

Describe the bug

when upgrade arch linux, upgrade yazi version from 0.3.3-1 to 0.4.1-1. open yazi again, can't see yazi ui when open it.

Minimal reproducer

just simply open random terminal emulator(kitty, alacritty, etc), input yazi command, then yazi really works, but you can't see its ui :).

Anything else?

No response

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)

[sxyazi]

Version: 0.4.1 (Arch Linux 2024-12-19)

• I updated the debug information (yazi --debug) input box to the nightly that I tried

0.4.1 is the release version, not nighty. Can you try the latest nightly 0.4.3?

[hankertrix]

@siuyutpang you have UI code in your init.lua that hasn't been migrated to Yazi v0.4.0. Please read #1772 (comment).

[sxyazi]

Yeah @hankertrix is right, please update your config as per the pinned issue. If you're using any plugins, run ya pack -u to upgrade them to the latest, https://yazi-rs.github.io/docs/cli#package-manager

[siuyutpang]

😂 Actaully I had already migrated init.lua file to Yazi V0.4.0, not update in my dotfiles repo, I resolved it just use ya pack -u command. @sxyazi @hankertrix

[github-actions]

I'm going to lock this issue because it has been closed for 30 days. ⏳
This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please file a new issue and complete the issue template so we can capture all the details necessary to investigate further.