GNOME Bugzilla – Bug 518149
crash in Tasks:
Last modified: 2008-02-23 13:14: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: Clearlooks Icon Theme: Fedora Memory status: size: 138240000 vsize: 138240000 resident: 39587840 share: 32342016 rss: 39587840 rss_rlim: 4294967295 CPU usage: start_time: 1203720387 rtime: 47 utime: 43 stime: 4 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 -1208863008 (LWP 6855)] [New Thread -1269838960 (LWP 6877)] [New Thread -1225946224 (LWP 6872)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 190145
Thread 1 (Thread -1208863008 (LWP 6855))
----------- .xsession-errors --------------------- Fri Feb 22 23:11:24 2008 CConn: connected to host 82.224.87.113 port 59000 CConnection: Server supports RFB protocol version 3.8 CConnection: Using RFB protocol version 3.8 Fri Feb 22 23:11:28 2008 TXImage: Using default colormap and visual, TrueColor, depth 24. CConn: Using pixel format depth 24 (32bpp) little-endian rgb888 CConn: Using ZRLE encoding CalDAV Eplugin starting up ... ** (evolution:6855): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:6855): 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 ***