GitX-L: missing object 0000000000000000000000000000000000000000
Asked Answered
D

3

5

I'm getting the following error in GitX-L when opening a git repository:

The document “REPO_NAME” could not be opened.

An error occured while trying to open file://localhost/Volumes/SERVER/www/REPO_NAME/.git/.
fatal: missing object 0000000000000000000000000000000000000000 for refs/remotes/origin/HEAD

Does anyone know what is causing this issue or how to fix it? I don't get the error while using the command line, so I'm assuming it is a problem with GitX-L.

git fsck does tell me about a bunch of dangling entries, could those be to blame?

Delvecchio answered 15/5, 2012 at 13:25 Comment(1)
Check that HEAD points to something - it may be empty. You appear to have a null sha1, and it says you are trying to open the file . which is simply the current directory.Gemeinschaft
S
8

I had the same error message when opening a repository in 'GitX' (a GUI tool).

For me, the problem was caused by the file .git/refs/remotes/origin/HEAD, which referenced a remote branch which I had deleted:

ref: refs/remotes/origin/develop

I fixed it by editing the file to contain the name name of a remote branch which did still exist:

ref: refs/remotes/origin/master
Savannasavannah answered 13/12, 2012 at 12:8 Comment(0)
S
4

It looks like something is wrong with the origin remote ref... Remove the culprit from Terminal with git branch -r -d origin/HEAD, or even git remote prune origin and re-open it in GitX.

Septilateral answered 15/5, 2012 at 13:32 Comment(2)
Didn't work for me: "error: remote branch 'origin/HEAD' not found." This sounds bad, but I don't understand what it really means. Recloning the remote repo fixed the problem for me.Savannasavannah
git branch -r -d origin/HEAD worked for me. @Jonathan Hartley - I'm pretty sure that it isn't a bad thing. It means that you don't have a local representation of the remote branch on origin named HEAD. At any rate, recloning the remote repo, if that is an option, is always a safe bet.Otis
W
1

I had the same problem.

A simple solution is to clone the faulty repository and start using the clone instead. It worked for me.

Webworm answered 6/6, 2012 at 15:57 Comment(0)

© 2022 - 2024 — McMap. All rights reserved.