-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2008-12-27 at 22:12 -0500, Anton Aylward wrote:
Maybe there is another agent run directly by KDE that is not compatible with keychain. In Gnome this is called seahorse-agent, in kde I don't know its name.
Maybe. But that doesn't explain something.
Under KDE4 running under 11.0 I did get the prompt to enter my keyphrase after logging in. Same as if I run keychain manually at the command line from a konsole window after logging in. A popup window with a cell that changes colour for each character I type.
That doesn't happen after login under 11.1
Yes, it would explain it. If KDE runs its own agent, it will be loaded before keychain, and might impede keychain from loading. The change would be that now kde4 has that agent. Previously, in gnome, the seahorse agent failed to work well, and I used a traditional console agent. But on a later version, seahorse was better, and both services were exclusive. Now I use seahorse instead of gpg agent and ssh agent. The advantage is that it can be used by apps inside xterms and native gnome apps. It works better than the previous situation. My hypothesis is that now kde has its own working agent. Would make sense. Check it; I can't. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAklW96YACgkQtTMYHG2NR9WezQCeP1GX7j30d9FlxrDqG/FGQZi+ P0QAn0cGswplJHH4NDe8XkzFhYClJdnA =etUZ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org