GNOME Bugzilla – Bug 327827
Evolution crashes when forwarding an email as an attachment
Last modified: 2006-07-31 18:05:15 UTC
Steps to reproduce: 1. Select email 2. Forward email 3. Send email to be forwarded Stack trace: (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) *** ABOVE MESSAGE REPEATED MULTIPLE TIMES *** [Thread debugging using libthread_db enabled] [New Thread -1229674272 (LWP 25542)] [New Thread -1294005328 (LWP 17572)] [New Thread -1282507856 (LWP 17341)] [New Thread -1290900560 (LWP 29314)] [New Thread -1274025040 (LWP 25563)] [New Thread -1265632336 (LWP 25562)] [New Thread -1247118416 (LWP 25561)] [New Thread -1255511120 (LWP 25558)] [New Thread -1238332496 (LWP 25547)] (no debugging symbols found) *** ABOVE MESSAGE REPEATED MULTIPLE TIMES *** 0xffffe410 in __kernel_vsyscall ()
+ Trace 65396
Thread 8 (Thread -1255511120 (LWP 25558))
Other information: Bug reported downstream - https://launchpad.net/products/evolution/+bug/29186 - Ubuntu Bug.
Bug also submitted downstream - https://launchpad.net/products/evolution/+bug/29186 - Ubuntu.
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
The following stack trace was generated by the evolution debug package: Backtrace was generated from '/usr/bin/evolution' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1229817632 (LWP 11928)] [New Thread -1280439376 (LWP 11944)] [New Thread -1272046672 (LWP 11943)] [New Thread -1263539280 (LWP 11934)] [New Thread -1255146576 (LWP 11933)] [New Thread -1245185104 (LWP 11932)] [New Thread -1236649040 (LWP 11930)] 0xffffe410 in ?? ()
+ Trace 66224
Thread 7 (Thread -1236649040 (LWP 11930))
hmm strange. the last one is even worse. It is useless with that many ?? question marks.
I hope the following bugtraces provide more info.. After installing the libedataserver1.2-4 and libebook1.2-5 packages, I have generated the following backtraces: "Obtaining a stack trace using just GDB" - http://live.gnome.org/GettingTraces Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1236493392 (LWP 13394)] 0xb7dcd539 in camel_object_cast () from /usr/lib/libcamel-1.2.so.0 (gdb) thread apply all bt
+ Trace 66309
Thread 7 (Thread -1236915280 (LWP 13702))
thanks. however the important part still misses debugging symbols:
+ Trace 66310
so please make somehow sure that /usr/lib/libcamel-1.2.so.0 and /usr/lib/evolution/2.4/components/libevolution-mail.so have debugging symbols. please install appropriate packages, like libcamel-dbg (or similar, depends on your distribution) and evolution-mail-dbg alternatively you can attach the mail causing this if (and only if) you are willing to make it public.
I have now installed the libcamel debug package for Ubuntu. As far as I know, I have had the evolution debug package installed from the early stages of working through this bug, it might not have the right debug symbols setup in it. The problem is this issue is that it is not one problematic email that is causing it, it applies to all emails. When I reply or forward an email, after two seconds of sending the mail, Evolution crashes. Here is the shortened output of my latest backtrace with the important section you are after. A full version of the backtrace is available at: https://launchpad.net/distros/ubuntu/+source/evolution/+bug/29186 (gdb) thread apply all bt
+ Trace 66344
Thread 6 (Thread -1237152848 (LWP 27496))
*** Bug 330299 has been marked as a duplicate of this bug. ***
Comment on bug #330299, says that it is fixed now. Naaman Campbell, Can you please test this with the latest version?
Sushma, After speaking with the submitter of bug #330299, it appears the fix to his problem was found by a configuration change on the Exchange server side. Also, further correspondance with the Evolution maintain for Ubuntu has confirmed that the package has not been updated in the current release, Breezy Badger. The submitter of bug #330299 could not have installed a newer version. The forwarding of/replying to emails still crashes Evolution.
Naaman: Could you update to evolution 2.6 and verify if this crash is still reproducible. I tried forwarding mail(different types of mail) as attachment. Is it specific to one mail or any mail which is forwarded. If its for specific mail you observe this issue, attach that mail.
Poornima: I have moved on from my previous employer, and do not have access to the user's environment that was causing the issue. The general consensus was to move to the next version of Ubuntu before cutting over to it in a production capacity - so the next version of Evolution would be used.. On the Ubuntu bugtracker (Malone), there is another bug reporter who claims to have confirmed the bug - please look at https://launchpad.net/bugs/29186 to continue the investigation into this bug.. Naaman.
Lokking at the downstream bug, the traces pointed out a *NULL* folder in send_queue_send, which is unlikely. Also, it is reported in 2.4 and lots of fixes have gone in after that. Hence, I am closing this bug. Please feel free to re-open this bug, with more information.