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 535363 - crash in Evolution Mail:
crash in Evolution Mail:
Status: RESOLVED DUPLICATE of bug 519536
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.22.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-05-28 22:11 UTC by Claudio
Modified: 2008-09-23 16:11 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Claudio 2008-05-28 22:11:45 UTC 
What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.22.1 2008-04-08 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-amd64 #1 SMP Sat May 10 09:28:10 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Enabled
GTK+ Theme: Clearlooks
Icon Theme: dlg-neu

Memory status: size: 456314880 vsize: 456314880 resident: 45445120 share: 23900160 rss: 45445120 rss_rlim: 18446744073709551615
CPU usage: start_time: 1212012796 rtime: 405 utime: 361 stime: 44 cutime:4 cstime: 9 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0x2b7114aa3a20 (LWP 8084)]
[New Thread 0x40040950 (LWP 8186)]
[New Thread 0x41802950 (LWP 8184)]
[New Thread 0x42003950 (LWP 8110)]
0x00002b710a436edf in waitpid () from /lib/libpthread.so.0

+ Trace 198909

Thread 1 (Thread 0x2b7114aa3a20 (LWP 8084))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 <signal handler called>
  • #5 activity_info_free
    at e-activity-handler.c line 157
  • #6 cancel_wrapper
    at e-activity-handler.c line 397
  • #7 button_press_event_cb
    at e-task-widget.c line 134
  • #8 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #9 ??
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #13 ??
    from /usr/lib/libgobject-2.0.so.0
  • #14 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #15 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #16 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #17 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #18 ??
    from /usr/lib/libgobject-2.0.so.0
  • #19 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #20 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #21 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #22 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #23 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #24 ??
    from /usr/lib/libgobject-2.0.so.0
  • #25 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #26 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #27 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #28 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #29 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #30 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #31 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #32 ??
    from /usr/lib/libglib-2.0.so.0
  • #33 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #34 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #35 main
    at main.c line 782
  • #36 __libc_start_main
    from /lib/libc.so.6
  • #37 _start
  • #0 waitpid
    from /lib/libpthread.so.0 


----------- .xsession-errors (98672 sec old) ---------------------
(evolution:11822): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed
(evolution:11822): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed
(evolution:11822): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed
(evolution:11822): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed
(evolution:11822): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed
(evolution:11822): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed
(evolution:11822): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Akhil Laddha 2008-05-29 04:54:40 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.
Could you please install some debugging packages [1], start the application as
normal, and reproduce the crash, if possible?

Once bug-buddy pops up, you can find the stacktrace in the Details, now
containing way more information. Please copy that stacktrace and paste it as a
comment here. Thanks in advance!

[1] debugging packages for evolution, evolution-data-server, evolution-exchange, gtkhtml, gtk, glib, libsoup, gnome-vfs, libgnome, orbit2 and libgnomeui (as far as those packages are provided by your distribution). More details can be found here:
http://live.gnome.org/GettingTraces
Comment 2 Milan Crha 2008-09-23 16:11:55 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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