GNOME Bugzilla – Bug 506601
crash in Email:
Last modified: 2008-01-02 14:03:47 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: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 135241728 vsize: 135241728 resident: 43773952 share: 31105024 rss: 43773952 rss_rlim: 4294967295 CPU usage: start_time: 1199120199 rtime: 166 utime: 142 stime: 24 cutime:0 cstime: 3 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 -1209153824 (LWP 3474)] [New Thread -1295758448 (LWP 3530)] [New Thread -1221911664 (LWP 3497)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 183652
Thread 1 (Thread -1209153824 (LWP 3474))
----------- .xsession-errors (6 sec old) --------------------- INFO Shutting down movie data updates INFO Done shutting down. INFO Remaining threads are: INFO <_MainThread(MainThread, started)> ** Message: Error: 找不到資源。 gstfilesrc.c(976): gst_file_src_start (): /play/source: No such file "/tmp/kinsellapodcast_episode5.m4v" CalDAV Eplugin starting up ... ** (evolution:3474): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3474): 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 (bug-buddy:3532): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: 第 1 行第 40 個字發生錯誤:元素‘b’已關閉,但開啟中的元素是‘span’ --------------------------------------------------
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 431459 ***