GNOME Bugzilla – Bug 504798
crash in Tasks: Changing folders
Last modified: 2008-02-11 04:49:07 UTC
Version: 2.10 What were you doing when the application crashed? Changing folders Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.8-34.fc7 #1 SMP Thu Nov 22 23:05:33 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: ThinIce Icon Theme: Echo Memory status: size: 151138304 vsize: 151138304 resident: 59826176 share: 46424064 rss: 59826176 rss_rlim: 4294967295 CPU usage: start_time: 1198207116 rtime: 1034 utime: 971 stime: 63 cutime:0 cstime: 0 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 -1208596768 (LWP 30744)] [New Thread -1277170800 (LWP 30913)] [New Thread -1372554352 (LWP 30912)] [New Thread -1328104560 (LWP 30788)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 182504
Thread 1 (Thread -1208596768 (LWP 30744))
----------- .xsession-errors --------------------- (evolution:30744): 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?) BBDB spinning up... (evolution:30744): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa478018' (evolution:30744): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa478138' sh: acpi: command not found sh: acpi: command not found sh: acpi: command not found sh: acpi: command not found (evolution:30744): e-data-server-ui-WARNING **: Key file does not have key 'pop:__zobisch@pop.gmail.com:995_' sh: acpi: command not found sh: acpi: command not found --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 447591 ***