GNOME Bugzilla – Bug 506997
crash in Tasks: Clicked on mail in list ...
Last modified: 2008-01-03 12:09:04 UTC
Version: 2.10 What were you doing when the application crashed? Clicked on mail in list of mails in folder. 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: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 182460416 vsize: 182460416 resident: 74481664 share: 45621248 rss: 74481664 rss_rlim: 4294967295 CPU usage: start_time: 1199355641 rtime: 1508 utime: 1351 stime: 157 cutime:2 cstime: 3 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1208641824 (LWP 13510)] [New Thread -1278620784 (LWP 13814)] [New Thread -1257247856 (LWP 13538)] 0x00110402 in __kernel_vsyscall ()
+ Trace 183894
Thread 1 (Thread -1208641824 (LWP 13510))
----------- .xsession-errors (747 sec old) --------------------- Loading socket Config module ... 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 SESSION_MANAGER=local/unix:/tmp/.ICE-unix/13220 CalDAV Eplugin starting up ... ** (evolution:13510): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:13510): 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 431459 ***