GNOME Bugzilla – Bug 497406
crash in Tasks:
Last modified: 2007-11-16 17:37:11 UTC
Version: 2.10 What were you doing when the application crashed? 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.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 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: 109600768 vsize: 109600768 resident: 37646336 share: 29863936 rss: 37646336 rss_rlim: 4294967295 CPU usage: start_time: 1195227487 rtime: 67 utime: 60 stime: 7 cutime:0 cstime: 1 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 -1208441120 (LWP 3317)] [New Thread -1231979632 (LWP 3367)] [New Thread -1221080176 (LWP 3342)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 178149
Thread 1 (Thread -1208441120 (LWP 3317))
----------- .xsession-errors (16 sec old) --------------------- localuser:tseaman being added to access control list SESSION_MANAGER=local/unix:/tmp/.ICE-unix/3113 winscard_clnt.c:3349:SCardCheckDaemonAvailability() PCSC Not Running Unable to open desktop file /home/tseaman/Desktop/gnome-gedit.desktop for panel launcher: No such file or directory CalDAV Eplugin starting up ... ** (evolution:3317): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3317): 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. 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 ***