GNOME Bugzilla – Bug 484787
crash in Tasks: selecting multiple messa...
Last modified: 2007-10-08 21:06:18 UTC
Version: 2.10 What were you doing when the application crashed? selecting multiple messages 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.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 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: 138276864 vsize: 138276864 resident: 53182464 share: 36311040 rss: 53182464 rss_rlim: 4294967295 CPU usage: start_time: 1191861294 rtime: 891 utime: 569 stime: 322 cutime:0 cstime: 1 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 -1208768800 (LWP 3432)] [New Thread -1301570672 (LWP 3447)] [New Thread -1249764464 (LWP 3438)] (no debugging symbols found) 0x0012d402 in __kernel_vsyscall ()
+ Trace 168819
Thread 1 (Thread -1208768800 (LWP 3432))
----------- .xsession-errors (47 sec old) --------------------- (evolution:3432): 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:3432): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa34c248' (evolution:3432): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa34c368' Can't open file 'wordlist.db' in directory '/home/rick/.bogofilter'. error #2 - No such file or directory. Remember to register some spam and ham messages before you use bogofilter to evaluate mail for its probable spam status! Can't open file 'wordlist.db' in directory '/home/rick/.bogofilter'. error #2 - No such file or directory. Remember to register some spam and ham messages before you use bogofilter to evaluate mail for its probable spam status! --------------------------------------------------
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 ***