GNOME Bugzilla – Bug 466199
crash in Tasks: Trying to get my mail. ...
Last modified: 2007-10-02 03:24:30 UTC
Version: 2.10 What were you doing when the application crashed? Trying to get my mail. The message was that there were 195 messages (!) to be retrieved. The message was probably correct: I have been away 3 weeks. 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: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 119586816 vsize: 119586816 resident: 41463808 share: 32317440 rss: 41463808 rss_rlim: 4294967295 CPU usage: start_time: 1186999953 rtime: 142 utime: 118 stime: 24 cutime:4 cstime: 10 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 -1208616208 (LWP 2939)] [New Thread -1283994736 (LWP 3004)] [New Thread -1225090160 (LWP 2977)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 154837
Thread 1 (Thread -1208616208 (LWP 2939))
----------- .xsession-errors (19 sec old) --------------------- localuser:parpia being added to access control list SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/2735 CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:2939): DEBUG: mailto URL command: evolution %s ** (evolution:2939): 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 ***