GNOME Bugzilla – Bug 490334
crash in Tasks:
Last modified: 2007-10-26 11:55:29 UTC
Version: 2.10 What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 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: 122433536 vsize: 122433536 resident: 45686784 share: 37023744 rss: 45686784 rss_rlim: 4294967295 CPU usage: start_time: 1193357308 rtime: 76 utime: 69 stime: 7 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 -1208580384 (LWP 3260)] [New Thread -1232032880 (LWP 3312)] [New Thread -1221133424 (LWP 3285)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 172899
Thread 1 (Thread -1208580384 (LWP 3260))
----------- .xsession-errors (88 sec old) --------------------- localuser:tseaman being added to access control list SESSION_MANAGER=local/unix:/tmp/.ICE-unix/3049 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:3260): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3260): 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 ***