GNOME Bugzilla – Bug 503227
crash in Tasks: Opening it
Last modified: 2007-12-12 20:50:56 UTC
Version: 2.10 What were you doing when the application crashed? Opening it Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.8-34.fc7 #1 SMP Thu Nov 22 23:05:33 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 130220032 vsize: 130220032 resident: 37396480 share: 29851648 rss: 37396480 rss_rlim: 4294967295 CPU usage: start_time: 1197451077 rtime: 59 utime: 49 stime: 10 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 -1208781088 (LWP 4243)] [New Thread -1287210096 (LWP 4317)] [New Thread -1264989296 (LWP 4310)] [New Thread -1221424240 (LWP 4307)] [New Thread -1244009584 (LWP 4259)] [New Thread -1233126512 (LWP 4258)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 181643
Thread 1 (Thread -1208781088 (LWP 4243))
----------- .xsession-errors (7 sec old) --------------------- localuser:nason being added to access control list SESSION_MANAGER=local/unix:/tmp/.ICE-unix/3835 Failed to connect to socket /tmp/fam-nason- ** (gnome-panel:3962): WARNING **: Failed to connect to the FAM server: Connection failure Unable to open desktop file file:///home/nason/Desktop/redhat-evolution-contacts.desktop for panel launcher: No such file or directory CalDAV Eplugin starting up ... 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. 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 ***