GNOME Bugzilla – Bug 485234
crash in Tasks: starting it
Last modified: 2007-10-10 08:32:18 UTC
Version: 2.10 What were you doing when the application crashed? starting it 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.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70000001 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 149598208 vsize: 149598208 resident: 41828352 share: 34721792 rss: 41828352 rss_rlim: 4294967295 CPU usage: start_time: 1191973989 rtime: 55 utime: 50 stime: 5 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 -1208584480 (LWP 20905)] [New Thread -1316803696 (LWP 20916)] [New Thread -1241506928 (LWP 20909)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 169149
Thread 1 (Thread -1208584480 (LWP 20905))
----------- .xsession-errors (7 sec old) --------------------- X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x360003b X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x140f2e6 QGDict::hashKeyString: Invalid null key QGDict::hashKeyString: Invalid null key CalDAV Eplugin starting up ... ** (evolution:20905): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:20905): 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. 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 ***