Bug#443115: seahorse-agent should start after gpg-agent and ssh-agent, and not start if both available

[Sebastian Dröge]

Am Mittwoch, den 19.09.2007, 13:36 -0700 schrieb Josh Triplett:
> retitle 443115 seahorse-agent should not start with gpg-agent and ssh-agent both available
> thanks
> 
> Sebastian Dröge wrote:
> > Am Dienstag, den 18.09.2007, 12:33 -0700 schrieb Josh Triplett:
> >> Package: seahorse
> >> Version: 2.20-1
> >> Severity: normal
> >>
> >> seahorse-agent currently starts in Xsession.d at 60.  gpg-agent and
> >> ssh-agent start at 90.  seahorse-agent should start after 90, and not
> >> start with both gpg-agent and ssh-agent already available.  I have
> >> gpg-agent installed and I don't want seahorse-agent replacing it; same
> >> with ssh-agent.
> > 
> > Doesn't seahorse start after gpg-agent then? IIRC the stuff from
> > Xsession.d starts from the highest to the lowest number. (see dbus which
> > has a higher number than seahorse but starts first)
> > 
> > What you want is probably seahorse before gpg-agent which is impossible
> > (as seahorse needs dbus). I really don't know what to do about this bug,
> > you're not the first who tells me something like that.
> 
> Actually, no, I really do want seahorse to start after gpg-agent and
> ssh-agent.  I forgot that while the scripts in Xsession.d run from
> lowest to highest, the ones like gpg-agent and ssh-agent prefix
> themselves to $STARTUP and thus run from highest to lowest; thus,
> seahorse-agent really does start after gpg-agent and ssh-agent.
> 
> That leaves the other half of this bug: I want seahorse-agent to not
> start at all if it can see from the environment that the session
> already has gpg-agent and ssh-agent running.

Which then will probably yield to a bug like your's, only the other way
around.

Users that want seahorse can only use it then when removing gpg-agent
and ssh-agent.