nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

'git log' failed with code 5

Aron Malkine

I just upgraded to version 2.0.4 and now when I open the app, I get several errors that read:

'git log' failed with code 5:'dyld: lazy symbol binding failed: Symbol not found: ___strlcpy_chk

Referenced from: /Applications/SourceTree.app/Contents/Resources/git_local/bin/git
Expected in: /usr/lib/libSystem.B.dylib

dyld: Symbol not found: ___strlcpy_chk
Referenced from: /Applications/SourceTree.app/Contents/Resources/git_local/bin/git
Expected in: /usr/lib/libSystem.B.dylib

hat should I do? Hoping reinstalling is not required.

Accepted answers

All comments

TCS Developer

I also had this issue after upgrading to 2.0.4. For now as a work around, I have changed from the embedded git to the version on my system. You can do this by selecting SourceTree -> Preferences -> Git -> Use System Git

Hopefully Atlassian will fix this soon.

Jorge Diaz

Holly cows. Same issue here for ALL my repos. sad

bookingpad-web__Git_.png

Greg Rebholz

Same issue here after upgrade to 2.0.4. Reverting to system git (1.8.5.2) worked around for me as well.

Aron Malkine

Reinstalling did not help.

Noah_Reddell

I see this same problem on my machine running OS X 10.8.5. But no problem on my machine running OS X 10.9.5.

Greg Rebholz

Should have mentioned this was on OSX 10.8.5

unknown

Same here, all repos stopped working and showing the errors above - 10.8.5

unknown

Also confirmed that delete related plist, .gitconfig files and reinstall did not help.

TCS Developer

I am also running 10.8.5

bauerdev

Gave it one more try. This cause "fatal: Unable to create [my_project_path].git/index.lock': File exists." when tying to pull. Tried to follow Atlassian's help: https://blog.sourcetreeapp.com/2014/12/18/atlassian-update-for-git-and-mercurial-vulnerability/ But nothing worked except reverting to 2.0.3 removing the whole project and re-cloning it. Really bad.

Ben Currie

Ouch - wish I'd read this before updating. Pop up errors many. Fortunately reinstalling 2.0.3 over 2.0.4 and everything reappeared again. OS X 10.8.5.

KieranA

Hey there,

I'm the developer responsible for this release. 2.0.4 was an urgent maintenance release for CVE-2014-9390, so we shipped it with an existing binary release that addressed the issue. That binary release doesn't support 10.8 and prior, and this is something we're looking to address as we plan on continued support for 10.8.

In the meantime - as suggested in here already - you can use a system Git version from the Xcode Command Line Tools that addresses CVE-2014-9390 which is really easy to do (available through developer.apple.com). You may find there's a system Git already installed that's OK to use.

We'll be embedding a binary Git version which works on all OS X versions in the near future.

Cheers

Orson Bradford

I had the same result. Going back to 2.0.3 fixed the problem. http://downloads.atlassian.com/software/sourcetree/SourceTree_2.0.3.dmg

raghaaav

I just pinpointed the problem. It's the new version of Git (2.2.1) that's causing the issue. Using the old Git (1.8.4.2), I don't get the error anymore. I upgraded to SourceTree 2.0.4 and got the error. Thinking it was because my git was outdated, I updated the System Git to 2.2.1 and pointed SourceTree to the new git (Preferences -> Git). No bueno. I reverted to Sourcetree 2.0.3. It was still pointing to the System Git (2.2.1). Still no bueno. I pointed Sourcetree (Preferences -> Git) to the embedded Git (1.8.4.2) and it worked! No more error. I have a feeling that I was getting an error with the new git because I am on OSX Lion, not Mavericks. If you have SourceTree 2.0.4, try pointing SourceTree to Git 1.8.4.2. If you have SourceTree 2.0.3, make sure to use the embedded git.

Kevin Alexander

As of 2.0.5.8, this issue still exists for OS X 10.8.5. Reverting back to 2.0.3 allows it to work. When will this be addressed?