GNOME Bugzilla – Bug 482061
crash in Tasks: add signature
Last modified: 2007-10-06 12:36:40 UTC
Version: 2.10 What were you doing when the application crashed? add signature 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.3194.fc7 #1 SMP Wed May 23 22:11:19 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: 134180864 vsize: 134180864 resident: 52101120 share: 34099200 rss: 52101120 rss_rlim: 4294967295 CPU usage: start_time: 1191207832 rtime: 948 utime: 897 stime: 51 cutime:32 cstime: 11 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 -1208867104 (LWP 3988)] [New Thread -1276716144 (LWP 4044)] [New Thread -1265165424 (LWP 4042)] [New Thread -1221125232 (LWP 4013)] (no debugging symbols found) 0x00f43402 in __kernel_vsyscall ()
+ Trace 166755
Thread 1 (Thread -1208867104 (LWP 3988))
----------- .xsession-errors (50 sec old) --------------------- (evolution:3988): gtkhtml-WARNING **: Selection retrieval failed (evolution:3988): gtkhtml-WARNING **: Selection retrieval failed (evolution:3988): gtkhtml-WARNING **: Selection retrieval failed (evolution:3988): 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:3988): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8bd27e8' (evolution:3988): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8bd2908' --------------------------------------------------
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 426807 ***