GNOME Bugzilla – Bug 488002
crash in Tasks: checking email
Last modified: 2007-10-22 22:04:32 UTC
Version: 2.10 What were you doing when the application crashed? checking email 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 23:10:59 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 131018752 vsize: 131018752 resident: 42430464 share: 33689600 rss: 42430464 rss_rlim: 4294967295 CPU usage: start_time: 1192733252 rtime: 242 utime: 211 stime: 31 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 -1208887584 (LWP 8037)] [New Thread -1296954480 (LWP 10800)] [New Thread -1257952368 (LWP 8661)] [New Thread -1236567152 (LWP 8630)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 171210
Thread 1 (Thread -1208887584 (LWP 8037))
----------- .xsession-errors (15 sec old) --------------------- X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x3c00003 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x3600003 CalDAV Eplugin starting up ... ** (evolution:8037): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:8037): 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 ** (evolution:8037): WARNING **: LDAP authentication failed (0xffffffff) --------------------------------------------------
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 ***