LazyVim will not start because Neovim or Git is too old
LazyVim does not start and nvim --version shows a version older than 0.11.2Short answer
LazyVim needs Neovim 0.11.2 or newer (built with LuaJIT) and Git 2.19 or newer. Ubuntu's apt package is often older. Install the official Neovim release tarball, put it first on PATH, and check with nvim --version.
Fix it fast
1Find out which cause you have
Print the Neovim and Git versions you actually run, and every nvim on your PATH.
nvim --version | head -n 3 git --version which -a nvim2Match what you see, then jump to its fix
- 1
nvim --version shows a version below 0.11.2, or LuaJIT is missing from the build lineNeovim is older than LazyVim's minimumFix - 2
which -a nvim lists /usr/bin/nvim before the new copy, and nvim --version still shows the old numberAn old nvim still comes first on PATHFix - 3
git --version prints less than 2.19.0, and plugins fail to downloadGit is older than 2.19Fix
- 1
What does the error look like?
LazyVim does not start and nvim --version shows a version older than 0.11.2Plugins fail to download while git --version is older than 2.19.0
Cause 1 of 3
Neovim is older than LazyVim's minimum
1Check
LazyVim's own page lists Neovim 0.11.2 or newer, built with LuaJIT, as the first requirement. The version in the default Ubuntu repository can be lower.
nvim --version | head -n 32Fix
Install the official release tarball into /opt and add it to your PATH.
# download nvim-linux-x86_64.tar.gz from the Neovim releases page, then:
sudo rm -rf /opt/nvim-linux-x86_64
sudo tar -C /opt -xzf nvim-linux-x86_64.tar.gz
echo 'export PATH="/opt/nvim-linux-x86_64/bin:$PATH"' >> ~/.bashrc3Verify
A new shell prints the new version.
exec bash
nvim --version | head -n 1Confirmed by github.com
Cause 2 of 3
An old nvim still comes first on PATH
1Check
Neovim's install page adds its folder to the end of PATH, so an apt-installed nvim in /usr/bin is found first. Shells also cache the old path.
which -a nvim
type -a nvim2Fix
Put the new folder first in PATH (as in the line above), or remove the old package, and open a new shell.
sudo apt remove neovim
hash -r3Verify
The first nvim in the list is the new one.
which nvim && nvim --version | head -n 1Confirmed by github.com
Cause 3 of 3
Git is older than 2.19
1Check
LazyVim lists Git 2.19.0 or newer as a requirement because it uses partial clone support.
git --version2Fix
Install a Git release that is 2.19.0 or newer from your distribution or from Git's own downloads, then restart Neovim so lazy.nvim retries the plugins.
git --version3Verify
The version is 2.19.0 or higher.
git --versionConfirmed by lazyvim.org
How do I stop it coming back?
- Check the requirements list on lazyvim.org before upgrading LazyVim, since the minimum Neovim version moves.
- Keep one nvim on the machine.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Related fixes
Servers
dnf cannot install MySQL on Amazon Linux 2023
dnf cannot find a mysql-server package on Amazon Linux 2023
Amazon Linux 2023 documents MariaDB, not MySQL, as its database server, with packages named mariadb105 and mariadb105-server.
3 causes, each with a fixServers
Ansible hangs, then times out waiting for the sudo prompt
a playbook using become seems to hang
Ansible ran sudo on the target and never saw the answer it expected.
3 causes, each with a fixServers
Apache on Ubuntu returns 404 Not Found for my site
The requested URL was not found on this server.
On Ubuntu a 404 from Apache usually means the request maps to a path that has no file.
3 causes, each with a fixServers
Apache returns 504 Gateway Timeout when PHP takes too long
Quick requests work, slow ones end in a 504 after a fixed wait
A 504 from Apache means the backend did not answer within the proxy timeout.
2 causes, each with a fixServers
Apache logs SIGWINCH and exits on its own
the httpd container stops although nothing crashed
SIGWINCH is Apache's graceful-stop signal.
2 causes, each with a fixServers
Apache warns that a ${VAR} config variable is not defined
${VAR} left unchanged in the configuration, with a warning in the error log
Apache expands ${VAR} from Define or from the shell environment that exists when the server starts.
3 causes, each with a fix