GNOME Bugzilla – Bug 515833
crash in Tasks: intentar salir
Last modified: 2008-02-12 00:32:49 UTC
What were you doing when the application crashed? intentar salir 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: Clearlooks Icon Theme: Fedora Memory status: size: 98598912 vsize: 98598912 resident: 28868608 share: 20054016 rss: 28868608 rss_rlim: 4294967295 CPU usage: start_time: 1202757735 rtime: 598 utime: 548 stime: 50 cutime:0 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 -1208183072 (LWP 2846)] [New Thread -1262826608 (LWP 2892)] [New Thread -1273316464 (LWP 2880)] (no debugging symbols found) 0x009e1402 in __kernel_vsyscall ()
+ Trace 188857
Thread 1 (Thread -1208183072 (LWP 2846))
----------- .xsession-errors --------------------- Bonobo accessibility support initialized CalDAV Eplugin starting up ... ** (evolution:2809): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:2809): DEBUG: mailto URL program: evolution GTK Accessibility Module initialized Bonobo accessibility support initialized CalDAV Eplugin starting up ... ** (evolution:2846): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:2846): 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 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 ***