GNOME Bugzilla – Bug 515139
crash in Tasks:
Last modified: 2008-02-08 14:02:33 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:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 93028352 vsize: 93028352 resident: 22331392 share: 16093184 rss: 22331392 rss_rlim: 4294967295 CPU usage: start_time: 1202445133 rtime: 48 utime: 43 stime: 5 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 -1208113440 (LWP 2811)] [New Thread -1229325424 (LWP 2831)] [New Thread -1218835568 (LWP 2822)] (no debugging symbols found) 0x00993402 in __kernel_vsyscall ()
+ Trace 188501
Thread 1 (Thread -1208113440 (LWP 2811))
----------- .xsession-errors (6 sec old) --------------------- localuser:vaibhaw being added to access control list SESSION_MANAGER=local/KFC1:/tmp/.ICE-unix/2589 CalDAV Eplugin starting up ... ** (evolution:2811): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:2811): 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:2811): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0 (evolution:2811): e-data-server-ui-WARNING **: Key file does not have group 'Passwords-Mail' --------------------------------------------------
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 ***
It's not bug 364700, but rather bug 467846
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 467846 ***