thread 'main' (35636) panicked at src\main.rs:511:14

[mathias-buder]

Hi, I’ve been using this tool with Fork for quite some time and it has always worked flawlessly. I installed everything according to the instructions and selected the Git instance as shown below:

Recently, however, Fork started reporting an issue when trying to read my repositories:

⚠️ 2026-03-16 15:03:01.173 Refreshing repository status failed: fatal: detected dubious ownership in repository at '//wsl.localhost/SpitfireWSLImage2/projects/MyRepo'
To add an exception for this directory, call:

    git config --global --add safe.directory '%(prefix)///wsl.localhost/SpitfireWSLImage2/projects/MyRepo'

This has happened before when accessing a repository in WSL using the Windows Git instance. I checked Fork’s Git settings and noticed it had been reset to the default Windows version. I tried switching back to the Wslgit version, but it didn’t seem to take effect until I restarted Fork. Shortly after, it switched back to the Windows Git instance again.

I opened Fork’s log file and tried selecting Wslgit again, with the following result:

🔷 2026-03-16 14:49:44.273 Running 'C:\Users\user1\wslgit\bin\git.exe version'
⚠️ 2026-03-16 14:49:44.376 Shell request 'C:\Users\mb1052228\wslgit\bin\git.exe version' failed: '
thread 'main' (35636) panicked at src\main.rs:511:14:
Failed to execute command 'git -c credential.helper= -c "credential.helper=$(wslpath 'C:/Users/user1/AppData/Local/Fork/current/Fork.AskPass.exe')" -c credential.helper=manager version': Os { code: 6, kind: Uncategorized, message: "The handle is invalid." }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrac

Any ideas?

[andy-5]

Is this with the latest 1.3.0 release of wslgit?
Unfortunately, this release has a bug that already affects Fork in another way, see #149 . Maybe your problem is caused by the same issue.

Can you try wslgit v1.2.0 and check if that works?

[mathias-buder]

Hey @andy-5, thanks for the quick reply. Yes, this is with the latest v1.3.0 release. I'll give it a try with v1.2.0.

[mathias-buder]

Hi @andy-5, I testes v1.2.0 but it seams to have a different issue:

❌ 2026-03-17 15:10:04.421 Cannot find git instance at: ''
🔷 2026-03-17 15:10:04.421 Running 'C:\Users\user1\AppData\Local\Fork\gitInstance\2.50.1\bin\git.exe version'
🔷 2026-03-17 15:10:04.614 Running 'C:\Program Files\Git\bin\git.exe version'
🔷 2026-03-17 15:10:04.862 Running 'C:\Users\user1\wslgit\bin\git.exe version'
⚠️ 2026-03-17 15:10:05.048 Shell request 'C:\Users\user1\wslgit\bin\git.exe version' failed: 'thread 'main' panicked at 'Failed to execute command 'git -c credential.helper= -c "credential.helper=$(wslpath 'C:/Users/user1/AppData/Local/Fork/current/Fork.AskPass.exe')" -c credential.helper=manager version': Os { code: 6, kind: Uncategorized, message: "The handle is invalid." }', src\main.rs:441:14
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

[andy-5]

That's strange. Can you run a simplified version of that command directly from CMD/PowerShell?

wsl.exe -e /bin/bash -c 'git version'

Is there any output besides the git version?

[mathias-buder]

Here is the output for both, CMD and PowerShell:

CMD

C:\Users\user1>wsl.exe -e /bin/bash -c 'git version'
version': -c: line 1: unexpected EOF while looking for matching `''
version': -c: line 2: syntax error: unexpected end of file

If I replace the single quotes ('') with double quotes ("") it looks better

C:\Users\user1>wsl.exe -e /bin/bash -c "git version"
git version 2.34.1

PowerShell

PS C:\WINDOWS\System32> wsl.exe -e /bin/bash -c 'git version'
wsl: Failed to start the systemd user session for 'root'. See journalctl for more details.
git version 2.34.1

[andy-5]

It's interesting that the outputs differ. The additional line wsl: Failed to start the systemd user session for 'root'. See journalctl for more details. in the PowerShell output could be a problem, as wslgit (and I guess also Fork) expects only the output from git itself.

Maybe you can try to fix this startup error. There is an issue with some possible solutions to this: microsoft/WSL#13826

You could also try using another WSL distribution for wslgit by setting the WSLGIT_DEFAULT_DIST environment variable in Windows: https://github.com/andy-5/wslgit#wslgit_default_dist