GNOME Bugzilla – Bug 481430
crash in Tasks:
Last modified: 2007-09-29 00:26:37 UTC
Version: 2.10 What were you doing when the application crashed? 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.7-85.fc7PAE #1 SMP Fri Sep 21 19:44:36 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 133447680 vsize: 133447680 resident: 43585536 share: 33280000 rss: 43585536 rss_rlim: 4294967295 CPU usage: start_time: 1191012695 rtime: 128 utime: 109 stime: 19 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1209141536 (LWP 3407)] [New Thread -1227519088 (LWP 3747)] [New Thread -1250952304 (LWP 3633)] [New Thread -1238013040 (LWP 3552)] 0x00110410 in __kernel_vsyscall ()
+ Trace 166273
Thread 1 (Thread -1209141536 (LWP 3407))
----------- .xsession-errors (30 sec old) --------------------- --------------------------------- It looks like dcopserver is already running. If you are sure that it is not already running, remove /home/jld/.DCOPserver_oaktree__0 and start dcopserver again. --------------------------------- kbuildsycoca running... DCOP Cleaning up dead connections. ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name CalDAV Eplugin starting up ... Launched ok, pid = 3437 ** (evolution:3407): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3407): 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 ***