Comment 14 for bug 394629

For the record I was able to trigger it again with my backup to rsync.net (the other one I tried was my S3 backup). So whatever the problem is it is definitely crossing backends.

As per previous discussion I too saw a GPG child process. Hitting ctrl-c yielded:

gpg: signal Interrupt caught ... exiting
Exception exceptions.KeyboardInterrupt in <module 'threading' from '/usr/local/lib/python2.5/threading.pyc'> ignored

I'll see if I can indeed reproduce it reliably and hopefully debug it.