GNOME Bugzilla – Bug 518080
crash in Tasks:
Last modified: 2008-02-23 13:12:46 UTC
Version: 2.10 What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.8-34.fc7 #1 SMP Thu Nov 22 23:05:33 EST 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: 129953792 vsize: 129953792 resident: 41705472 share: 32845824 rss: 41705472 rss_rlim: 4294967295 CPU usage: start_time: 1203691794 rtime: 139 utime: 124 stime: 15 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 -1208469792 (LWP 3254)] [New Thread -1247810672 (LWP 3317)] [New Thread -1224868976 (LWP 3298)] [New Thread -1237320816 (LWP 3267)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 190103
Thread 1 (Thread -1208469792 (LWP 3254))
----------- .xsession-errors (14 sec old) --------------------- Major opcode: 19 Minor opcode: 0 Resource id: 0x2c0000c X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x280006a CalDAV Eplugin starting up ... ** (evolution:3254): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3254): 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:3254): camel-groupwise-provider-WARNING **: Could not connect..failure connecting --------------------------------------------------
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 ***