RE: [Evolution] Crash on startup with OAFD error
- From: Cesar Talon <cesar talon uam es>
- To: Michel <michel salin org>
- Cc: evolution helixcode com
- Subject: RE: [Evolution] Crash on startup with OAFD error
- Date: Wed, 12 Jul 2000 10:13:43 +0200 (CEST)
On 12-Jul-2000 Michel wrote:
evolution-shell-WARNING **: Could not activate component
OAFIID:evolution-shell-component:evolution-mail:d3cb3ed6-a654-4337-8aa0-f44375
1d6d1b.
(Maybe you need to set OAF_INFO_PATH?)
I set OAF_INFO_PATH to /usr/share/oaf; if OAF_INFO_PATH is not set the
only difference is that 'trying /usr/share/oaf/' appears before the
warning.
Have a look at /tmp/orbit-XXXXX where XXXXX is your username. Deleting it
should work because it seems that once you have started the program with a
wrong OAF_INFO_PATH, it keeps the configuration there.
In my case, deleting the full /tmp/orbit-ctalon, and setting the OAF_INFO_
PATH to /usr/share/oaf worked ok, although I had to start evolution a couple of
times again in order to have the menus working.
BTW, this is on a debian dist, but I don't thing there should be differences
there.
Cesar
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Cesar Talon email: <Cesar Talon <cesar talon uam es>>
Laboratorio de Bajas Temperaturas / Dpto.Física de la Materia condensada
Universidad Autonoma de Madrid / Cantoblanco, E-28049 Madrid
Phone: +34 91 397 4756 / Fax: +34 91 397 3961
Whenever someone tells you to take their advice, you can be pretty sure
that they're not using it.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]