GNOME Bugzilla – Bug 466100
crash in Tasks: Just opened Evolution an...
Last modified: 2007-10-02 03:24:40 UTC
Version: 2.10 What were you doing when the application crashed? Just opened Evolution and was waiting for it to fetch my mail. 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.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Clearlooks Memory status: size: 196669440 vsize: 196669440 resident: 62857216 share: 56287232 rss: 62857216 rss_rlim: 4294967295 CPU usage: start_time: 1186966948 rtime: 89 utime: 79 stime: 10 cutime:2 cstime: 5 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 -1208617248 (LWP 446)] [New Thread -1281229936 (LWP 470)] [New Thread -1260250224 (LWP 467)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 154761
Thread 1 (Thread -1208617248 (LWP 446))
----------- .xsession-errors (17 sec old) --------------------- (evolution:32373): libebook-WARNING **: invalid escape, passing it through (evolution:32373): e-utils-WARNING **: calling e_icon_factory_get_icon_filename with unknown icon_size value (48) new dimensions = (48,48) initial setting of an image. no scaling scale = 1 new dimensions = (48,48) we need to scale up scale = 1 CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:446): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:446): 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. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
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 364700 ***