GNOME Bugzilla – Bug 516329
crash in Email: use email
Last modified: 2008-02-14 18:19:35 UTC
Version: 2.10 What were you doing when the application crashed? use email 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.15-80.fc7 #1 SMP Sun Feb 10 17:29:10 EST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 147206144 vsize: 147206144 resident: 40546304 share: 31256576 rss: 40546304 rss_rlim: 4294967295 CPU usage: start_time: 1202932554 rtime: 231 utime: 196 stime: 35 cutime:179 cstime: 16 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 -1208689936 (LWP 2968)] [New Thread -1301324912 (LWP 3018)] [New Thread -1224471664 (LWP 2990)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 189124
Thread 1 (Thread -1208689936 (LWP 2968))
----------- .xsession-errors (7 sec old) --------------------- Creating backend ... Loading x11 FrontEnd module ... GTK Panel of SCIM 1.4.5 Starting SCIM as daemon ... SCIM has been successfully launched. Smart Common Input Method 1.4.5 CalDAV Eplugin starting up ... ** (evolution:2968): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:2968): 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:3020): 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 ***