GNOME Bugzilla – Bug 499848
crash in Tasks:
Last modified: 2007-12-04 16:13:56 UTC
Version: 2.10 What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 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: 147775488 vsize: 147775488 resident: 65024000 share: 41148416 rss: 65024000 rss_rlim: 4294967295 CPU usage: start_time: 1196070097 rtime: 3633 utime: 3209 stime: 424 cutime:2848 cstime: 238 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 -1208526096 (LWP 3030)] [New Thread -1326941296 (LWP 6771)] [New Thread -1223189616 (LWP 6770)] [New Thread -1368900720 (LWP 6769)] [New Thread -1247446128 (LWP 3105)] [New Thread -1233679472 (LWP 3055)] 0x00110402 in __kernel_vsyscall ()
+ Trace 179755
Thread 4 (Thread -1368900720 (LWP 6769))
----------- .xsession-errors --------------------- e-utils-Message: e_dialog_combo_box_set(): could not find value 0 in value map! (evolution:3030): Gtk-CRITICAL **: gtk_font_button_set_font_name: assertion `fontname != NULL' failed (evolution:3030): Gtk-CRITICAL **: gtk_font_button_set_font_name: assertion `fontname != NULL' failed (evolution:3030): 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:3030): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xae0e008' (evolution:3030): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xae0e128' Cannot access memory at address 0x3406d044 Cannot access memory at address 0xfffff7fc Cannot access memory at address 0xfffff7fc --------------------------------------------------
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Could you please install some debugging packages [1] 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! [1] debugging packages for evolution, evolution-data-server and gtkhtml, plus debugging packages for some basic GNOME libs. More details can be found here: http://live.gnome.org/GettingTraces/DistroSpecificInstructions If you can reproduce it while running Evolution under gdb (see http://live.gnome.org/GettingTraces/Details#gdb-not-yet-running for details about how to do this), that might help getting a better trace if you've already got debug packages installed.
I already have evolution-debuginfo and evolution-data-server-debuginfo and most of the gnome debugging packages. Specifically, which packages do you need me to add?
Don't know Akhil is missing. But this is bug 427105 (which needs info) anyway. *** This bug has been marked as a duplicate of 427105 ***