GNOME Bugzilla – Bug 448938
crash in Tasks:
Last modified: 2007-07-26 21:47:39 UTC
Version: 2.10 What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 621584384 vsize: 621584384 resident: 49938432 share: 35086336 rss: 49938432 rss_rlim: 18446744073709551615 CPU usage: start_time: 1182204831 rtime: 163 utime: 136 stime: 27 cutime:2 cstime: 5 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496516704 (LWP 17134)] [New Thread 1136945488 (LWP 17192)] [New Thread 1126189392 (LWP 17190)] [New Thread 1105209680 (LWP 17171)] [New Thread 1084229968 (LWP 17168)] (no debugging symbols found) 0x0000003422c0d89f in waitpid () from /lib64/libpthread.so.0
+ Trace 141999
Thread 3 (Thread 1126189392 (LWP 17190))
----------- .xsession-errors (53065 sec old) --------------------- (evolution:3884): e-activity-handler.c-WARNING **: e_activity_handler_operation_finished: Unknown activity 10922 (evolution:3884): e-activity-handler.c-WARNING **: e_activity_handler_operation_finished: Unknown activity 10922 (evolution:3884): e-activity-handler.c-WARNING **: e_activity_handler_operation_finished: Unknown activity 10922 (evolution:3884): e-activity-handler.c-WARNING **: e_activity_handler_operation_finished: Unknown activity 10922 ...Too much output, ignoring rest... --------------------------------------------------
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, gtkhtml, gtk, glib, gnome-vfs, pango, libgnome and libgnomeui (as far as those packages are provided by your distribution). More details can be found here: http://live.gnome.org/GettingTraces Also, this bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a more useful description to this bug.
Unfortunately the stacktrace does not have any hints about the real cause of the crash and does not help in debugging this issue. For some yet unknown reason, such stacktraces are pretty common currently on certain distributions. However, almost all of them do turn out to be filed already, once we managed to gather a useful stacktrace. To do so, simply install the corresponding debugging packages and reproduce the issue, if possible. The resulting stacktrace (see bug-buddy details) will help us to identify and fix the issue. Just in case you ever can reproduce this crash later, please consider installing debugging packages [1] and either reopen this bug report or simply file a new one with the resulting stacktrace. Thanks! Closing this bug report as no further information has been provided.
*** This bug has been marked as a duplicate of 339602 ***