Checkhealth telescope gives error executing Lua

[JohnWilliston]

Description

I installed Neovim on an Amazon Linux 2023 VM and got my normal config (which works fine on other *nix VMs, macOS, and Windows I should note) in place. I noticed it was complaining today that the telescope plugin can't grep because it says ripgrep is required (it's already installed, so I don't know why it's bitching in the first place), so I did a checkhealth telescope as I've done plenty of times before and got the following unexpected output:

E5009: Invalid $VIMRUNTIME: /opt/nvim-linux-x86_64/share/nvim/runtime
Error executing lua: function health#telescope#check, line 1: Vim(lua):E5108: Error executing lua ...m/lua/telescope/_extensions/lazy_plugins/healthcheck.lua:63: attempt to index local 'finder' (a function value)
stack traceback:
	...m/lua/telescope/_extensions/lazy_plugins/healthcheck.lua:63: in function 'extension_healthcheck'
	.../share/nvim/lazy/telescope.nvim/lua/telescope/health.lua:126: in function 'check'
	[string ":lua"]:1: in main chunk
	[C]: in function 'call'
	.../nvim-linux-x86_64/share/nvim/runtime/lua/vim/health.lua:439: in function '_check'
	[string "<nvim>"]:1: in main chunk
stack traceback:
	[C]: in function 'call'
	.../nvim-linux-x86_64/share/nvim/runtime/lua/vim/health.lua:439: in function '_check'
	[string "<nvim>"]:1: in main chunk

Any ideas?

Neovim version

NVIM v0.11.4
Build type: Release
LuaJIT 2.1.1741730670

Operating system and version

Amazon Linux 2023

Telescope version / branch / rev

The latest master branch right now as of Wednesday, October 22, 2025, 10:26 hrs.

checkhealth telescope

Doesn't give me any output.

Steps to reproduce

1. Start Neovim.
2. Do :checkhealth telescope

Expected behavior

I expect a normal check health report.

Actual behavior

I get the error message I provided.

Minimal config

local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs { "config", "data", "state", "cache" } do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.uv.fs_stat(lazypath) then
  vim.fn.system {
    "git",
    "clone",
    "--filter=blob:none",
    "https://github.com/folke/lazy.nvim.git",
    lazypath,
  }
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  {
    "nvim-telescope/telescope.nvim",
    dependencies = {
      "nvim-lua/plenary.nvim",
    },
    config = function()
      -- ADD INIT.LUA SETTINGS THAT ARE _NECESSARY_ FOR REPRODUCING THE ISSUE
      require("telescope").setup {}
    end,
  },
}

require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

[JohnWilliston]

I can't tell you why, but I can tell you that: (1) the two problems seem to be related, and (2) changing my PATH variable fixed both of them. My PATH variable previously had an entry ~/.cargo/bin because I have a number of Rust utilities, ripgrep being one of them. It works fine at the prompt in any shell I use (mostly Bash and Zsh), so I thought that was alright. But that entry screws up the vim.fn.executable function, so that it reports I do not have ripgrep on my path when I do. It also appears to be causing the crash when running :checkhealth telescope. As soon as I change that entry to read $HOME/.cargo/bin, both of my problems go away.

I don't think this is a telescope issue as much as it's some kind of lower-level Neovim issue.

[clason]

Sorry, just now reading your reply more closely. If the issue is with the vim.fn.executable call and you shell PATH, then this is indeed not going to be fixed here.

And the error you post comes from a telescope extension, not this project, so we can't do anything about that here, either. (My suspicion is that the extension is outdated and no longer compatible with the latest Neovim.)