GNOME Bugzilla – Bug 511265
crash in Tasks: send/recieve email
Last modified: 2008-01-22 17:45:06 UTC
Version: 2.10 What were you doing when the application crashed? send/recieve email 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.12-52.fc7 #1 SMP Tue Dec 18 21:18:02 EST 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: 118685696 vsize: 118685696 resident: 47828992 share: 36872192 rss: 47828992 rss_rlim: 4294967295 CPU usage: start_time: 1201012763 rtime: 155 utime: 143 stime: 12 cutime:1 cstime: 1 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 -1209116960 (LWP 24002)] [New Thread -1273369712 (LWP 24030)] [New Thread -1219970160 (LWP 24020)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 186328
Thread 1 (Thread -1209116960 (LWP 24002))
----------- .xsession-errors --------------------- (nautilus:4497): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) (nautilus:2880): Gtk-CRITICAL **: gtk_window_realize_icon: assertion `info->icon_pixmap == NULL' failed --- Hash table keys for warning below: --> file:///home/jim (nautilus:5284): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) Model not found, discarding config in emp_apps_open_in inside eab_vcard_control_new CalDAV Eplugin starting up ... ** (evolution:24002): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:24002): DEBUG: mailto URL program: evolution --------------------------------------------------
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 364700 ***