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 384163 - crash in Evolution:
crash in Evolution:
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: 2006-12-09 20:46 UTC by j.milliet
Modified: 2006-12-10 11:18 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description j.milliet 2006-12-09 20:46:36 UTC 
What were you doing when the application crashed?



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

Memory status: size: 180314112 vsize: 0 resident: 180314112 share: 0 rss: 55476224 rss_rlim: 0
CPU usage: start_time: 1165684847 rtime: 0 utime: 6157 stime: 0 cutime:5740 cstime: 0 timeout: 417 it_real_value: 0 frequency: 8

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1233000784 (LWP 11073)]
[New Thread -1321374816 (LWP 11124)]
[New Thread -1312982112 (LWP 11120)]
[New Thread -1269019744 (LWP 11089)]
[New Thread -1260590176 (LWP 11088)]
[New Thread -1277822048 (LWP 11083)]
[New Thread -1252197472 (LWP 11080)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 92879

Thread 6 (Thread -1277822048 (LWP 11083))

  • #0 __kernel_vsyscall
  • #1 waitpid
    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_message
    from /usr/lib/libcamel-provider-1.2.so.8
  • #16 camel_folder_summary_add_from_message
    from /usr/lib/libcamel-provider-1.2.so.8
  • #17 camel_local_summary_get_type
    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_add
    from /usr/lib/evolution-data-server-1.2/camel-providers-8/libcamellocal.so
  • #20 camel_mbox_folder_new
    from /usr/lib/evolution-data-server-1.2/camel-providers-8/libcamellocal.so
  • #21 camel_folder_append_message
    from /usr/lib/libcamel-provider-1.2.so.8
  • #22 camel_filter_driver_filter_message
    from /usr/lib/libcamel-provider-1.2.so.8
  • #23 camel_filter_driver_filter_folder
    from /usr/lib/libcamel-provider-1.2.so.8
  • #24 mail_fetch_mail
    from /usr/lib/evolution/2.8/components/libevolution-mail.so
  • #25 mail_fetch_mail
    from /usr/lib/evolution/2.8/components/libevolution-mail.so
  • #26 mail_enable_stop
    from /usr/lib/evolution/2.8/components/libevolution-mail.so
  • #27 e_msgport_reply
    from /usr/lib/libedataserver-1.2.so.7
  • #28 start_thread
    from /lib/tls/i686/cmov/libpthread.so.0
  • #29 clone
    from /lib/tls/i686/cmov/libc.so.6 






Comment 1


Baptiste Mille-Mathias





          2006-12-10 11:18:33 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 ***