GNOME Bugzilla – Bug 449609
crash in Evolution: I was forwarding an e-ma...
Last modified: 2008-09-02 06:08:58 UTC
Version: 2.12.x What were you doing when the application crashed? I was forwarding an e-mail. I'd started typing in the recepient's name (which was in my addressbook and had autocompleted) and here we are. Distribution: Slackware Slackware 11.0.0 Gnome Release: 2.19.4 2007-06-19 (GARNOME) BugBuddy Version: 2.18.1 System: Linux 2.6.21.5 #61 SMP Mon Jun 11 19:21:44 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 60900000 Selinux: No Accessibility: Enabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 65544192 vsize: 65544192 resident: 13807616 share: 9957376 rss: 13807616 rss_rlim: 4294967295 CPU usage: start_time: 1182362736 rtime: 33 utime: 30 stime: 3 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/opt/garnome-svn-2.19.4/libexec/evolution-exchange-storage' Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1236719392 (LWP 25425)] [New Thread -1254990928 (LWP 11340)] [New Thread -1237709904 (LWP 25426)] 0xb66cc071 in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 142522
Thread 1 (Thread -1236719392 (LWP 25425))
----------- .xsession-errors (302566561 sec old) --------------------- iceauth: creating new authority file /home/ronis/.ICEauthority --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
Unfortunately, I don't know how to reproduce this bug. I've tried forwarding similar e-mails and this time it works. My suspicion is that it had something to do with the interaction with our ldap server. Are you sure the current stack-trace isn't enough? I've built all of gnome with -g so you have much of the information you need vis-a-vis gnome; as to libldap, if indeed that is the problem, this probably isn't the place to file the report :)
Dude, that should have been NEEDINFO, not INCO. ;) Also, this probably is an OpenLDAP issue:
+ Trace 142745
However, we'd need debugging symbols for OpenLDAP, to tell more. Also, I assume you build GARNOME with -g enabled, David? The rest of the stacktrace (the parts where the code didn't crash) sure look like this. For best debugging results, please use -g when building, and preferably do not use optimization at all. In case you can reproduce this crash, but the stacktraces don't contain more function calls, we maybe should try running Evolution in gdb -- this may get us a better stacktrace.
(In reply to comment #2) > Unfortunately, I don't know how to reproduce this bug. I've tried forwarding > similar e-mails and this time it works. My suspicion is that it had something > to do with the interaction with our ldap server. > > Are you sure the current stack-trace isn't enough? I've built all of gnome > with -g so you have much of the information you need vis-a-vis gnome; as to > libldap, if indeed that is the problem, this probably isn't the place to file > the report :) Yup, the stacktrace is not good, unfortunately. See the top-most thread, right below the <signal handler called> line. This, however, may indeed be the case because it's openldap crashing...
Since this actually is evolution-exchange-storage, not Evolution itself... This page should give some hints how to run e-e-s in gdb, too. http://www.gnome.org/projects/evolution/bugs.shtml Evolution Exchange 2.11.4, right? Unfortunately, this version doesn't exist in bugzilla yet. *sigh*
I've not seen this problem again (I'm now using evolution- and evolution-exchange 2.11.15, with the same version of openldap). Either the bug was fixed (unlikely) or was caused by something non-gnome. In any event, perhaps this should be closed.
(In reply to comment #6) > In any event, perhaps this should be closed. > But then not as FIXED. Actually, bug 354442 looks pretty the same, but it's fixed since one year, so I think we've got another issue here. Actually there is at least one other guy facing the same issue, so reopening and marking it as dup of this one, since here is the better trace.
*** Bug 469542 has been marked as a duplicate of this bug. ***
Is this still reproducible? Can you please check this with the latest stable version Evolution 2.22.x and give us the stack trace if reproducible? Thanks in Advance. Please install debug packages for evolution, evolution-data-server, gtkhtml, gtk, glib, glibc, orbit2, gnome-vfs, pango, libgnome and libgnomeui (as far as those packages are provided by your distribution).
Please feel free to reopen this bug if the problem still occurs with a newer version of GNOME 2.22.3.1, thanks.