GNOME Bugzilla – Bug 489848
crash in Tasks:
Last modified: 2007-12-04 17:21:37 UTC
Version: 2.10 What were you doing when the application crashed? 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.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Raleigh Icon Theme: gnome Memory status: size: 133877760 vsize: 133877760 resident: 28762112 share: 17752064 rss: 28762112 rss_rlim: 4294967295 CPU usage: start_time: 1193239663 rtime: 4587 utime: 4122 stime: 465 cutime:125 cstime: 36 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1208260896 (LWP 12783)] [New Thread -1232368752 (LWP 13156)] [New Thread -1297757296 (LWP 12807)] [New Thread -1221874800 (LWP 12790)] 0x0012d402 in __kernel_vsyscall ()
+ Trace 172568
Thread 1 (Thread -1208260896 (LWP 12783))
----------- .xsession-errors --------------------- (evolution:12783): camel-CRITICAL **: camel_data_wrapper_set_mime_type_field: assertion `mime_type != NULL' failed (evolution:12783): camel-CRITICAL **: camel_data_wrapper_set_mime_type_field: assertion `mime_type != NULL' failed (evolution:12783): 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:12783): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9761240' (evolution:12783): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9761360' Window manager warning: Invalid WM_TRANSIENT_FOR window 0x2a0607a specified for 0x2a060fb (Delete acc). warning: the debug information found in "/usr/lib/debug//usr/lib/libX11.so.6.2.0.debug" does not match "/usr/lib/libX11.so.6" (CRC mismatch). Cannot access memory at address 0xfffff7fc --------------------------------------------------
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 449996 ***