GNOME Bugzilla – Bug 450752
crash in Tasks: Closing the
Last modified: 2007-06-25 00:18:59 UTC
Version: 2.10 What were you doing when the application crashed? Closing the "Preferences" menu in Evolution. I was only reviewing my settings and did not make any changes. 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: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 115802112 vsize: 115802112 resident: 45076480 share: 32251904 rss: 45076480 rss_rlim: 4294967295 CPU usage: start_time: 1182719811 rtime: 685 utime: 632 stime: 53 cutime:7 cstime: 13 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 -1208551712 (LWP 3346)] [New Thread -1284686960 (LWP 3415)] [New Thread -1220719728 (LWP 3387)] (no debugging symbols found) 0x00816402 in __kernel_vsyscall ()
+ Trace 143442
Thread 1 (Thread -1208551712 (LWP 3346))
----------- .xsession-errors (89 sec old) --------------------- Reloading options Reloading options Reloading options Reloading options Reloading options Reloading options Reloading options Reloading options (evolution:3346): 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:3346): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9788010' (evolution:3346): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9788130' --------------------------------------------------
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 435356 ***