GNOME Bugzilla – Bug 448065
crash in Tasks: reading email
Last modified: 2007-07-02 22:29:12 UTC
What were you doing when the application crashed? reading email 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.3194.fc7 #1 SMP Wed May 23 22:35:01 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: 128253952 vsize: 128253952 resident: 50888704 share: 31993856 rss: 50888704 rss_rlim: 4294967295 CPU usage: start_time: 1181942372 rtime: 3356 utime: 1041 stime: 2315 cutime:0 cstime: 20 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 -1209137440 (LWP 15150)] [New Thread -1301570672 (LWP 20354)] [New Thread -1343530096 (LWP 20353)] [New Thread -1290318960 (LWP 15223)] [New Thread -1261438064 (LWP 15188)] [New Thread -1228379248 (LWP 15185)] (no debugging symbols found) 0x00ae5402 in __kernel_vsyscall ()
+ Trace 141338
Thread 1 (Thread -1209137440 (LWP 15150))
----------- .xsession-errors (63 sec old) --------------------- libnm_glib_nm_state_cb: dbus returned an error. (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files (evolution:15150): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?) BBDB spinning up... (evolution:15150): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x96b4020' (evolution:15150): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x96b4140' (evolution:15150): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?) (evolution:15150): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x96b4260' (evolution:15150): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x96b4380' --------------------------------------------------
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
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.
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 444924 ***