GNOME Bugzilla – Bug 463100
crash in Tasks:
Last modified: 2007-09-29 00:04:03 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.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Bluecurve-Tangerine Icon Theme: Crux Memory status: size: 129351680 vsize: 129351680 resident: 37019648 share: 29548544 rss: 37019648 rss_rlim: 4294967295 CPU usage: start_time: 1186143253 rtime: 97 utime: 85 stime: 12 cutime:2 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 -1208781088 (LWP 24602)] [New Thread -1210881136 (LWP 24667)] [New Thread -1286603888 (LWP 24666)] [New Thread -1263412336 (LWP 24665)] [New Thread -1242432624 (LWP 24629)] [New Thread -1231549552 (LWP 24628)] (no debugging symbols found) 0x00523402 in __kernel_vsyscall ()
+ Trace 152540
Thread 1 (Thread -1208781088 (LWP 24602))
----------- .xsession-errors (22 sec old) --------------------- (evolution:14385): camel-WARNING **: Could not find key entry for word '20070118t140000': Success (evolution:14385): camel-WARNING **: Could not find key entry for word '20070118t140000': Success index:0 index:1 index:0 CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:24602): DEBUG: mailto URL command: evolution %s ** (evolution:24602): 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. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
Likely to be a dupe of bug 431459
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 ***