GNOME Bugzilla – Bug 488749
crash in Tasks: Verificando email no Evo...
Last modified: 2007-10-22 22:02:00 UTC
Version: 2.10 What were you doing when the application crashed? Verificando email no 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 20:47:39 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 565473280 vsize: 565473280 resident: 43102208 share: 33210368 rss: 43102208 rss_rlim: 18446744073709551615 CPU usage: start_time: 1192916870 rtime: 169 utime: 151 stime: 18 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 "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912511203808 (LWP 3492)] [New Thread 1105209680 (LWP 3553)] [New Thread 1084229968 (LWP 3514)] (no debugging symbols found) 0x0000003ac600d97f in waitpid () from /lib64/libpthread.so.0
+ Trace 171793
Thread 1 (Thread 46912511203808 (LWP 3492))
----------- .xsession-errors (129 sec old) --------------------- localuser:root being added to access control list SESSION_MANAGER=local/unix:/tmp/.ICE-unix/3111 ** (gnome-session:3111): WARNING **: Host name lookup failure on localhost. /var/tmp/rpm-tmp.82052: line 24: /etc/pango/i686-redhat-linux-gnu/pango.modules: Arquivo ou diretório não encontrado CalDAV Eplugin starting up ... ** (evolution:3492): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3492): 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 ***