GNOME Bugzilla – Bug 487926
crash in Tasks:
Last modified: 2007-10-22 22:24:55 UTC
Version: 2.10 What were you doing when the application crashed? 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: 143466496 vsize: 143466496 resident: 42868736 share: 34729984 rss: 42868736 rss_rlim: 4294967295 CPU usage: start_time: 1192719314 rtime: 247 utime: 232 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 -1208793376 (LWP 3621)] [New Thread -1268884592 (LWP 3657)] [New Thread -1257006192 (LWP 3654)] (no debugging symbols found) 0x0012d402 in __kernel_vsyscall ()
+ Trace 171155
Thread 1 (Thread -1208793376 (LWP 3621))
----------- .xsession-errors (23 sec old) --------------------- ** (evolution:3621): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3621): DEBUG: mailto URL program: evolution (evolution:3621): e-data-server-DEBUG: Saving categories to "/home/graham/.evolution/categories.xml" X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0xc00055 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0xc00055 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:3621): e-data-server-ui-WARNING **: Key file does not have group 'Passwords-Mail' --------------------------------------------------
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 ***