GNOME Bugzilla – Bug 480820
crash in Tasks:
Last modified: 2007-09-27 13:27:11 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.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 157204480 vsize: 157204480 resident: 57516032 share: 32358400 rss: 57516032 rss_rlim: 4294967295 CPU usage: start_time: 1190864821 rtime: 226 utime: 210 stime: 16 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 -1208879392 (LWP 3003)] [New Thread -1328829552 (LWP 3042)] [New Thread -1259345008 (LWP 3032)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 165812
Thread 1 (Thread -1208879392 (LWP 3003))
----------- .xsession-errors (10 sec old) --------------------- Input File : '/usr/share/sounds/ekiga/voicemail.wav' Sample Size : 16-bit (2 bytes) Sample Encoding: signed (2's complement) Channels : 1 Sample Rate : 22050 Time: 00:00.37 [00:01.37] of 00:01.74 ( 21.3%) Output Buffer: 17.76K Time: 00:00.74 [00:01.00] of 00:01.74 ( 42.6%) Output Buffer: 35.60K Time: 00:01.11 [00:00.63] of 00:01.74 ( 63.9%) Output Buffe Done. CalDAV Eplugin starting up ... ** (evolution:3003): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3003): 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 ***