GNOME Bugzilla – Bug 504667
crash in Tasks:
Last modified: 2007-12-20 16:03:55 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: No Accessibility: Disabled GTK+ Theme: Bluecurve-Tangerine Icon Theme: Crux Memory status: size: 133435392 vsize: 133435392 resident: 50716672 share: 30285824 rss: 50716672 rss_rlim: 4294967295 CPU usage: start_time: 1198158733 rtime: 597 utime: 490 stime: 107 cutime:0 cstime: 0 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 -1208731936 (LWP 23519)] [New Thread -1243616368 (LWP 23569)] [New Thread -1254106224 (LWP 23527)] [New Thread -1233126512 (LWP 23525)] 0x00110402 in __kernel_vsyscall ()
+ Trace 182436
Thread 1 (Thread -1208731936 (LWP 23519))
----------- .xsession-errors (183 sec old) --------------------- Increasing itip formatter search count to 2 Increasing itip formatter search count to 3 Increasing itip formatter search count to 4 Decreasing itip formatter search count to 3 Decreasing itip formatter search count to 2 Decreasing itip formatter search count to 1 Decreasing itip formatter search count to 0 calendar selection changed calendar selection changed calendar selection changed CalDAV Eplugin starting up ... ** (evolution:23519): DEBUG: mailto URL command: evolution %s ** (evolution:23519): 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 431459 ***