Any idea why starting evolution from the panel should take much longer than from the command line?

[Chris G]

On Sun, Oct 24, 2010 at 01:41:44PM +0100, Chris G wrote:
> On Sat, Oct 23, 2010 at 05:01:56PM +0200, Liviu Andronic wrote:
> > On Sat, Oct 23, 2010 at 2:37 PM, Chris G <cl at isbd.net> wrote:
> > > I'm not sure if this is an xfce problem or what but it might be.
> > >
> > > If I start evolution from either the 'Applications' menu or from a
> > > launcher I have added myself to the xfce4-panel it takes about 30
> > > seconds for the GUI to appear.
> > >
> > > If I start it from a command line it starts instantly (or near enough).
> > >
> > > So what's causing the long delay?  The command is exactly the same in
> > > both cases - /usr/bin/evolution, I'm stumped as to where that 30 seconds
> > > is going.
> > >
> > > Any ideas?
> > >
> > Is it different when you're launching from the app finder? Are you
> > sure that the launcher contains 'evolution' with no additional
> > parameters?
> 
> It takes the same 30 seconds or so when run from the app finder.
> 
> I've checked the entry in /usr/share/menu and it doesn't have any extra
> parameters, the command there is just "/usr/bin/evolution".  However
> running that from the command line is still instantaneous unlike running
> it from any of the menus etc.
> 
> I have also just tried it from "Run Program", just the same, takes 30
> seconds to appear.
> 
> Aha - a clue.  I just tried running evolution from "Run Program" but in
> addition I ticked "Run in Terminal".  The terminal window popped up
> immediately and then set there for 30 seconds after which it output:-
> 
>     ** Message: secret service operation failed: Did not receive a
>     reply. Possible causes include: the remote application did not send
>     a reply, the message bus security policy blocked the reply, the
>     reply timeout expired, or the network connection was broken.
> 
> So *that's* what is wasting the time.  What on earth does "secret
> service operation failed:" mean?  I'll go and Google it.
> 
Well, after a little Googling I found that the above error is due to
evolution not communicating with gnome-keyring etc.  I've also realised
why I have the problem when running from the menus and not from the
command line.

To overcome a bug/problem in the Gnome startup I have the following in
my .xprofile:-

    eval $(gnome-keyring-daemon --start)
    export SSH_AUTH_SOCK
    export GNOME_KEYRING_SOCKET

This obviously fixes the problem when running evolution from the command
line but I guess that .xprofile doesn't get executed early enough to set
the environment for the menus etc.

So the question now is where can I put the above commands so that the
*whole* of my X session gets the gnome-keyring-daemon set correctly?

-- 
Chris Green