GNOME Bugzilla – Bug 507271
crash in Tasks:
Last modified: 2008-01-04 15:19:02 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.12-52.fc7 #1 SMP Tue Dec 18 21:18:02 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: 113709056 vsize: 113709056 resident: 34574336 share: 28250112 rss: 34574336 rss_rlim: 4294967295 CPU usage: start_time: 1199458711 rtime: 99 utime: 86 stime: 13 cutime:1 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 -1208305952 (LWP 9018)] [New Thread -1252009072 (LWP 9040)] [New Thread -1219060848 (LWP 9035)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 184057
Thread 1 (Thread -1208305952 (LWP 9018))
----------- .xsession-errors --------------------- Input File : '/home/Steve/havmail2.wav' Sample Size : 8-bit (1 byte) Sample Encoding: unsigned Channels : 1 Sample Rate : 11025 Comment : 'File created by GoldWave. GoldWave copyright (C) Chris Craig' Time: 00:00.74 [00:01.36] of 00:02.10 ( 35.3%) Output Buffer: 35.52K Time: 00:01.49 [00:00.62] of 00:02.10 ( 70.6%) Output Buffer: 71.19K Time: 00:02.10 [00:00.00] of 00:02.10 ( 100.0%) Output Buff Done. CalDAV Eplugin starting up ... ** (evolution:9018): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:9018): 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 ***