GNOME Bugzilla – Bug 478977
crash in Tasks: Opening Evolution to che...
Last modified: 2007-09-24 17:34:33 UTC
Version: 2.10 What were you doing when the application crashed? Opening Evolution to check e-mail, had opened pidgin messaging client moments before. 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: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 116363264 vsize: 116363264 resident: 37650432 share: 31256576 rss: 37650432 rss_rlim: 4294967295 CPU usage: start_time: 1190384471 rtime: 34 utime: 28 stime: 6 cutime:1 cstime: 4 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 -1208985888 (LWP 7646)] [New Thread -1238369392 (LWP 7682)] [New Thread -1226679408 (LWP 7679)] (no debugging symbols found) 0x0012d402 in __kernel_vsyscall ()
+ Trace 164414
Thread 1 (Thread -1208985888 (LWP 7646))
----------- .xsession-errors --------------------- localuser:sbaxter being added to access control list SESSION_MANAGER=local/anaconda5.uml.edu:/tmp/.ICE-unix/7433 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 CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:7646): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:7646): 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 ***