Installation of 64bit could complete, but running Git GUI always prompt the error below:
Couldn’t read file “C:\Program Files\Git\cmd\mingw64\libexec\git-core\git-gui”: no such file or directory
threads / discuss / 40331
v2.5.2 installation on Windows 10
Subject: v2.5.2 installation on Windows 10
Re: v2.5.2 installation on Windows 10
I can confirm this on the same setup (W10 64bit git 2.5.2)
Long <gimmely <at> gmail.com> writes:
Show 6 quoted lines
> > Installation of 64bit could complete, but running Git GUI always prompt the > error below: > > Couldn’t read file “C:\Program > Files\Git\cmd\mingw64\libexec\git-core\git-gui”: no such file or directory
Johannes SchindelinRe: v2.5.2 installation on Windows 10
Dear Diaoul,
it is considered rude on this mailing list to top-post, and likewise to cull the Cc: list. Please do not do that.
On 2015-09-12 11:34, Diaoul wrote:
> I can confirm this on the same setup (W10 64bit git 2.5.2)
Please see the corresponding ticket: https://github.com/git-for-windows/git/issues/376
In short: I will release an updated installer soon, with other fixes. In the meantime, as a work-around you could right-click on the Git GUI shortcut (you can right-click the icon in the Windows menu and open the file location to get there), select Properties... and change the Target: from
"C:\Program Files\Git\cmd\git-gui.exe"
to
"C:\Program Files\Git\cmd\git.exe" gui
It will open an ugly, unnecessary console until the next Git for Windows version is available, but at least it will work until then.
Out of curiosity: how did you go about finding the best place to report this bug?
Ciao, Johannes
Johannes SchindelinRe: v2.5.2 installation on Windows 10
Hi Long,
On 2015-09-11 18:13, Long wrote:
Show 6 quoted lines
> Installation of 64bit could complete, but running Git GUI always prompt the > error below: > > Couldn’t read file “C:\Program > Files\Git\cmd\mingw64\libexec\git-core\git-gui”: no such file or > directory
Please see the corresponding ticket: https://github.com/git-for-windows/git/issues/376
In short: I will release an updated installer soon, with other fixes. In the meantime, as a work-around you could right-click on the Git GUI shortcut (you can right-click the icon in the Windows menu and open the file location to get there), select Properties... and change the Target: from
"C:\Program Files\Git\cmd\git-gui.exe"
to
"C:\Program Files\Git\cmd\git.exe" gui
It will open an ugly, unnecessary console until the next Git for Windows version is available, but at least it will work until then.
Out of curiosity: how did you go about finding the best place to report this bug?
Ciao, Johannes
Johannes SchindelinRE: v2.5.2 installation on Windows 10
Hi Long,
On 2015-09-12 13:43, Long Yang wrote:
> Thanks for the email to confirm the bug.
Of course! Thank you for taking the time to report it.
Show 6 quoted lines
> To answer your question first, I found only the Community page at > http://www.git-scm.com/, as I was looking for a forum-kind of page to > see if someone had reported the same problem I had. Then I tried to > send a couple of emails to the mailing list, git@vger.kernel.org, as > instructed on the Community page. But none of my emails was > delivered. At the end, I post my case via gmane.
Thank you, I think I will open a Pull Request to that Community page to suggest going the GitHub issues route in case of Windows-specific bugs.
> In short, I still don't know how to successfully report a bug for Git. > Should I/users use GitHub?
If the bug in question is a Windows-specific bug, or if you do not know whether it is a Windows-specific bug, then yes, please submit it to our GitHub issue tracker, as described in the "Contribute" section of our home page: http://git-for-windows.github.io/#contribute
If you already know that the bug in question affects more than just Windows users, please report it to the Git mailing list, as you have done. (You will need to send plain-text messages, as the Git mailing list rejects HTML mails.)
Ciao, Johannes
Re: v2.5.2 installation on Windows 10
Hi Johannes,
Johannes Schindelin <johannes.schindelin <at> gmx.de> writes:
Show 17 quoted lines
> > Hi Long, > > On 2015-09-12 13:43, Long Yang wrote: > > > Thanks for the email to confirm the bug. > > Of course! Thank you for taking the time to report it. > > > To answer your question first, I found only the Community page at > > http://www.git-scm.com/, as I was looking for a forum-kind of page to > > see if someone had reported the same problem I had. Then I tried to > > send a couple of emails to the mailing list, git <at> vger.kernel.org, as > > instructed on the Community page. But none of my emails was > > delivered. At the end, I post my case via gmane. > > Thank you, I think I will open a Pull Request to that Community page to
suggest going the GitHub issues route
Show 6 quoted lines
> in case of Windows-specific bugs. > > > In short, I still don't know how to successfully report a bug for Git. > > Should I/users use GitHub? > > If the bug in question is a Windows-specific bug, or if you do not know
whether it is a Windows-specific bug,
> then yes, please submit it to our GitHub issue tracker, as described in
the "Contribute" section of our
> home page: http://git-for-windows.github.io/#contribute > > If you already know that the bug in question affects more than just
Windows users, please report it to the Git
> mailing list, as you have done. (You will need to send plain-text
messages, as the Git mailing list rejects
> HTML mails.) >
I guess my emails were rejected due to HTML, as I'm using Outlook with HTML default.
I'll try to follow the instructions on reporting bugs going forward.
> Ciao, > Johannes >
"Another" issue I'm seeing now is that, as I mentioned in a follow-up post to another person's on this problem, Git commands are not showing in Windows Explorer (via right-click). I've installed TortoiseGit and seen the same/similar "issue" with its commands too. Especially, TortoiseGit doesn't show a command to create a repository, which I don't know is with Git or the communication between Git v2.5.2 and TortoiseGit.
Long