Gnome-Keyring won't unlock my own GPG keys

English Applications
1

Hi every one!

For a couple of days now, I had the following issue: Whenever I try to sign an email in Evolution, I get the following (German) message:

Because "gpg: Abbruch durch Benutzer
gpg: übersprungen “50175350”: Verarbeitung wurde abgebrochen
gpg: signing failed: Verarbeitung wurde abgebrochen
", you may need to select different mail options.

(Which is so wrong in itself that I can’t properly translate it).

If I receive an email, Evolution just puts its “Encrypted” batch there, but doesn’t dare to give me any error message – but it does not decrypt/display/… anything!

Turns out, Gnome Keyring seems to not unlock the private key. Hence I went and clicked around, I found that if I try to alter the password for my private key (in Seahorse), I receive an error stating I already tried three times (and should repeat, without any option to repeat). Which is strange since I cannot remember to ever enter an incorrect PW here! Just to give Evolution/Gnome-Keyring a fresh chance, in Seahorse I deleted the password for the private key; Rebooted the machine and expected Evolution/Gnome-Keyring/Seahorse to ask me for the password to unlock the private key (which is still in the Seahorse GPG-Keyring-Ring). But nothing happened. I was not given any chance to enter my private key’s password, and, no wonder now, Evolution’s behaviour hasn’t changed.

Can anyone explain (a) what the hack happened here and (b) how I can make my system useable again (no, I do not want to switch to Thunderbird, seriously!)?

Any help is needed/appreciated!

2

What DM ssdm or gdm? I think keyring may not start up if ssd need to switch to gdm

3

I use GDM 3.14.2. Think that’s default for openSUSE. As fas as ps aux can tell, /usr/bin/gnome-keyring-daemon is running here.

4

Update:
After writing this, I shut down my PC, started it again this morning → Evolution asks for the passwords for the key, and whether it should automatically un-lock it. Up to now, all looks fine, except I am pretty sure I didn’t do anything (but re-booting the machine one more time). WTF?

5

**Update II:
**
I re-booted my machine again, now the behaviour as before: Evolution doesn’t work, Seahorse claims I entered the wrong password thrice.