gpg-agent is not stopped on logout

Bug #30717 reported by hunger
10
Affects Status Importance Assigned to Milestone
gnupg2 (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Try this:
* create new user
* Log into X using it
* directly log out again (or do some other tests, doesen't matter)
* ps aux | grep username

This will show that gpg-agent is left runnnig for that user.

Revision history for this message
Alexandre Otto Strube (surak) wrote :

Hello Hunger, thanks for the bug. Is this still happening for you with latest dapper?

Revision history for this message
hunger (hunger) wrote :

Yes. Now gconf is left hanging around in addition to gpg-agent.

Revision history for this message
Alexandre Otto Strube (surak) wrote :

hunger, thanks for your answer! can you please open a separate bug against gconf? there are different people for dealing with each bug. Thanks a lot!

Revision history for this message
Ralf Hildebrandt (ralf-hildebrandt) wrote :

The bug is still there in feisty:

~$ date && ps auxwww|grep gpg
Sat Jan 27 21:05:09 CET 2007
hildeb 1719 0.0 0.0 3536 476 ? Ss Jan21 0:00 gpg-agent --daemon
hildeb 2478 0.0 0.0 3536 476 ? Ss Jan25 0:00 gpg-agent --daemon
hildeb 2770 0.0 0.1 3900 748 ? Ss Jan20 0:00 gpg-agent --daemon
hildeb 8514 0.0 0.0 3536 476 ? Ss Jan24 0:00 gpg-agent --daemon
hildeb 14661 0.0 0.0 3536 432 ? Ss Jan20 0:00 gpg-agent --daemon
hildeb 17229 0.0 0.0 3540 480 ? Ss Jan22 0:00 gpg-agent --daemon
hildeb 18764 0.0 0.0 3536 476 ? Ss 13:05 0:00 /usr/bin/gpg-agent --daemon --sh
hildeb 18791 0.0 0.0 3536 476 ? Ss 13:05 0:00 gpg-agent --daemon
hildeb 19203 0.0 0.1 3900 772 ? Ss Jan21 0:00 gpg-agent --daemon
hildeb 19662 0.0 0.0 3540 480 ? Ss Jan22 0:00 gpg-agent --daemon
hildeb 25987 0.0 0.1 3888 540 ? Ss Jan19 0:00 /usr/bin/gpg-agent --daemon --sh
hildeb 26016 0.0 0.0 3540 312 ? Ss Jan19 0:00 gpg-agent --daemon
hildeb 26138 0.0 0.0 3536 476 ? Ss Jan25 0:00 gpg-agent --daemon
hildeb 28402 0.0 0.0 3536 476 ? Ss Jan24 0:00 gpg-agent --daemon
hildeb 29032 0.0 0.0 3540 480 ? Ss Jan26 0:00 gpg-agent --daemon
hildeb 30793 0.0 0.0 3540 364 ? Ss Jan20 0:00 gpg-agent --daemon
hildeb 31621 0.0 0.0 3540 480 ? Ss Jan22 0:00 gpg-agent --daemon

Oh my god!

Revision history for this message
Ralf Hildebrandt (ralf-hildebrandt) wrote :

Still there in feisty, even after the release...

Revision history for this message
Scott Kitterman (kitterman) wrote :

I see this also with Kubuntu Feisty.

Changed in gnupg2:
status: New → Confirmed
Revision history for this message
Scott Kitterman (kitterman) wrote :

It looks like the fundamental problem is that gpg-agent is started with X from Xsessions.d, but doesn't get registered (presumably RegisterClient()), so when X exists it doesn't know to stop gpg-agent.

Changed in gnupg2:
status: Confirmed → Triaged
Revision history for this message
Scott Kitterman (kitterman) wrote :

Bryce Harrington,

I saw from your MOTU application your interest in X, so Ithought this bug might be up your alley. If not please accept my apologies for the bug mail spam and unsubscribe yourself.

Revision history for this message
Michael Bienia (geser) wrote :

This sounds like Debian bug #401843 which got fixed in gnupg2 2.0.6-1 in Debian unstable.

Revision history for this message
Scott Kitterman (kitterman) wrote : Re: [Bug 30717] Re: gpg-agent is not stopped on logout

I'm working on testing this.

Revision history for this message
Scott Kitterman (kitterman) wrote :

I've built a test package, but cannot seem to replicate the problem with
the current Gutsy gnupg2 (I haven't installed the test package yet).

Would someone else running Gutsy please see if you can still replicate the
issue?

Revision history for this message
hunger (hunger) wrote :

I no longer see this bug in Hardy. Can we close this bug?

I'm asking since so many other people reported similar problems, so I do not want to close the bug without at least a little feedback.

Revision history for this message
Ralf Hildebrandt (ralf-hildebrandt) wrote :

* hunger <email address hidden>:
> I no longer see this bug in Hardy. Can we close this bug?

Um, but the bug is still in the version I reported it AND hardy isn't
even released.

Revision history for this message
Scott Kitterman (kitterman) wrote :

Yes, but the Ubuntu policy (like it or not) is to only fix critical and
security bugs in releases. The criteria is here:

https://wiki.ubuntu.com/StableReleaseUpdates#head-9bac29d96da353649a97b4b1918c0b382b79a000

Revision history for this message
Ralf Hildebrandt (ralf-hildebrandt) wrote :

Seems to be fixed now in intrepid. Hussa.

Changed in gnupg2:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.