GNOME Bugzilla – Bug 502815
crash in Tasks:
Last modified: 2007-12-10 12:44:32 UTC
What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 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: 115421184 vsize: 115421184 resident: 33820672 share: 17756160 rss: 33820672 rss_rlim: 4294967295 CPU usage: start_time: 1197282651 rtime: 206 utime: 187 stime: 19 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 -1208871200 (LWP 3086)] [New Thread -1253246064 (LWP 3149)] [New Thread -1221026928 (LWP 3110)] (no debugging symbols found) 0x0031e402 in __kernel_vsyscall ()
+ Trace 181417
Thread 1 (Thread -1208871200 (LWP 3086))
----------- .xsession-errors --------------------- localuser:sif20957 being added to access control list SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/2876 CalDAV Eplugin starting up ... ** (evolution:3086): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3086): 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:3086): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0 (evolution:3086): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0 --------------------------------------------------
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 ***