Key lookup somehow broken when using --key=<peerId> option for `ipfs name publish`

#### Version information:

0.4.14-dev-199a52d

#### Type:

Bug

#### Description:

I somehow broke key lookup:

```
$ ipfs key list -l
Qma5Tggt66MccA7p4qe3cTRkHEN1jTvCg8FotF2DedW7vM self

$ ipfs name publish --key=Qma5Tggt66MccA7p4qe3cTRkHEN1jTvCg8FotF2DedW7vM QmYYSXJyYsgqMQGHKgFyYAvrmu5YjpNAVVCHXaGRbYLh9E
Error: no key by the given name or PeerID was found

$ ipfs name publish QmYYSXJyYsgqMQGHKgFyYAvrmu5YjpNAVVCHXaGRbYLh9E
Published to Qma5Tggt66MccA7p4qe3cTRkHEN1jTvCg8FotF2DedW7vM: /ipfs/QmYYSXJyYsgqMQGHKgFyYAvrmu5YjpNAVVCHXaGRbYLh9E
```

I don't recall seeing any error messages, but I was messing around with publishing things to IPNS all afternoon and had to cancel a few publish requests that I had made through the HTTP API because they hadn't returned after more than 10 minutes. It was working earlier today.

I should note that it's only for that key, and only when using the peer ID:

- when I generated another key, I was able to do `ipfs name publish --key=` successfully.
- when I use `ipfs name publish --key=self` instead, it works also