GNOME Bugzilla – Bug 479187
crash in Tasks: Setting preferences in t...
Last modified: 2007-09-29 01:14:06 UTC
What were you doing when the application crashed? Setting preferences in the Evolution -> General tab. Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Mist Icon Theme: gnome Memory status: size: 132722688 vsize: 132722688 resident: 32722944 share: 20807680 rss: 32722944 rss_rlim: 4294967295 CPU usage: start_time: 1190444565 rtime: 1114 utime: 1040 stime: 74 cutime:126 cstime: 25 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 -1208875296 (LWP 4782)] [New Thread -1282954352 (LWP 4819)] [New Thread -1251366000 (LWP 4814)] [New Thread -1229993072 (LWP 4802)] (no debugging symbols found) 0x00d27402 in __kernel_vsyscall ()
+ Trace 164588
Thread 1 (Thread -1208875296 (LWP 4782))
----------- .xsession-errors (103 sec old) --------------------- (evolution:4782): gtkhtml-WARNING **: No such file or directory (evolution:4782): gtkhtml-WARNING **: No such file or directory (evolution:4782): gtkhtml-WARNING **: No such file or directory (evolution:4782): gtkhtml-WARNING **: Bad address (evolution:4782): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0 (evolution:4782): 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:4782): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8c7f260' (evolution:4782): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8c7f380' --------------------------------------------------
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 464159 ***