Crash when opening Exchange inbox in e2k_context_send_message

Bug #63715 reported by V S
4
Affects Status Importance Assigned to Milestone
evolution-exchange
Fix Released
Critical
evolution-exchange (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs
Hardy
Invalid
Medium
Unassigned

Bug Description

I've reported numerous crashes in the past in the Exchange backend, and I'm not sure if this is another one or not.

Simply, opening my inbox on an Exchange server crashes evolution-exchange-backend immediately.

Revision history for this message
V S (th-deactivatedaccount-deactivatedaccount) wrote :

PS. Makes evolution completely unusable for me.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your bug. What version of Ubuntu do you use? Maybe you could get a backtrace with a debug build of evolution-exchange? Does evolution crash too or it's unusable an another way or that's because you use it only for with an exchange server?

Changed in evolution:
assignee: nobody → desktop-bugs
status: Unconfirmed → Needs Info
Revision history for this message
V S (th-deactivatedaccount-deactivatedaccount) wrote :

I'm running the latest edgy.

I've installed evolution-dbg and evolution-data-server-dbg. What's the easiest way to get the exchange backend with debug symbols? Hand-compile from source?

It's unusable just 'cos I use only exchange, sorry for being ambiguous.

Revision history for this message
Sebastien Bacher (seb128) wrote :

to get a debug evolution-exchange add "deb http://people.ubuntu.com/~pitti/ddebs edgy main" to your apt sources list and install the evolution-exchange-dbgsym package

Revision history for this message
V S (th-deactivatedaccount-deactivatedaccount) wrote :

There's -dbgsym packages for evolution, evolution-data-server and evolution-plugins, but not for evolution-exchange.

Revision history for this message
Sebastien Bacher (seb128) wrote :

what architecture do you use?

"$ apt-cache show evolution-exchange-dbgsym | grep Filename
Filename: pool/main/e/evolution-exchange/evolution-exchange-dbgsym_2.8.1-0ubuntu1_amd64.ddeb"

Revision history for this message
V S (th-deactivatedaccount-deactivatedaccount) wrote :

Plain intel (i386/i686)

toni@toni-laptop:~$ uname -a
Linux toni-laptop 2.6.17-10-generic #2 SMP Mon Oct 2 13:48:24 UTC 2006 i686 GNU/Linux

Revision history for this message
V S (th-deactivatedaccount-deactivatedaccount) wrote :
  • bt Edit (3.8 KiB, text/plain)

Well,

I installed debug versions of evolution-exchange-server, libc6-i686 and others, and got the attached backtrace by hand. I'm really not sure if this is the same, because it didn't seem to crash instantaneously with the new packages.

(At least this one doesn't seem to be an evolution-exchange bug.)

Revision history for this message
Daniel Holbach (dholbach) wrote :

Can you get the debug symbols of evolution-data-server too and try again?

Revision history for this message
V S (th-deactivatedaccount-deactivatedaccount) wrote :

I already have them (evolution-data-server-dbg)

Revision history for this message
Sebastien Bacher (seb128) wrote :

could you install evolution-exchange-dbgsym from "deb http://people.ubuntu.com/~pitti/ddebs edgy main" and get a backtrace with it?

Revision history for this message
V S (th-deactivatedaccount-deactivatedaccount) wrote :

Oh, looks like the i386 packages have appeared. Okay, here's the latest.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for the work on that. It looks like the issue might be due to libsoup or gnutls, could you install libsoup2.2-8-dbgsym (it should be available tomorrow) and libgnutls13-dbg and get a new backtrace with gdb:
gdb evolution-exchange
(gdb) run

After that we should have all the required informations, sorry for the extra work required to install the debug packages etc, we are working to get automatic debug backtraces without having to ask users to install packages and get new backtraces, etc

Revision history for this message
V S (th-deactivatedaccount-deactivatedaccount) wrote :

Hmm, the evolution-exchange backend gets started when I log in, so I just attached to it using gdb. I hope this is OK.

Revision history for this message
V S (th-deactivatedaccount-deactivatedaccount) wrote :

And here's another report, this one by bug buddy.

Revision history for this message
Daniel Holbach (dholbach) wrote :

Gaim crashes in the same gnutls bits in bug 51272. We can't rule out breakage in gnutls.

Revision history for this message
V S (th-deactivatedaccount-deactivatedaccount) wrote :

Why is this still tagged as needs information? What information do you need? Network sniffs, more gdb stuff, strace/ltrace, what?

Revision history for this message
Sebastien Bacher (seb128) wrote :

Nothing else required, there is thousand of desktop bugs and only few people working on them so it takes time to reply, I've forwarded your bug with the debug backtrace upstream: http://bugzilla.gnome.org/show_bug.cgi?id=402752

Changed in evolution:
importance: Undecided → Medium
status: Needs Info → Confirmed
Changed in evolution-exchange:
status: Unknown → Unconfirmed
Changed in evolution-exchange:
status: New → Fix Released
Revision history for this message
Pedro Villavicencio (pedro) wrote :

fixed upstream, thanks for reporting!.

Changed in evolution-exchange:
status: Confirmed → Fix Committed
Revision history for this message
Sebastien Bacher (seb128) wrote :

there is no need to have a specific hardy bug for this one, using bug #236781 for the update rather

Changed in evolution-exchange:
importance: Undecided → Medium
status: New → Confirmed
status: Confirmed → Invalid
Revision history for this message
Sebastien Bacher (seb128) wrote :

there is a new version in intrepid

Changed in evolution-exchange:
status: Fix Committed → Fix Released
Changed in evolution-exchange:
importance: Unknown → Critical
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.