threads / discuss / 34649

gitk: "Can't parse git log output: { }"

Subject: gitk: "Can't parse git log output: { }"

## tl;dr

3 messages between Aug 9, 2013 and Aug 11, 2013.

replies: 2people: 2as markdown or json

Peter Krefting· Aug 9, 2013, 06:31 UTC · lore

Hi!

In my local clone of git.git, currently with the v1.8.4-rc2 tag checked out and built (and installed on the system), starting up gitk yields an empty window, with a dialog in front of it:

   error

   Can't parse git log output: { }

   [ OK ]

Has anyone else seen this, and know what might have happened? I do not get the behaviour in other repositories (including other clones of git.git), only this particular one.

-- 
\\// Peter - http://www.softwolves.pp.se/

Thomas Rast· Aug 9, 2013, 08:05 UTC · re: Peter Krefting · lore

Re: gitk: "Can't parse git log output: { }"

Peter Krefting <peter@softwolves.pp.se> writes:

Show 15 quoted lines

> Hi!
>
> In my local clone of git.git, currently with the v1.8.4-rc2 tag
> checked out and built (and installed on the system), starting up gitk
> yields an empty window, with a dialog in front of it:
>
>   error
>
>   Can't parse git log output: { }
>
>   [ OK ]
>
> Has anyone else seen this, and know what might have happened? I do not
> get the behaviour in other repositories (including other clones of
> git.git), only this particular one.

Have you tried moving away .git/gitk.cache?

If that fixes it, perhaps you can share it for inspection.

-- 
Thomas Rast
trast@{inf,student}.ethz.ch

Peter Krefting· Aug 11, 2013, 11:20 UTC · re: Thomas Rast · lore

Re: gitk: "Can't parse git log output: { }"

Thomas Rast:

> Have you tried moving away .git/gitk.cache?
> If that fixes it, perhaps you can share it for inspection.

Yes, I did, just after I sent off that email. It did not fix the problem, however.

-- 
\\// Peter - http://www.softwolves.pp.se/