threads / discuss / 63769

Problem with gitk

Subject: Problem with gitk

## tl;dr

3 messages between Jul 9, 2025 and Jul 10, 2025.

replies: 2people: 3as markdown or json

Nicolas Ratier· Jul 9, 2025, 10:23 UTC · lore

Hello,

I have this error with gitk :

$ gitk

and inside the window of gitk :

Erreur à l'exécution de git log :

wrong # args: should be

"safe_open_command_redirect cmd redir"

+ My git is clean (I tried git status, qgit etc ...)

+ I reinstall gitk without success

+ google don't have any information about the problem

+ and chatgpt doesn't give useful help ...

Thanks for help, I don't know what to do...

Nicolas

Johannes Sixt· Jul 9, 2025, 15:08 UTC · re: Nicolas Ratier · lore

Re: Problem with gitk

Am 09.07.25 um 12:23 schrieb Nicolas Ratier:

Show 11 quoted lines

> I have this error with gitk :
> 
> $ gitk
> 
> and inside the window of gitk :
> 
> Erreur à l'exécution de git log :
> 
> wrong # args: should be
> 
> "safe_open_command_redirect cmd redir"

You are suffering from an incorrect backport of the recent security fixes to a Git version before 2.43.7. Tell your maintainer to look into this. I can help if necessary.

For example, see here: https://bugs.launchpad.net/ubuntu/+source/git/+bug/2116253

-- Hannes

Junio C Hamano· Jul 10, 2025, 15:59 UTC · re: Johannes Sixt · lore

Re: Problem with gitk

Johannes Sixt <j6t@kdbg.org> writes:

Show 21 quoted lines

> Am 09.07.25 um 12:23 schrieb Nicolas Ratier:
>> I have this error with gitk :
>> 
>> $ gitk
>> 
>> and inside the window of gitk :
>> 
>> Erreur à l'exécution de git log :
>> 
>> wrong # args: should be
>> 
>> "safe_open_command_redirect cmd redir"
>
> You are suffering from an incorrect backport of the recent security
> fixes to a Git version before 2.43.7. Tell your maintainer to look into
> this. I can help if necessary.
>
> For example, see here:
> https://bugs.launchpad.net/ubuntu/+source/git/+bug/2116253
>
> -- Hannes

Whew.

I first misread the above report and response and was afraid that we started from an in-between version and botched our backport down to older maintenance tracks, but after double checking that what we shipped (Git 2.43.7 and upwards) recently does not have this issue, I realized that there are distro packagers that backport even further into the past, where some mistakes happened.

Thanks for a quick response.