GNOME Bugzilla – Bug 300255
Crash when responding to Exchange Meeting Request
Last modified: 2005-04-27 13:45:15 UTC
Distribution: Debian 3.1 Package: Evolution Severity: critical Version: GNOME2.10.0 2.2.1 Gnome-Distributor: Ubuntu Synopsis: Crash when responding to Exchange Meeting Request Bugzilla-Product: Evolution Bugzilla-Component: Calendar Bugzilla-Version: 2.2.1 BugBuddy-GnomeVersion: 2.0 (2.10.0) Description: Description of the crash: I received an Email from an Outlook User through my company's Exchange Server into Evolution using the Evolution-Exchange plugin. Steps to reproduce the crash: 1. Receive meeting request including a .ics meeting request 2. Scroll down through the email to where the Accept/Reject/etc buttons are. 3. Click on "Accept" 4. Crash. Expected Results: A reply will be sent to the original meeting requester indicating that I will attend the meeting. How often does this happen? Every time. Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1228748416 (LWP 16254)] [New Thread -1280042064 (LWP 16262)] [New Thread -1271280720 (LWP 16261)] [New Thread -1262486608 (LWP 16259)] [New Thread -1252582480 (LWP 16258)] [New Thread -1244189776 (LWP 16257)] [New Thread -1235256400 (LWP 16256)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 58043
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-04-11 17:52 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "Evolution". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was debian-bugs@mikevitale.com. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Thanks for the bug report. This appears to be a unique stack trace, according to the simple-dup-finder, but it is missing a fair amount of information. Could you get a stack trace with debugging symbols? See http://live.gnome.org/GettingTraces for more information on how to do so.
Created attachment 45157 [details] Extended stack trace The following backtrace was obtained by performing the same steps as outlined above, and after installing the Ubuntu packages "libglib2.0-0-dbg libgtk2.0-0-dbg libgnomevfs2-0-dbg" as mentioned at http://live.gnome.org/GettingTraces/DistroSpecificInstructions. -Mike Vitale
Thanks for following up. That does look better, but is probably missing some key functions near the top of the trace and debugging info for them. Is there any chance you could install debug packages for evolution and evolution-data-server as well?
Created attachment 45180 [details] Yet another stack trace, with more system information Trying to help you get as much information as possible...If you know of any other packages that I can install that would help you track this bug down, please let me know. -Mike Vitale
-dev packages (e.g. evolution-dev) aren't what you want; it'd be -dbg packages (something like evolution-dbg) to get debugging information. Let me cc Sebastien since he's likely to know the exact package names.
Hoary doesn't has -dbg variants for all the applications. There is a debug build of the package without -dbg here: http://people.ubuntu.com/~seb128/hoary_dbgdebs/. Can you install evolution and evolution-data-server to get a debug backtrace with them ?
Sebastien: Why not? http://download.fedora.redhat.com/pub/fedora/linux/core/3/i386/debug/ (and similar links for other versions) makes life so much easier... Ubuntu isn't going to let Fedora show it up, is it? ;-)
Created attachment 45182 [details] Stacktrace after installing Sebastien's Evo -dbg packages. OK, I downloaded the four packages mentioned in the attachment from Sebastien's site, closed and restarted Evolution, and here's my latest stacktrace. -Mike Vitale
can you install evolution, evolution-exchange, libedataserver1.2-4 from the website ? Elijah: because nobody has worked on getting dbg for every package like that for the moment :) I've put debug packages online as a temporary workaround but we intend to fix that for breezy. The fedora solution is probably not optimal though, users still need to get there and to grab/install the required packages ... we will try to do better :)
Created attachment 45185 [details] Stacktrace after installing latest 2 packages. Stacktrace after installing evolution-exchange and libedataserver1.2.4 from Sebastien's site. -Mike
thanks for the backtraces but apparently you don't have evolution debug. There is also one function from libcamel1.2-3 ... with this both the backtrace should be complete!
Created attachment 45187 [details] After installing libcamel1.2-3 OK...I've re-installed the evolution_2.2.1.1-0ubuntu4_i386.deb package I downloaded from Sebastien's site (md5sum 588b5fb04a67950d5388c86aa76672d2), and downloaded and installed the libcamel1.2-3_1.2.1-0ubuntu1_i386.deb (md5sum bbaabd91a184a81f652cb85729d2769f). Here's the latest stacktrace. -Mike
Mike: You deserve the bug reporter of the year award. Granted, no such award exists, but your promptness in responding to gather more info is incredible. Thanks! I'm going to post the leading part of the stack trace here so we can catch any duplicates with the simple-dup-finder.
+ Trace 58085
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. Matches the stack trace in bug 272632 *** This bug has been marked as a duplicate of 272632 ***