You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I downloaded version 0.49.0 and now when launching lazygit I get the following error message
2025/04/16 10:10:44 An error occurred! Please create an issue at: https://github.com/jesseduffield/lazygit/issues
*fs.PathError open C:\Users\USERNAME\AppData\Local\lazygit\state.yml: The requested operation cannot be performed on a file with a user-mapped section open.
/home/runner/work/lazygit/lazygit/pkg/app/app.go:55 (0x10046df)
/home/runner/work/lazygit/lazygit/pkg/app/entry_point.go:168 (0x1006885)
/home/runner/work/lazygit/lazygit/main.go:23 (0x1007ad8)
/opt/hostedtoolcache/go/1.24.2/x64/src/internal/runtime/atomic/types.go:194 (0x7c679d)
/opt/hostedtoolcache/go/1.24.2/x64/src/runtime/asm_amd64.s:1700 (0x8019a1)
I can't see anything locking state.yml.
If I delete the C:\Users\USERNAME\AppData\Local\lazygit and start lazygit then it works but if I exit lazygit and then launch lazygit again I get the error again.
To Reproduce
Go into any git repo and launch lazygit
Version info: Run lazygit --version and paste the result here
I can't reproduce this on my Windows box. Also, I don't see anything in the diff between 0.48 and 0.49 that could make a difference to how we read or write state.yml.
My suspicion is that there is some other process that keeps the file open for some reason. See if this helps.
Describe the bug
I downloaded version
0.49.0
and now when launchinglazygit
I get the following error messageI can't see anything locking
state.yml
.If I delete the
C:\Users\USERNAME\AppData\Local\lazygit
and startlazygit
then it works but if I exitlazygit
and then launchlazygit
again I get the error again.To Reproduce
Go into any git repo and launch
lazygit
Version info:
Run
lazygit --version
and paste the result hereRun
git --version
and paste the result hereAdditional context
This appears to only be an issue with
v0.49.0
.v0.48.0
is working for me.The text was updated successfully, but these errors were encountered: