GPG key passphrase not accepted, Atom can't commit staged changes #814
Description
Description
When I attempt to commit my staged changes, I'm correctly prompted for my GPG key's passphrase. I use Keybase so, after opening my password manager and copying my Keybase password, I paste it into the prompt. However, the github package doesn't accept this passphrase and instead fails to create my commit.
Steps to Reproduce
- Stage some changes via git
- Type in a commit message and press the "Commit" button
- Paste Keybase passphrase into prompt
Expected behavior:
The github package to creates a new commit
Actual behavior:
The following error is shown:
12:02:56.616970 git.c:371 trace: built-in: git 'commit' '-m' 'WIP'
12:02:56.735330 run-command.c:369 trace: run_command: '/Applications/Atom Beta.app/Contents/Resources/app/node_modules/github/bin/gpg-no-tty.sh' '--status-fd=2' '-bsau' '2B0016D7'
error: gpg failed to sign the data
fatal: failed to write commit object
Reproduces how often:
100% of the time
Versions
# atom --version
Atom : 1.16.0
Electron: 1.3.13
Chrome : 52.0.2743.82
Node : 6.5.0
# apm --version
apm 1.16.1
npm 3.10.5
node 6.9.5 x64
python 2.7.13
# git --version
git version 2.13.0
hub version 2.2.9
# gpg --version
gpg (GnuPG/MacGPG2) 2.0.30
libgcrypt 1.7.0Additional Information
The project I am attempting to create a commit with has its own compiled version of git in the bin/ directory. My $PATH contains ./bin as the first entry, but I'm not sure what atom considers its working directory. If the working directory is whatever project is being used, then its using this custom built git. However, I am able to run git commit using this custom git and sign my own commits just fine.