http://bugzilla.novell.com/show_bug.cgi?id=589994 http://bugzilla.novell.com/show_bug.cgi?id=589994#c5 --- Comment #5 from Petr Uzel <puzel@novell.com> 2010-04-01 15:48:54 UTC --- (In reply to comment #4)
It is reproducible. I think this may be interference from seahorse-agent. It is. Seahorse-agent does not fully implement the gpg-agent interface.
Perhaps running gpg-agent somehow makes gpg stop trying to connect to seahorse-agent, and it doesn't try to connect even after gpg-agent is killed? Yes, that's how gpg-agent works. See echo $GPG_AGENT_INFO - this is set both by gpg-agent and seahorse-agent.
gpg2-2.0.14-3.1.x86_64 This is not gpg2 version included in 'official 11.2' repositories. Please try to install gpg2-2.0.12 - with this version, I was no longer able to reproduce the issue.
I'll have a look into what has changed between gpg-2.0.{12,14} and if it is gpg2 bug or if seahorse-agent should be adjusted instead. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.