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

[Sebastian Dröge]

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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
Url : http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20070919/89f8a514/attachment.pgp