GNOME Bugzilla – Bug 501466
crash in Email:
Last modified: 2007-12-04 12:33:07 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: Bluecurve-Lime Icon Theme: Clearlooks Memory status: size: 153882624 vsize: 153882624 resident: 49192960 share: 42397696 rss: 49192960 rss_rlim: 4294967295 CPU usage: start_time: 1196759478 rtime: 73 utime: 60 stime: 13 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 -1208924448 (LWP 2955)] [New Thread -1312187504 (LWP 3008)] [New Thread -1234449520 (LWP 3003)] [New Thread -1244947568 (LWP 2978)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 180686
Thread 1 (Thread -1208924448 (LWP 2955))
----------- .xsession-errors --------------------- localuser:epoeta being added to access control list SESSION_MANAGER=local/unix:/tmp/.ICE-unix/2712 Autoselected keyboard map it WARNING: Remote desktop does not support colour depth 24; falling back to 16 CalDAV Eplugin starting up ... ** (evolution:2955): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:2955): 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 ***