GNOME Bugzilla – Bug 450718
crash in Tasks: REviewing preferences
Last modified: 2007-06-25 00:16:35 UTC
Version: 2.10 What were you doing when the application crashed? REviewing preferences 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.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 538165248 vsize: 538165248 resident: 49594368 share: 33132544 rss: 49594368 rss_rlim: 18446744073709551615 CPU usage: start_time: 1182712381 rtime: 752 utime: 693 stime: 59 cutime:39 cstime: 22 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496414304 (LWP 3304)] [New Thread 1126455632 (LWP 3413)] [New Thread 1126189392 (LWP 3375)] (no debugging symbols found) 0x0000003cb900d89f in waitpid () from /lib64/libpthread.so.0
+ Trace 143415
Thread 1 (Thread 46912496414304 (LWP 3304))
----------- .xsession-errors (52 sec old) --------------------- (evolution:3304): camel-pop3-provider-WARNING **: Bad server response: . (evolution:3304): camel-pop3-provider-WARNING **: Bad server response: . (evolution:3304): camel-pop3-provider-WARNING **: Bad server response: . (evolution:3304): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib64/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?) BBDB spinning up... (evolution:3304): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x871140' (evolution:3304): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x870b40' --------------------------------------------------
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 436043 ***