GNOME Bugzilla – Bug 476895
crash in Tasks: Tabbing through Evolutio...
Last modified: 2007-09-22 19:08:16 UTC
Version: 2.10 What were you doing when the application crashed? Tabbing through Evolution Preferences Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 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: 142077952 vsize: 142077952 resident: 51585024 share: 36110336 rss: 51585024 rss_rlim: 4294967295 CPU usage: start_time: 1189771830 rtime: 743 utime: 688 stime: 55 cutime:0 cstime: 0 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 -1208437024 (LWP 3211)] [New Thread -1299170416 (LWP 4852)] [New Thread -1259349104 (LWP 4851)] [New Thread -1248859248 (LWP 4831)] [New Thread -1298097264 (LWP 3251)] [New Thread -1238369392 (LWP 3221)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 162879
Thread 3 (Thread -1259349104 (LWP 4851))
----------- .xsession-errors (36 sec old) --------------------- (evolution:3211): e-dateedit.c-WARNING **: time_text:10:00 AM (evolution:3211): e-dateedit.c-WARNING **: time_text:10:30 AM (evolution:3211): e-dateedit.c-WARNING **: time_text:10:00 AM (evolution:3211): e-dateedit.c-WARNING **: time_text:10:30 AM (evolution:3211): 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:3211): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x95f9260' (evolution:3211): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x95f9380' --------------------------------------------------
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 460409 ***