GNOME Bugzilla – Bug 482587
crash in Tasks: logging in to Evolution
Last modified: 2007-10-05 09:45:41 UTC
Version: 2.10 What were you doing when the application crashed? logging in to Evolution Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 126029824 vsize: 126029824 resident: 34893824 share: 28504064 rss: 34893824 rss_rlim: 4294967295 CPU usage: start_time: 1191333884 rtime: 74 utime: 63 stime: 11 cutime:0 cstime: 0 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 -1208338720 (LWP 4846)] [New Thread -1229522032 (LWP 4875)] [New Thread -1240011888 (LWP 4852)] [New Thread -1219032176 (LWP 4849)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 167129
Thread 1 (Thread -1208338720 (LWP 4846))
----------- .xsession-errors --------------------- localuser:hector being added to access control list SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/3237 Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x360005b (OpenOffice) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. CalDAV Eplugin starting up ... ** (evolution:4846): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:4846): 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 ***