fatal: Unable to create `../index.lock`: File exists.

[Dich0tomy]

For some time now lazygit seems to bug all the time. I'm 100% sure that there are no other programs running in the background that could do some git operations.

I try to open lazygit from the terminal, but everytime I try to do any operation after that I get the error about the git lock. So I remove it by hand rm -rf .git/index.lock and get back to lazygit, same thing.

It doesn't matter if I do this from bare console or from the console inside neovim. Sometimes after deleting the index.lock file and getting back it works fine, only to complain again a usage later.

If I remove the file manually and then use git commands instead of using lazygit, everything works fine.

Windows, but I'm on WSL2 kali-linux Linux stacjonarny 5.4.72-microsoft-standard-WSL2 #1 SMP Wed Oct 28 23:40:43 UTC 2020 x86_64 GNU/Linux
Lazygit version 0.34

[mark2185]

Do you by any chance have the automatic fetch enabled? (that's the default)
Maybe it hangs and causes said issues.

[Dich0tomy]

@mark2185 I didn't change any settings, so yes, that's probable that I have it enabled. I'll try to disable it and I'll come back with the results.

[Dich0tomy]

@mark2185 I tried. It doesn't help same issue.

[mattmiller-daxko]

I'm getting the same issue and I would love a fix or a workaround

[mark2185]

@mattmiller-daxko could you specify your environment? E.g. OS, lazygit version?

If it's also on WSL2, I found this (no answer) and this (long thread, but the link is to the answer).

In short, I cannot reproduce this, and if you're both on WSL, I'd bet my two cents on WSL itself being the root of the problems, not lazygit.

[mattmiller-daxko]

I'm not using WSL. I'm on Windows 11 21H2 using Windows Terminal with cmder mini as my shell. Lazygit commit=367b0d331836c90c015bf0c45f88612f3d94d08a, build date=2022-07-20T09:27:56Z, build source=binaryRelease, version=0.35, os=windows, arch=amd64

[mark2185]

Does the same happen with v0.34?

[mattmiller-daxko]

Not that I ever noticed. It only started happening after upgrading to 0.35

[mark2185]

Then it might be a regression. @mattmiller-daxko would you be willing to downgrade to v0.34 to see if it keeps happening? Same goes for @B4mbus

I seem to recall something about subprocesses being changed, but can't put my finger on it.

cc @jesseduffield for visibility and ideas

[mattmiller-daxko]

I have downgraded to v0.34 and I don't seem to have this problem anymore. I used v0.34 for several weeks before upgrading without any issues so I think it probably is a regression but I will leave another comment if I run into this issue again.

I also appreciate the quick response on this. I really love this git tool and would hate to have to switch to anything else.

[Dich0tomy]

@mark2185 I was running lazygit 0.34 all along, so the version is probably not a problem for me.

[mark2185]

Uhhh, well then... try updating? 😅

[Dich0tomy]

@mark2185 Yeah I just upgraded it, nothing wrong so far, I'll report in a day or two.

[mattmiller-daxko]

I'm still having this issue with v0.35. However, downgrading to v0.34 seems to solve it for me. I even tried disabling automatic refresh as suggested above but that did not solve the problem.