GNOME Bugzilla – Bug 478793
crash in Tasks: send/receive button
Last modified: 2007-10-11 17:07:43 UTC
Version: 2.10 What were you doing when the application crashed? send/receive button 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 21:50:50 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 652009472 vsize: 652009472 resident: 48611328 share: 38473728 rss: 48611328 rss_rlim: 18446744073709551615 CPU usage: start_time: 1190332253 rtime: 224 utime: 187 stime: 37 cutime:5 cstime: 17 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496423056 (LWP 2839)] [New Thread 1126189392 (LWP 2906)] [New Thread 1115699536 (LWP 2905)] [New Thread 1105209680 (LWP 2904)] [New Thread 1084229968 (LWP 2877)] (no debugging symbols found) 0x000000388080d97f in waitpid () from /lib64/libpthread.so.0
+ Trace 164276
Thread 1 (Thread 46912496423056 (LWP 2839))
----------- .xsession-errors (11 sec old) --------------------- localuser:phil being added to access control list SESSION_MANAGER=local/cpv6:/tmp/.ICE-unix/2603 CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:2839): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:2839): 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 ***