The strace show only that you interrupted gpg:
28203 rt_sigaction(SIGINT, {SIG_DFL}, NULL, 8) = 0
28203 unlink("/home/madduck/.gnupg/pubring.gpg.lock") = 0
28203 unlink("/home/madduck/.gnupg/.#lk0x81281d8.lapse.28203") = 0
and it cleaned up the lock file. The .tmp file won't get cleaned up
in such a case.
Thus, this does not show your problem
gpg: /home/madduck/.gnupg/pubring.gpg: copy to
`/home/madduck/.gnupg/pubring.gpg.tmp' failed: file read error gpg:
error writing keyring `/home/madduck/.gnupg/pubring.gpg': file read
error
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
