After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 418502 - evolution causes gpg stale locks
evolution causes gpg stale locks
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Mailer
2.30.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
evolution[gpg]
Depends on:
Blocks:
 
 
Reported: 2007-03-15 09:17 UTC by Sebastien Bacher
Modified: 2013-09-13 01:06 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28


Attachments
eds patch (2.12 KB, patch)
2010-03-30 20:59 UTC, Milan Crha
committed Details | Review

Description Sebastien Bacher 2007-03-15 09:17:36 UTC
The bug has been opened on https://launchpad.net/bugs/42199

"When changing from one message to another in the mail view, and the first one is gpg signed, evolution will [sometimes] kill gpg too abruptly, leaving a stale lock.

This seems to occur when the 'verifying message (0% complete)' message is in the status bar.

You can tell this has occured by running gpg --edit-key anykeyhere.

As shown here:
$ gpg --edit-key robertc

gpg: checking the trustdb
gpg: waiting for lock (held by 21748 - probably dead) ...
gpg: waiting for lock (held by 21748 - probably dead) ...

gpg: Interrupt caught ... exiting

I dont know if this is a security bug, buts its certainly problematic: I appear to have lost by public keyring twice in some sort of interaction with this.
..."
Comment 1 Matthew Barnes 2008-03-11 00:32:27 UTC
Bumping version to a stable release.
Comment 2 Akhil Laddha 2009-07-29 14:27:16 UTC
This version is no longer maintained, which means that it will not receive any
further security or bug fix updates.
The current stable GNOME and Evolution version is 2.26.

Can you please check again whether this issue still happens in Evolution 2.24
or 2.26 and update this report by adding a comment and changing the "Version"
field? Thanks a lot.

Again thank you for reporting this bug and we are sorry it could not be fixed
for the version you originally used here.
Comment 3 Akhil Laddha 2009-09-11 04:29:11 UTC
Thanks for taking the time to report this bug; however, closing due to lack of
response of the reporter, sorry. if you still see this issue with a current
release of evolution (2.26.3 or later), please reopen. thanks in advance.
Comment 4 Martin Mai 2009-09-21 18:34:11 UTC
Comment from launchpad on 20.09.2009:
>>>
happened yesterday
<<<

So this should be reopened.
Comment 5 Akhil Laddha 2009-09-22 03:46:50 UTC
(In reply to comment #4)
> Comment from launchpad on 20.09.2009:
> >>>
> happened yesterday
> <<<
> 
> So this should be reopened.

Could you please tell us your evolution version ?
Comment 6 Martin Mai 2009-09-22 13:42:37 UTC
Um, sorry. After all the version is the most important thing. He is using evolution 2.27.4.
Comment 7 Akhil Laddha 2009-09-25 05:49:49 UTC
thanks Martin
Comment 8 Milan Crha 2010-03-25 12:13:34 UTC
I cannot reproduce exactly the same thing as the original reporter sees, but I can reproduce something similar on actual master (~2.30.0):
a) choose an encrypted message, thus you'll be asked for a password
b) before entering a password, select another message
c) cancel the password prompt
See that
   $ ps -A | grep gpg
produces:
>  2787 ?        00:00:00 gpg <defunct>

repeating the process above produces another line. Closing Evolution makes it free again. The difference is, that I am able to --edit-key with these defunct gpgs, but I guess it's related, and fixing one will fit the other as well.
Comment 9 Milan Crha 2010-03-30 20:59:14 UTC
Created attachment 157527 [details] [review]
eds patch

for evolution-data-server;

This seems to do that for me.
Comment 10 Milan Crha 2010-04-01 12:10:41 UTC
Created commit 10bc3c4 in eds master (2.31.1+)
Created commit 757a25d in eds gnome-2-30 (2.30.1+)