GNOME Bugzilla – Bug 500974
crash in Tasks: checking email
Last modified: 2007-12-02 15:12:07 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-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.1-21.fc7 #1 SMP Thu Nov 1 20:28:15 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 573399040 vsize: 573399040 resident: 44552192 share: 33554432 rss: 44552192 rss_rlim: 18446744073709551615 CPU usage: start_time: 1196572726 rtime: 79 utime: 69 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 "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496502128 (LWP 3477)] [New Thread 1115699536 (LWP 3496)] [New Thread 1084229968 (LWP 3481)] (no debugging symbols found) 0x0000003bb180d97f in waitpid () from /lib64/libpthread.so.0
+ Trace 180384
Thread 1 (Thread 46912496502128 (LWP 3477))
----------- .xsession-errors --------------------- CalDAV Eplugin starting up ... ** (evolution:3477): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3477): 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 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x20004bb X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x2000790 warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fffc8ffd000 --------------------------------------------------
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 ***