I have the same problem, as described by Timothy. Started from the command 
line, Evolution produces the following output:
<code>
libexchangemapi-Message: exchange-mapi-connection.c:2880: 
exchange_mapi_create_profile: lock(connect_lock)
Unknown parameter encountered: "max log size"
Ignoring unknown parameter "max log size"
Unknown parameter encountered: "syslog"
Ignoring unknown parameter "syslog"
Unknown parameter encountered: "passdb backend"
Ignoring unknown parameter "passdb backend"
Unknown parameter encountered: "unix password sync"
Ignoring unknown parameter "unix password sync"
Unknown parameter encountered: "passwd program"
Ignoring unknown parameter "passwd program"
Unknown parameter encountered: "pam password change"
Ignoring unknown parameter "pam password change"
Unknown parameter encountered: "map to guest"
Ignoring unknown parameter "map to guest"
Unknown parameter encountered: "usershare allow guests"
Ignoring unknown parameter "usershare allow guests"
Unknown parameter encountered: "guest ok"
Ignoring unknown parameter "guest ok"
Unknown parameter encountered: "guest ok"
Ignoring unknown parameter "guest ok"
Logging into the server... succeeded 
libexchangemapi-Message: exchange-mapi-connection.c:146: 
exchange_mapi_connection_close: lock(connect_lock)
Segmentation fault (core dumped)
</code>

So it seems that it succeeds with authentication but crashes immediately
upon it. If you look at <tt>~/.evolution/mapi-profiles.ldb</tt>, you
will see that there is a profile inside.

I have taken a look at the evolution-mapi source package. It seems to me
that the <tt>SIGSEGV</tt> happens in  <tt>src/libexchangemapi/exchange-
mapi-connection.c:148</tt>

<code>
void
exchange_mapi_connection_close ()
{
  LOCK();
  global_mapi_session = NULL;
  MAPIUninitialize (); // <- here is where we get a SIGSEGV
  UNLOCK();
  /* TODO :  Return status. get last error ? */
}
</code>

-- 
evolution crashed with SIGSEGV trying to authenticate with MAPI
https://bugs.launchpad.net/bugs/348621
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to