I *think* if you change the numbers in /etc/X11/Xsession.d/ that'll do it.
The lower numbers start first, higher numbers start last. Seahorse-plugins is
by default a lower number, so it should be starting first. If you have use-
agent in your gpg.conf this *may* vary.
The hacky way:
In your
Scott:
I talked to Adam (upstream) about that gnupg.conf over-writing, and he
said it shouldn't happen in any version of Seahorse released in the last
year (pointed out the commit that removed it, too). He asked about
patches Ubuntu has applied. Is it possible we have some old n crufty
patch
Seb, I'm using Jaunty. I created a new user. As soon as that user
logged into GNOME for the first time (really, I think it was as soon as
the gnome-session started seahorse-agent) that user's gpg.conf was
edited to say:
# FILE CREATED BY SEAHORSE
Just that comment and a blank line. That means
I don't know. I do think it might be useful if you tried to force remove
gnupg-agent and see how well seahorse-agent works for stuff like gpg
singing mail (kmail), signing packages, etc.
I think seahorse-agent either needs to fully replace gnupg-agent or work
along side it.
--
seahorse does
Seb I talked to Adam again.
Seahorse adds gpg.conf if it does not exist when seahorse-agent runs.
Seahorse's caching preferences set use-agent in gconf but not in the
file.
KMail and Evolution *both* claim bad passphrase if I use
seahorse-agent inside KDE. Evolution additionally uses 98% CPU
gnome-keyring-daemon and ssh-agent share a purpose
seahorse-agent (s-a) and gpg-agent (g-a) share a purpose
The first on each line to start wins.
gnome-keyring-daemon means we have pretty passphrase boxes and the
password is remembered, unlike ssh-agent.
seahorse-agent...I don't see any
