[wellylug] gpg: signing failed: secret key

[Adam Bogacki]

> 1) stat your ~/.gnupg/gpg.conf and look at the atime.
>
> 2) start mutt, try to sign/send an email. it fails?
>
> 3) stat ~/.gnupg/gpg.conf again, and see if the atime is updated.
> assuming
> that it's the same atime as step 1, find out why mutt isn't reading
> it.
adam at Tohunga:~$ stat  ~/.gnupg/gpg.conf
  File: `/home/adam/.gnupg/gpg.conf'
  Size: 131           Blocks: 8          IO Block: 4096   regular file
Device: 341h/833d    Inode: 2052377     Links: 1
Access: (0600/-rw-------)  Uid: ( 1000/    adam)   Gid: ( 1000/    adam)
Access: 2008-10-17 21:16:42.000000000 +1300
Modify: 2008-10-17 15:31:07.000000000 +1300
Change: 2008-10-17 15:31:07.000000000 +1300
adam at Tohunga:~$ stat  ~/.gnupg/gpg.conf
  File: `/home/adam/.gnupg/gpg.conf'
  Size: 131           Blocks: 8          IO Block: 4096   regular file
Device: 341h/833d    Inode: 2052377     Links: 1
Access: (0600/-rw-------)  Uid: ( 1000/    adam)   Gid: ( 1000/    adam)
Access: 2008-10-19 17:28:24.000000000 +1300
Modify: 2008-10-17 15:31:07.000000000 +1300
Change: 2008-10-17 15:31:07.000000000 +1300
adam at Tohunga:~$ stat  -f ~/.gnupg/gpg.conf
  File: "/home/adam/.gnupg/gpg.conf"
    ID: daebfa5a9957f005 Namelen: 255     Type: ext2/ext3
Block size: 4096       Fundamental block size: 4096
Blocks: Total: 4903934    Free: 920022     Available: 670915
Inodes: Total: 2492064    Free: 2367745
adam at Tohunga:~$

.. so atime for Access is updated.

I'm unclear how to

> find out why mutt isn't reading
> it.

Could you add some more detail ?

Adam.