GNOME Bugzilla – Bug 497726
crash in Tasks: restart
Last modified: 2007-11-18 13:18:08 UTC
What were you doing when the application crashed? restart 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:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Enabled GTK+ Theme: Crux Icon Theme: Crux Memory status: size: 111636480 vsize: 111636480 resident: 33153024 share: 26525696 rss: 33153024 rss_rlim: 4294967295 CPU usage: start_time: 1195326303 rtime: 91 utime: 77 stime: 14 cutime:1 cstime: 0 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 -1208989984 (LWP 2886)] [New Thread -1247904880 (LWP 2934)] [New Thread -1217672304 (LWP 2908)] (no debugging symbols found) 0x004a9402 in __kernel_vsyscall ()
+ Trace 178385
Thread 1 (Thread -1208989984 (LWP 2886))
----------- .xsession-errors --------------------- dbus.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name edu.duke.linux.yum was not provided by any .service files You can not run beagle as root. Beagle is designed to run from your own user account. If you want to create multiuser or system-wide indexes, use the beagle-build-index tool. You can override this setting using the beagle-config or beagle-settings tools. GTK Accessibility Module initialized Bonobo accessibility support initialized CalDAV Eplugin starting up ... ** (evolution:2886): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:2886): DEBUG: mailto URL program: evolution GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized --------------------------------------------------
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 ***