GNOME Bugzilla – Bug 498050
crash in Email:
Last modified: 2007-11-19 18:38:38 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.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 151310336 vsize: 151310336 resident: 41680896 share: 33603584 rss: 41680896 rss_rlim: 4294967295 CPU usage: start_time: 1195461641 rtime: 127 utime: 115 stime: 12 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 -1208637728 (LWP 3294)] [New Thread -1238242416 (LWP 3336)] [New Thread -1227248752 (LWP 3316)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 178610
Thread 1 (Thread -1208637728 (LWP 3294))
----------- .xsession-errors --------------------- 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:3294): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3294): 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:3343): 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 ***