Hi again!

I still have a problem with my PGP de-cryption in Evolution. But I nailed it down a bit, maybe now some experiences Geekos can help me!
After re-booting and logging into a fresh Gnome session, Evolution won't open mails that were GPG-encrypted. It looks as if Evolution doesn't have my PGP key (at least, it doesn't even ask for the passphrase…); PGP (cli pgp2) works as usual, Seahorse shows my PGP key and its passphrase correctly.

But:
In the logs, I can find error messages such as
Code:
gnome-keyring-daemon: insufficient process capabilities, unsecure memory might get used
→ I tried to manually start gnome-keyring-daemon, and the result is:

Code:
/usr/bin/gnome-keyring-daemon --start --components=gpg
gnome-keyring-daemon: insufficient process capabilities, unsecure memory might get used
SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
GPG_AGENT_INFO=/run/user/1000/keyring/gpg:0:1
and no effect.

It worked,
however, if I use su privileges:

Code:
sudo /usr/bin/gnome-keyring-daemon --start --components=gpg
root's password:
** Message: couldn't access control socket: /run/user/0/keyring/control: Datei oder Verzeichnis nicht gefunden
** Message: couldn't connect to dbus session bus: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
GPG_AGENT_INFO=/run/user/0/keyring/gpg:0:1
plus logging in again does solve the issue.

Of course, I preferred gnome-keyring-daemon gpg to be started right away on log-in. Does anyone know what the problem could be? I don't understand the error messages. Thanks in advance!

Philipp


BTW, if that's helpful:
Code:
gpg2-2.0.24-5.1.x86_64
python-gpgme-0.1-121.2.x86_64
gpg-pubkey-XX…XX
gpg-pubkey-XX…XX
libgpg-error0-32bit-1.13-3.6.x86_64
gpg-pubkey-XX…XX
gpg-pubkey-XX…XX
gpg-pubkey-XX…XX
libgpg-error0-1.13-3.6.x86_64
gpg-pubkey-XX…XX
libgpgme11-1.6.0-9.1.x86_64
gpg-pubkey-XX…XX
gpg2-lang-2.0.24-5.1.noarch
gpgme-1.6.0-9.1.x86_64
gpg-pubkey-XX…XX