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 506655 - crash in Email: I don't know. Maybe just...
crash in Email: I don't know. Maybe just...
Status: RESOLVED DUPLICATE of bug 348149
Product: evolution
Classification: Applications
Component: Mailer
unspecified
Other All
: High critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-01-01 08:52 UTC by josephcclin
Modified: 2008-01-10 04:15 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description josephcclin 2008-01-01 08:52:48 UTC
Version: 2.10

What were you doing when the application crashed?
I don't know. Maybe just writing a latex document.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 135180288 vsize: 135180288 resident: 38408192 share: 29278208 rss: 38408192 rss_rlim: 4294967295
CPU usage: start_time: 1198650866 rtime: 8789 utime: 6456 stime: 2333 cutime:178934 cstime: 10810 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208584480 (LWP 20037)]
[New Thread -1230963824 (LWP 16312)]
[New Thread -1252344944 (LWP 20096)]
[New Thread -1241855088 (LWP 20061)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 2 (Thread -1230963824 (LWP 16312))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/libc.so.6
  • #7 g_logv
    from /lib/libglib-2.0.so.0
  • #8 g_log
    from /lib/libglib-2.0.so.0
  • #9 g_assert_warning
    from /lib/libglib-2.0.so.0
  • #10 camel_key_table_lookup
    from /usr/lib/libcamel-1.2.so.10
  • #11 ??
    from /usr/lib/libcamel-1.2.so.10
  • #12 g_hash_table_foreach
    from /lib/libglib-2.0.so.0
  • #13 ??
    from /usr/lib/libcamel-1.2.so.10
  • #14 camel_index_write_name
    from /usr/lib/libcamel-1.2.so.10
  • #15 camel_folder_summary_info_new_from_message
    from /usr/lib/libcamel-provider-1.2.so.10
  • #16 camel_folder_summary_add_from_message
    from /usr/lib/libcamel-provider-1.2.so.10
  • #17 ??
    from /usr/lib/evolution-data-server-1.2/camel-providers/libcamellocal.so
  • #18 ??
    from /usr/lib/evolution-data-server-1.2/camel-providers/libcamellocal.so
  • #19 camel_local_summary_add
    from /usr/lib/evolution-data-server-1.2/camel-providers/libcamellocal.so
  • #20 ??
    from /usr/lib/evolution-data-server-1.2/camel-providers/libcamellocal.so
  • #21 camel_folder_append_message
    from /usr/lib/libcamel-provider-1.2.so.10
  • #22 camel_filter_driver_filter_message
    from /usr/lib/libcamel-provider-1.2.so.10
  • #23 camel_filter_driver_filter_folder
    from /usr/lib/libcamel-provider-1.2.so.10
  • #24 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #25 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #26 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #27 ??
    from /lib/libglib-2.0.so.0
  • #28 ??
    from /lib/libglib-2.0.so.0
  • #29 start_thread
    from /lib/libpthread.so.0
  • #30 clone
    from /lib/libc.so.6

Comment 1 Akhil Laddha 2008-01-10 04:15:13 UTC
Thanks for the bug report. This particular bug has already been reported into
our bug tracking system and partially fixed, but please feel free to report any further bugs you find. 

Please comment #122 in bug 348149

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