GNOME Bugzilla – Bug 474667
crash in Tasks: editing rules
Last modified: 2007-12-04 16:59:03 UTC
Version: 2.10 What were you doing when the application crashed? editing rules 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.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 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: 143761408 vsize: 143761408 resident: 61259776 share: 39542784 rss: 61259776 rss_rlim: 4294967295 CPU usage: start_time: 1189196144 rtime: 2799 utime: 2565 stime: 234 cutime:33 cstime: 21 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 -1208830240 (LWP 4884)] [New Thread -1219544176 (LWP 5003)] [New Thread -1304032368 (LWP 4946)] [New Thread -1284527216 (LWP 4924)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 161187
Thread 1 (Thread -1208830240 (LWP 4884))
----------- .xsession-errors (69 sec old) --------------------- (evolution:4884): camel-WARNING **: No from set for message (evolution:4884): camel-WARNING **: No from set for message (evolution:4884): camel-WARNING **: No from set for message (evolution:4884): camel-WARNING **: No from set for message DEBUG: virus (mbox:/home/jonadmin/.evolution/mail/local#virus) (evolution:4884): 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:4884): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x94e6128' (evolution:4884): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x94e6248' --------------------------------------------------
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 436128 ***