GNOME Bugzilla – Bug 504466
crash in Tasks:
Last modified: 2007-12-19 16:02:23 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.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: No Accessibility: Disabled GTK+ Theme: Cillop-Mediterranean Icon Theme: gnome Memory status: size: 106713088 vsize: 106713088 resident: 35733504 share: 28934144 rss: 35733504 rss_rlim: 4294967295 CPU usage: start_time: 1198073686 rtime: 109 utime: 100 stime: 9 cutime:0 cstime: 2 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 -1208936736 (LWP 3130)] [New Thread -1265177712 (LWP 3178)] [New Thread -1220686960 (LWP 3152)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 182346
Thread 1 (Thread -1208936736 (LWP 3130))
----------- .xsession-errors (10 sec old) --------------------- localuser:kbug being added to access control list SESSION_MANAGER=local/unix:/tmp/.ICE-unix/2932 CalDAV Eplugin starting up ... (evolution:3130): evolution-mail-WARNING **: ignored this junk plugin: not enabled or we have already loaded one (evolution:3130): e-utils-WARNING **: Plugin 'Spamassassin junk plugin' failed to load hook 'org.gnome.evolution.mail.junk:1.0' ** (evolution:3130): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3130): 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 ***