GNUPG / GPG / S3 / Duplicity gpg: no default secret key: secret key not available

[punksgt]

Okay, not to be a complete noob.

So I created a new key and selected  "RSA and RSA"

Still getting this error.

GPGError: GPG Failed, see log below:
===== Begin GnuPG log =====
gpg: no default secret key: secret key not available
gpg: [stdin]: sign+encrypt failed: secret key not available
===== End GnuPG log =====

Here is the out put of my edit function:

bege at BlueSky:~/Desktop$ gpg --edit D9CF0329
gpg (GnuPG) 1.4.18; Copyright (C) 2014 Free Software Foundation, Inc.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Secret key is available.

pub  2048R/D9CF0329  created: 2015-07-17  expires: never usage: SC
                      trust: ultimate      validity: ultimate
sub  2048R/545996A5  created: 2015-07-17  expires: never usage: E
[ultimate] (1). Chad H <chad.h at strategic-options.com>

gpg>




On 07/15/2015 06:09 PM, NIIBE Yutaka wrote:
> On 07/16/2015 12:13 AM, punksgt wrote:
>> Here is the details of my keys:
>>
>> |/home/bege/.gnupg/pubring.gpg
>> -----------------------------
>> pub   2048R/7E4B6B9B 2015-07-15
>> uid                  Chad H <me at mail.com>
>>
>> /home/bege/.gnupg/secring.gpg
>> -----------------------------
>> sec   2048R/7E4B6B9B 2015-07-15
>> uid                  Chad H <me at mail.com>
> It seems that your key is only primary key (which is for signing other
> key and for signing data).  For encryption, you also need a subkey for
> encryption (or primary key should have a flag for encryption).
>
> You can add a subkey for encryption by 'gpg --edit 7E4B6B9B' or you
> can create new key with primary key and subkey for encryption.
> Default is "RSA and RSA", which means RSA primary key and RSA
> encryption key.