GNOME Bugzilla – Bug 508208
crash in Tasks: send/receive
Last modified: 2008-01-10 22:40:11 UTC
Version: 2.10 What were you doing when the application crashed? send/receive 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: Permissive Accessibility: Disabled GTK+ Theme: Crux Icon Theme: Crux Memory status: size: 121225216 vsize: 121225216 resident: 43712512 share: 29290496 rss: 43712512 rss_rlim: 4294967295 CPU usage: start_time: 1199851804 rtime: 158 utime: 145 stime: 13 cutime:0 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 -1208789280 (LWP 3651)] [New Thread -1272067184 (LWP 3675)] [New Thread -1224381552 (LWP 3669)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 184620
Thread 1 (Thread -1208789280 (LWP 3651))
----------- .xsession-errors (9 sec old) --------------------- report junk?? **Message you sent blocked by our bulk email filter** report junk?? **Message you sent blocked by our bulk email filter** report junk?? **Message you sent blocked by our bulk email filter** report junk?? Returned mail: Service unavailable report junk?? failure notice CalDAV Eplugin starting up ... ** (evolution:3651): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3651): 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 ***