GNOME Bugzilla – Bug 475847
crash in Tasks: i was downloading a mess...
Last modified: 2007-09-24 17:48:19 UTC
Version: 2.10 What were you doing when the application crashed? i was downloading a message with gmail as a provider Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 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: 127209472 vsize: 127209472 resident: 38457344 share: 30986240 rss: 38457344 rss_rlim: 4294967295 CPU usage: start_time: 1189518313 rtime: 93 utime: 83 stime: 10 cutime:3 cstime: 5 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 4996)] [New Thread -1284117616 (LWP 5052)] [New Thread -1273627760 (LWP 5051)] [New Thread -1225466992 (LWP 5030)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 162069
Thread 1 (Thread -1208863008 (LWP 4996))
----------- .xsession-errors (9 sec old) --------------------- ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:4996): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:4996): 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 ***