After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 575298 - Clicking on certain IMAP email crashes Evolution
Clicking on certain IMAP email crashes Evolution
Status: RESOLVED DUPLICATE of bug 520233
Product: evolution-data-server
Classification: Platform
Component: Mailer
2.24.x (obsolete)
Other All
: High critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
: 576471 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-03-13 22:46 UTC by Andrea Mayer
Modified: 2009-03-24 04:24 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Attachments
mail that causes Evolution to crash in mbox format (5.43 KB, application/octet-stream)
2009-03-16 20:56 UTC, Andrea Mayer
Details

Description Andrea Mayer 2009-03-13 22:46:52 UTC
Steps to reproduce:
1. Open Evolution
2. Click on a certain email (does not happen with all emails)
3. Evolution crashes


Stack trace:
devvv@germania:~$ gdb evolution
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu"...
(gdb) run
Starting program: /usr/bin/evolution 
[Thread debugging using libthread_db enabled]
[New Thread 0x7f486b0cf790 (LWP 6651)]
** (evolution:6651): DEBUG: mailto URL command: evolution %s
** (evolution:6651): DEBUG: mailto URL program: evolution
[New Thread 0x41007950 (LWP 6658)]
[Thread 0x41007950 (LWP 6658) exited]
[New Thread 0x41007950 (LWP 6659)]
[Thread 0x41007950 (LWP 6659) exited]
[New Thread 0x4232f950 (LWP 6660)]
[Thread 0x4232f950 (LWP 6660) exited]
[New Thread 0x4232f950 (LWP 6661)]
[New Thread 0x41007950 (LWP 6662)]
[New Thread 0x41823950 (LWP 6663)]
[New Thread 0x42b30950 (LWP 6664)]
[Thread 0x41823950 (LWP 6663) exited]
[New Thread 0x41823950 (LWP 6665)]
[New Thread 0x43331950 (LWP 6666)]
[Thread 0x42b30950 (LWP 6664) exited]
[New Thread 0x42b30950 (LWP 6671)]
[New Thread 0x43b32950 (LWP 6672)]
[Thread 0x43b32950 (LWP 6672) exited]
[Thread 0x41823950 (LWP 6665) exited]
[Thread 0x4232f950 (LWP 6661) exited]
[Thread 0x43331950 (LWP 6666) exited]
[Thread 0x42b30950 (LWP 6671) exited]
[Thread 0x41007950 (LWP 6662) exited]
[New Thread 0x41007950 (LWP 6680)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x41007950 (LWP 6680)]
0x00007f4852a0fae3 in ?? ()
   from /usr/lib/evolution-data-server-1.2/camel-providers/libcamelimap.so

(gdb)       thread apply all bt 



Other information:
Comment 1 Matthew Barnes 2009-03-13 23:30:49 UTC
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!
Comment 2 Andrea Mayer 2009-03-15 11:46:00 UTC
(gdb) run
Starting program: /usr/bin/evolution 
[Thread debugging using libthread_db enabled]
[New Thread 0x7f5679bcf790 (LWP 6846)]
** (evolution:6846): DEBUG: mailto URL command: evolution %s
** (evolution:6846): DEBUG: mailto URL program: evolution
[New Thread 0x41095950 (LWP 6854)]
[Thread 0x41095950 (LWP 6854) exited]
[New Thread 0x41095950 (LWP 6855)]
[Thread 0x41095950 (LWP 6855) exited]
[New Thread 0x425f0950 (LWP 6857)]
[Thread 0x425f0950 (LWP 6857) exited]
[New Thread 0x425f0950 (LWP 6858)]
[New Thread 0x41095950 (LWP 6859)]
[New Thread 0x41896950 (LWP 6860)]
[New Thread 0x42df1950 (LWP 6861)]
[Thread 0x41896950 (LWP 6860) exited]
[New Thread 0x41896950 (LWP 6862)]
[New Thread 0x435f2950 (LWP 6863)]
[Thread 0x42df1950 (LWP 6861) exited]
[New Thread 0x42df1950 (LWP 6867)]
[Thread 0x425f0950 (LWP 6858) exited]
[Thread 0x41896950 (LWP 6862) exited]
[Thread 0x435f2950 (LWP 6863) exited]
[Thread 0x42df1950 (LWP 6867) exited]
[New Thread 0x42df1950 (LWP 6870)]
[Thread 0x42df1950 (LWP 6870) exited]
[Thread 0x41095950 (LWP 6859) exited]
[New Thread 0x41095950 (LWP 6887)]
[New Thread 0x42df1950 (LWP 6888)]
[New Thread 0x435f2950 (LWP 6889)]
[Thread 0x42df1950 (LWP 6888) exited]
[Thread 0x41095950 (LWP 6887) exited]
[Thread 0x435f2950 (LWP 6889) exited]
[New Thread 0x435f2950 (LWP 6890)]
[New Thread 0x41095950 (LWP 6891)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x435f2950 (LWP 6890)]
0x00007f56605c2ae3 in imap_body_decode (in=0x435f1ef8, ci=0x1c89540, folder=0x181e490, cis=<value optimized out>)
    at camel-imap-utils.c:932
932	camel-imap-utils.c: No such file or directory.
	in camel-imap-utils.c
(gdb) thread apply all bt

Thread 16 (Thread 0x435f2950 (LWP 6890))

  • #0 imap_body_decode
    at camel-imap-utils.c line 932
  • #1 imap_parse_body
    at camel-imap-utils.c line 1119
  • #2 imap_get_message
    at camel-imap-folder.c line 2916
  • #3 camel_folder_get_message
    at camel-folder.c line 1126
  • #4 get_message_exec
    at mail-ops.c line 1824
  • #5 mail_msg_proxy
    at mail-mt.c line 520
  • #6 g_thread_pool_thread_proxy
    at /build/buildd/glib2.0-2.18.2/glib/gthreadpool.c line 265
  • #7 g_thread_create_proxy
    at /build/buildd/glib2.0-2.18.2/glib/gthread.c line 635
  • #8 start_thread
    from /lib/libpthread.so.0
  • #9 clone
    from /lib/libc.so.6
  • #10 ??

Comment 3 Matthew Barnes 2009-03-15 14:12:12 UTC
Thanks for the debugging information.

Would you mind posting a sample message in mbox format that demonstrates the crash, so we can reproduce it for ourselves more easily?  The message will be posted publicly, so please remove any sensitive information before doing so.
Comment 4 Andrea Mayer 2009-03-16 20:56:06 UTC
Created attachment 130782 [details]
mail that causes Evolution to crash in mbox format
Comment 5 Andrea Mayer 2009-03-16 20:56:38 UTC
I have attached the mail in mbox format.
Comment 6 Akhil Laddha 2009-03-24 04:15:42 UTC
*** Bug 576471 has been marked as a duplicate of this bug. ***
Comment 7 Akhil Laddha 2009-03-24 04:24:52 UTC
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.


*** This bug has been marked as a duplicate of 520233 ***