On Mon, 2006-05-29 at 02:39 +0200, guenther wrote:
> On Fri, 2006-05-26 at 09:06 +0930, Iain Buchanan wrote:
> [...]
> > Unless it's evolution that is making the environment get in this state,
> > or evolution being confused about it, when nothing is really wrong.
>
> No, it is not Evo. :)
>
> Generally you get this message, after updating Evo or building to a
> different prefix, and starting that one -- with the the old b-a-s still
> running. The issue is, that the running b-a-s does not find the
> correct .server files in the dir where it expects them.
But the problem comes and goes - one minute it works, and the next
minute I can't start evolution. I _don't_ recompile anything, I _don't_
have different versions of e-d-s or b-a-s or evo or anything lying
around...
Hence I don't understand your "after updating Evo or building"
statement.
> Killing b-a-s often solves this issue already.
>
> Changing the BONOBO_* env var mentioned previously is one way to solve
> this, if simply kicking b-a-s does not do it (most likely, cause Evo and
> friends have been built to a new prefix). The best fix though is, to
> change the b-a-s config and make it aware of the new prefix.
>
>
> > I checked my environment when evolution works (with set), and compared
> > it to the environment when it doesn't work, and I don't see any
> > differences.
> >
> > I'll check out playing with mail-notification next, but at the moment, I
> > can't reproduce the error...
>
> If it is the same prefix (likely, since you now cannot reproduce this
> any more), this issue should be resolved by restarting b-a-s in whatever
> way. Yes, rebooting (ugh) does this, too. ;-)
OK, I couldn't reproduce it _then_ but it is still reproducible, when it
decides to be.
These are the only env vars that differ between "working" and "not
working". All of them seem to be unrelated.
DBUS_SESSION_BUS_ADDRESS
GNOME_KEYRING_SOCKET
PPID
SESSION_MANAGER
SSH_AGENT_PID
SSH_AUTH_SOCK
WINDOWID
This is what I do to see the behaviour:
open evolution (works)
close evolution
wait, without doing anything (don't know for how long)
open evolution - "can't open" message
log off, log on.
open evolution (works again).
I can do this over and over, without changing / compiling / installing anything.
any comments?
thanks,
--
Iain Buchanan <iaindb at netspace dot net dot au>
Win95 is not a virus; a virus does something.
-- unknown source
_______________________________________________
Evolution-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/evolution-list
