GNOME Bugzilla – Bug 500616
crash in Tasks:
Last modified: 2007-11-30 12:03:35 UTC
Version: 2.10 What were you doing when the application crashed? 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.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 121425920 vsize: 121425920 resident: 48848896 share: 36773888 rss: 48848896 rss_rlim: 4294967295 CPU usage: start_time: 1196414222 rtime: 530 utime: 459 stime: 71 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 -1208830240 (LWP 5669)] [New Thread -1241494640 (LWP 5739)] [New Thread -1230611568 (LWP 5691)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 180203
Thread 1 (Thread -1208830240 (LWP 5669))
----------- .xsession-errors (25 sec old) --------------------- localuser:cdl being added to access control list No profile for user 'cdl' found SESSION_MANAGER=local/unix:/tmp/.ICE-unix/5544 Initializing nautilus-open-terminal extension CalDAV Eplugin starting up ... ** (evolution:5669): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:5669): DEBUG: mailto URL program: evolution libnm_glib_nm_state_cb: dbus returned an error. (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files (evolution:5669): e-data-server-WARNING **: Could not open converter for 'UNKNOWN' to 'UTF-8' charset --------------------------------------------------
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 431459 ***