GNOME Bugzilla – Bug 504774
crash in Tasks:
Last modified: 2007-12-22 14:32:52 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.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: Glossy Icon Theme: gnome Memory status: size: 125767680 vsize: 125767680 resident: 42885120 share: 33722368 rss: 42885120 rss_rlim: 4294967295 CPU usage: start_time: 1198195666 rtime: 156 utime: 146 stime: 10 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 -1208551712 (LWP 4761)] [New Thread -1290564720 (LWP 4796)] [New Thread -1240466544 (LWP 4767)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 182489
Thread 1 (Thread -1208551712 (LWP 4761))
----------- .xsession-errors (356 sec old) --------------------- (evolution:4589): camel-WARNING **: Could not find key entry for word 'hd0000000311450': Success (evolution:4589): e-data-server-WARNING **: Could not open converter for 'UNKNOWN' to 'UTF-8' charset BBDB spinning up... (evolution:4589): e-data-server-DEBUG: Loading categories from "/home/ear1/.evolution/categories.xml" (evolution:4589): e-data-server-DEBUG: Loaded 29 categories index:2 CalDAV Eplugin starting up ... ** (evolution:4761): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:4761): 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 --------------------------------------------------
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 ***