GNOME Bugzilla – Bug 447273
crash in Tasks: I can't open evolution a...
Last modified: 2007-06-14 11:39:24 UTC
What were you doing when the application crashed? I can't open evolution at all. I have just rebooted and I am going to boot into Windows soon just to see my stupid email Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: gnome Memory status: size: 105066496 vsize: 105066496 resident: 34095104 share: 27930624 rss: 34095104 rss_rlim: 4294967295 CPU usage: start_time: 1181760557 rtime: 97 utime: 83 stime: 14 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 -1208604960 (LWP 4180)] [New Thread -1230951536 (LWP 4199)] (no debugging symbols found) 0x003ac402 in __kernel_vsyscall ()
+ Trace 140740
Thread 1 (Thread -1208604960 (LWP 4180))
----------- .xsession-errors --------------------- localuser:briant being added to access control list id: cannot find name for group ID 501 SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/3971 compiz: No stencil buffer. Clipping of transformed windows is not going to be correct when screen is transformed. CalDAV Eplugin starting up ... ** (evolution:4180): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:4180): 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 (evolution:4180): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0 --------------------------------------------------
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 431342 ***