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 400981 - crash in Evolution: Sending email
crash in Evolution: Sending email
Status: RESOLVED DUPLICATE of bug 348149
Product: evolution
Classification: Applications
Component: general
2.8.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-01-26 12:26 UTC by jnowak
Modified: 2007-01-27 00:54 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description jnowak 2007-01-26 12:26:19 UTC 
What were you doing when the application crashed?
Sending email


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 210550784 vsize: 0 resident: 210550784 share: 0 rss: 34963456 rss_rlim: 0
CPU usage: start_time: 1169811499 rtime: 0 utime: 1131 stime: 0 cutime:1057 cstime: 0 timeout: 74 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/evolution-2.8'

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1233086800 (LWP 32089)]
[New Thread -1395885152 (LWP 32146)]
[New Thread -1387492448 (LWP 32144)]
[New Thread -1378751584 (LWP 32105)]
[New Thread -1369687136 (LWP 32104)]
[New Thread -1361294432 (LWP 32103)]
[New Thread -1303909472 (LWP 32099)]
[New Thread -1295119456 (LWP 32096)]
[New Thread -1286558816 (LWP 32094)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 105406

Thread 6 (Thread -1361294432 (LWP 32103))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libc.so.6
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/tls/i686/cmov/libc.so.6
  • #6 abort
    from /lib/tls/i686/cmov/libc.so.6
  • #7 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #8 g_log
    from /usr/lib/libglib-2.0.so.0
  • #9 g_assert_warning
    from /usr/lib/libglib-2.0.so.0
  • #10 camel_key_table_lookup
    from /usr/lib/libcamel-1.2.so.8
  • #11 camel_text_index_new
    from /usr/lib/libcamel-1.2.so.8
  • #12 g_hash_table_foreach
    from /usr/lib/libglib-2.0.so.0
  • #13 camel_text_index_new
    from /usr/lib/libcamel-1.2.so.8
  • #14 camel_index_write_name
    from /usr/lib/libcamel-1.2.so.8
  • #15 camel_folder_summary_info_new_from_parser
    from /usr/lib/libcamel-provider-1.2.so.8
  • #16 camel_folder_summary_add_from_parser
    from /usr/lib/libcamel-provider-1.2.so.8
  • #17 camel_mbox_summary_new
    from /usr/lib/evolution-data-server-1.2/camel-providers-8/libcamellocal.so
  • #18 camel_mbox_summary_new
    from /usr/lib/evolution-data-server-1.2/camel-providers-8/libcamellocal.so
  • #19 camel_local_summary_check
    from /usr/lib/evolution-data-server-1.2/camel-providers-8/libcamellocal.so
  • #20 camel_mbox_summary_new
    from /usr/lib/evolution-data-server-1.2/camel-providers-8/libcamellocal.so
  • #21 camel_local_summary_sync
    from /usr/lib/evolution-data-server-1.2/camel-providers-8/libcamellocal.so
  • #22 camel_local_folder_construct
    from /usr/lib/evolution-data-server-1.2/camel-providers-8/libcamellocal.so
  • #23 camel_folder_sync
    from /usr/lib/libcamel-provider-1.2.so.8
  • #24 send_queue_send
    at mail-ops.c line 779
  • #25 mail_msg_received
    at mail-mt.c line 570
  • #26 e_msgport_reply
    from /usr/lib/libedataserver-1.2.so.7
  • #27 start_thread
    from /lib/tls/i686/cmov/libpthread.so.0
  • #28 clone
    from /lib/tls/i686/cmov/libc.so.6 






Comment 1


palfrey





          2007-01-27 00:54:14 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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