GNOME Bugzilla – Bug 496733
crash in Tasks:
Last modified: 2007-11-16 00:28:17 UTC
What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:47:07 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Crux Icon Theme: Crux Memory status: size: 570085376 vsize: 570085376 resident: 43868160 share: 17293312 rss: 43868160 rss_rlim: 18446744073709551615 CPU usage: start_time: 1195045216 rtime: 290 utime: 260 stime: 30 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 "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496504416 (LWP 19868)] [New Thread 1094719824 (LWP 20001)] [New Thread 1115699536 (LWP 19909)] (no debugging symbols found) 0x000000316100d89f in waitpid () from /lib64/libpthread.so.0
+ Trace 177652
Thread 1 (Thread 46912496504416 (LWP 19868))
----------- .xsession-errors (35 sec old) --------------------- SESSION_MANAGER=local/devnull2:/tmp/.ICE-unix/19598 INFO: imwheel started (pid=19738) CalDAV Eplugin starting up ... kbuildsycoca running... ** (evolution:19868): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:19868): 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 (evolution:19868): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0 (evolution:19868): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0 (evolution:19868): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0 DCOP Cleaning up dead connections. ScimInputContextPlugin() ~ScimInputContextPlugin() ScimInputContextPlugin() --------------------------------------------------
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 431459 ***