Date: Fri, 2 Jun 2006 13:34:14 GMT From: Mark Evenson <mark.evenson@gmx.at> To: freebsd-gnats-submit@FreeBSD.org Subject: ports/98377: evolution 2.6.2 has stopped working with Exchange Message-ID: <200606021334.k52DYEI3068564@www.freebsd.org> Resent-Message-ID: <200606021340.k52DeEOV038672@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 98377 >Category: ports >Synopsis: evolution 2.6.2 has stopped working with Exchange >Confidential: no >Severity: critical >Priority: medium >Responsible: freebsd-ports-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Jun 02 13:40:13 GMT 2006 >Closed-Date: >Last-Modified: >Originator: Mark Evenson >Release: RELENG_6_1 >Organization: >Environment: FreeBSD elvis.intern.etel.at 6.1-RELEASE FreeBSD 6.1-RELEASE #0: Mon May 22 14:32:02 CEST 2006 evenson@elvis.intern.etel.at:/usr/obj/usr/src/sys/GENERIC i386 >Description: After upgrading to mail/evolution-2.6.2 and mail/evolution-exchange-2.6.2 via "portupgrade -a", the Evolution email client has stopped working with our Microsoft Exchange server. The initial scan of the mailboxes completes, but then the evolution process freezes when attempting to actually access the remote messages. I rebuilt both ports with debugging symbols trying to follow where the problem occurs (and trying to get a reasonable backtrace) without much luck. The best I could figure is that some message pumped through evolution-exchange whacks the stack, which then (somehow) this message is mistakenly passed to evolution which then freezes. Sometimes the app stays frozen, sometimes the GNOME Bug Reporter intercepts whatever signal is being thrown (presumably SIGSEGV), but it never seems to work correctly (no core dump). The same setup in the same user account works with mail/evolution-2.6.1 and mail/evolution-exchange-2.6.1, so it doesn't appear to be corrupt local data. As far as I know, the Exchange server setup has not been modified (I don't admin the service, nor do I really know who to ask). -- evolution-exchange complains about a lot of "unescaped entity reference" (for all the umlauts usw.) when it starts up to stdout, but it does this in the previous version as well. -- My gknowledge of GNOME and Evolution is rather scant, so meaningful debugging by using gdb is going to take me quite a bit more time. I'd be happy to follow instructions to produce backtraces or stackdumps if someone can give me a few pointers. . . >How-To-Repeat: Install mail/evolution-2.6.2 and mail/evolution-exchange-2.6.2, then try to talk to my Exchange server ;) >Fix: Use sysutils/portdowngrade to move both mail/evolution and mail/evolution-exchange back to the CVS commit before the one with "2.6.2" in the comments. >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200606021334.k52DYEI3068564>