GNOME Bugzilla – Bug 476475
crash in Tasks: I was trying to send an ...
Last modified: 2007-09-20 16:54:19 UTC
What were you doing when the application crashed? I was trying to send an email. it keeps asking me for the password. 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: 125210624 vsize: 125210624 resident: 22306816 share: 16146432 rss: 22306816 rss_rlim: 4294967295 CPU usage: start_time: 1189670848 rtime: 70 utime: 60 stime: 10 cutime:0 cstime: 0 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 -1208359200 (LWP 2994)] [New Thread -1262019696 (LWP 3023)] [New Thread -1224463472 (LWP 3003)] (no debugging symbols found) 0x00d05402 in __kernel_vsyscall ()
+ Trace 162560
Thread 1 (Thread -1208359200 (LWP 2994))
----------- .xsession-errors --------------------- localuser:tharaka being added to access control list SESSION_MANAGER=local/bigguy:/tmp/.ICE-unix/2780 Loading "installonlyn" plugin Introspect error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the ne CalDAV Eplugin starting up ... ** (evolution:2994): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:2994): 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 the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 431459 ***