Evolution does not start anymore after an upgrade
Erich Dollansky
erichfreebsdlist at ovitrap.com
Fri Apr 13 15:58:31 UTC 2012
Hi,
On Friday 13 April 2012 20:46:37 Jeremy Messenger wrote:
> On Wed, Apr 11, 2012 at 9:02 PM, Erich Dollansky
> <erichfreebsdlist at ovitrap.com> wrote:
> >
> > On Wednesday 11 April 2012 20:56:13 Jeremy Messenger wrote:
> >> On Tue, Apr 10, 2012 at 8:23 PM, Erich Dollansky
> >> <erichfreebsdlist at ovitrap.com> wrote:
> >> >
> > There was a problem with the machine. It died during a port upgrade leaving it in a but undefined state. After fixing the hardware, I deleted everything (pkg_delete -a), updated the ports tree and started compiling. Ports which did not compile (like evolution) were installed as package.
> >
> > As I started from scratch, I believed the notes in UPGRADING should not apply and I ignored all.
>
> Correct, you don't need to follow the UPDATING if you install it from
> scratch. But the question is that how did you start it from scratch?
I deleted all installed ports with pkg_delete -a, made a 'make clean' in /usr/ports and then I started to randomly install the ports I normally like to have on the machine.
>
> I don't think it will help, because the change between of
> evolution-2.32.1_1 and evolution-2.32.1_2 are for libnotify. Try to
> remove ~/.gconf*. Yes it will remove your settings if you have
> modified.
This I did already without success.
> > I never specified this ' with krb5'. Do you know which port uses this?
>
> Do you have NO_KERBEROS, WITH_HEIMDAL or HEIMDAL_HOME in your
> make.conf or anywhere? It's supposed to be install security/heimdal if
> you have one of define in somewhere.
>
HEIMDAL_HOME is in make.conf
Should I add the NO_KERBEROS?
Erich
More information about the freebsd-gnome
mailing list