GNOME Bugzilla – Bug 498354
crash in Tasks: send/receive
Last modified: 2007-11-20 12:55:29 UTC
Version: 2.10 What were you doing when the application crashed? send/receive 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: 150167552 vsize: 150167552 resident: 42135552 share: 34664448 rss: 42135552 rss_rlim: 4294967295 CPU usage: start_time: 1195516169 rtime: 60 utime: 56 stime: 4 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 -1209006368 (LWP 6776)] [New Thread -1306760304 (LWP 6786)] [New Thread -1241937008 (LWP 6780)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 178830
Thread 1 (Thread -1209006368 (LWP 6776))
----------- .xsession-errors (6 sec old) --------------------- Minor opcode: 0 Resource id: 0x3200074 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x32004fb X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x200c9cf CalDAV Eplugin starting up ... ** (evolution:6776): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:6776): 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 ***