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 396390 - crash in Evolution: I were sending a mail
crash in Evolution: I were sending a mail
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-14 11:02 UTC by orvaquim
Modified: 2007-01-15 00:15 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description orvaquim 2007-01-14 11:02:00 UTC
What were you doing when the application crashed?
I were sending a mail


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

Memory status: size: 188919808 vsize: 0 resident: 188919808 share: 0 rss: 55943168 rss_rlim: 0
CPU usage: start_time: 1168712247 rtime: 0 utime: 6544 stime: 0 cutime:6177 cstime: 0 timeout: 367 it_real_value: 0 frequency: 0

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 -1232935248 (LWP 6248)]
[New Thread -1309668448 (LWP 22290)]
[New Thread -1300370528 (LWP 6276)]
[New Thread -1272927328 (LWP 6275)]
[New Thread -1300104288 (LWP 6274)]
[New Thread -1281320032 (LWP 6273)]
[New Thread -1264534624 (LWP 6257)]
[New Thread -1256105056 (LWP 6253)]
[New Thread -1247712352 (LWP 6252)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 9 (Thread -1247712352 (LWP 6252))

  • #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_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 mail_send_queue
    from /usr/lib/evolution/2.8/components/libevolution-mail.so
  • #25 mail_enable_stop
    from /usr/lib/evolution/2.8/components/libevolution-mail.so
  • #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-15 00:15:32 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 ***