GNOME Bugzilla – Bug 552086
seahorse asks twice for the same gpg password
Last modified: 2009-05-03 20:18:53 UTC
Please describe the problem: I've installed Ubuntu Hardy (8.04) with Gnome 2.22. When I'm sending an email with Thunderbird, Enigmail (GPG signing extension) asks twice for my gpg password, even though I've typed it correctly. This happens on Enigmail from Ubuntu package, and on the one downloaded from addons.mozilla.org. This worked properly on earlier version of Ubuntu/Gnome. It's a seahorse issue because it started happening when I've checked an option in Seahorse to not remember my GPG passwords. Steps to reproduce: 1. Open Seahorse 2. Change options to "don't remember my gpg passwords" 3. Try sending an email from Thunderbird with Enigmail Actual results: seahorse asks twice for the same gpg password in thunderbird (with enigmail) while I'm trying to send an email Expected results: to ask for my password only once Does this happen every time? yes Other information: same bug in Ubuntu bugtracker: https://bugs.edge.launchpad.net/ubuntu/+source/seahorse/+bug/246364
I can't duplicate this problem. Could you post a screenshot of the prompt? Do they look identical? Are the both from seahorse-agent?
Created attachment 118689 [details] screenshot1 screenshot1
Created attachment 118690 [details] screenshot2
Yes, they are identical, both are from Seahorse agent. There's another confirmation of the bug at the Enigmal forum: http://www.mozilla-enigmail.org/forum/viewtopic.php?f=3&t=421
I can confirm this bug agains Gnome 2.24 on Ubuntu Intrepid. The workaround described above works for me.
I also confirm this bug against Gnome 2.26.1 on Ubuntu jaunty.
From the enigmail ouput pasted in the enigmail forum, enigmail is performing two different operations: enigmail> /usr/bin/gpg --charset utf8 --batch --no-tty --status-fd 2 -t --clears ign -u 0xA81E15E0 --use-agent enigmail> /usr/bin/gpg --charset utf8 --batch --no-tty --status-fd 2 --digest-al go sha1 -s -b -a -t -u 0xA81E15E0 --use-agent If your option is set to have the agent not remember your passphrase, you will be asked twice for it because it's not being cached from request to request. If changing the caching option from never to expires after a period of time or always fixes this behavior, then everything is operating as designed. If that's not the case, please reopen this bug.