{"thread":{"id":"63769","subject":"Problem with gitk","startedAt":"2025-07-09T10:24:07Z","lastAt":"2025-07-10T15:59:32Z","messageCount":3,"participants":["Nicolas Ratier","Johannes Sixt","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"521645","messageId":"d3ab5bcc-6f71-455c-933a-a63a9b39e8b9@femto-st.fr","threadId":"63769","inReplyTo":null,"subject":"Problem with gitk","fromName":"Nicolas Ratier","fromEmail":"nicolas.ratier@femto-st.fr","sentAt":"2025-07-09T10:23:06Z","receivedAt":"2025-07-09T10:24:07Z","isPatch":false,"sender":{"key":"nicolas.ratier@femto-st.fr","avatar":null},"body":"Hello,\n\nI have this error with gitk :\n\n$ gitk\n\nand inside the window of gitk :\n\nErreur à l'exécution de git log :\n\nwrong # args: should be\n\n\"safe_open_command_redirect cmd redir\"\n\n\n+ My git is clean (I tried git status, qgit etc ...)\n\n+ I reinstall gitk without success\n\n+ google don't have any information about the problem\n\n+ and chatgpt doesn't give useful help ...\n\nThanks for help, I don't know what to do...\n\nNicolas\n\n\n\n\n"},{"id":"521683","messageId":"a6c5d181-5cdb-4070-96a6-cf88c3a5c838@kdbg.org","threadId":"63769","inReplyTo":"d3ab5bcc-6f71-455c-933a-a63a9b39e8b9@femto-st.fr","subject":"Re: Problem with gitk","fromName":"Johannes Sixt","fromEmail":"j6t@kdbg.org","sentAt":"2025-07-09T15:08:20Z","receivedAt":"2025-07-09T15:08:30Z","isPatch":false,"sender":{"key":"j6t@kdbg.org","avatar":"https://avatars.githubusercontent.com/u/14810926?v=4"},"body":"Am 09.07.25 um 12:23 schrieb Nicolas Ratier:\n> I have this error with gitk :\n> \n> $ gitk\n> \n> and inside the window of gitk :\n> \n> Erreur à l'exécution de git log :\n> \n> wrong # args: should be\n> \n> \"safe_open_command_redirect cmd redir\"\n\nYou are suffering from an incorrect backport of the recent security\nfixes to a Git version before 2.43.7. Tell your maintainer to look into\nthis. I can help if necessary.\n\nFor example, see here:\nhttps://bugs.launchpad.net/ubuntu/+source/git/+bug/2116253\n\n-- Hannes\n\n"},{"id":"521762","messageId":"xmqq1pqo82am.fsf@gitster.g","threadId":"63769","inReplyTo":"a6c5d181-5cdb-4070-96a6-cf88c3a5c838@kdbg.org","subject":"Re: Problem with gitk","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2025-07-10T15:59:29Z","receivedAt":"2025-07-10T15:59:32Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Johannes Sixt <j6t@kdbg.org> writes:\n\n> Am 09.07.25 um 12:23 schrieb Nicolas Ratier:\n>> I have this error with gitk :\n>> \n>> $ gitk\n>> \n>> and inside the window of gitk :\n>> \n>> Erreur à l'exécution de git log :\n>> \n>> wrong # args: should be\n>> \n>> \"safe_open_command_redirect cmd redir\"\n>\n> You are suffering from an incorrect backport of the recent security\n> fixes to a Git version before 2.43.7. Tell your maintainer to look into\n> this. I can help if necessary.\n>\n> For example, see here:\n> https://bugs.launchpad.net/ubuntu/+source/git/+bug/2116253\n>\n> -- Hannes\n\nWhew.\n\nI first misread the above report and response and was afraid that we\nstarted from an in-between version and botched our backport down to\nolder maintenance tracks, but after double checking that what we\nshipped (Git 2.43.7 and upwards) recently does not have this issue,\nI realized that there are distro packagers that backport even further\ninto the past, where some mistakes happened.\n\nThanks for a quick response.\n\n\n\n"}]}