GNOME Bugzilla – Bug 450225
crash in Tasks: trying to change setting...
Last modified: 2007-06-29 16:45:20 UTC
Version: 2.10 What were you doing when the application crashed? trying to change settings to empty deleted items on exit 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 15:37:31 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Bluecurve Icon Theme: Bluecurve Memory status: size: 244465664 vsize: 244465664 resident: 92393472 share: 66199552 rss: 92393472 rss_rlim: 4294967295 CPU usage: start_time: 1182550229 rtime: 4079 utime: 3840 stime: 239 cutime:1247 cstime: 130 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 -1208953120 (LWP 3560)] [New Thread -1374913648 (LWP 3761)] [New Thread -1283331184 (LWP 3641)] [New Thread -1271104624 (LWP 3598)] (no debugging symbols found) 0x004c4402 in __kernel_vsyscall ()
+ Trace 143018
Thread 1 (Thread -1208953120 (LWP 3560))
----------- .xsession-errors (80 sec old) --------------------- (evolution:3560): camel-WARNING **: No from set for message (evolution:3560): camel-WARNING **: No from set for message report junk?? Complete Health Coverage For All (evolution:3560): Gtk-CRITICAL **: gtk_toggle_button_get_active: assertion `GTK_IS_TOGGLE_BUTTON (toggle_button)' failed (evolution:3560): 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:3560): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x91ac130' (evolution:3560): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x91ac250' --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find *** This bug has been marked as a duplicate of 426227 ***