GNOME Bugzilla – Bug 453351
crash in Email: run evolution
Last modified: 2007-07-03 13:06:22 UTC
What were you doing when the application crashed? run evolution Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (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: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 105734144 vsize: 105734144 resident: 23363584 share: 14950400 rss: 23363584 rss_rlim: 4294967295 CPU usage: start_time: 1183461796 rtime: 102 utime: 86 stime: 16 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 -1208928544 (LWP 2904)] (no debugging symbols found) 0x00f05402 in __kernel_vsyscall ()
+ Trace 145438
Thread 1 (Thread -1208928544 (LWP 2904))
----------- .xsession-errors --------------------- localuser:van being added to access control list SESSION_MANAGER=local/nikitin-1.central.bcnn.ru:/tmp/.ICE-unix/2682 compiz: No stencil buffer. Clipping of transformed windows is not going to be correct when screen is transformed. 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 ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name error getting update info: Cannot open/read repomd.xml file for repository: local_DVD (nautilus:2793): Eel-WARNING **: No extension, not implemented yet CalDAV Eplugin starting up ... ** (evolution:2904): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:2904): DEBUG: mailto URL program: evolution --------------------------------------------------
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 425129 ***