GNOME Bugzilla – Bug 496208
crash in Tasks: Send / Receive
Last modified: 2007-11-14 00:53:00 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.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 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: 117293056 vsize: 117293056 resident: 38920192 share: 32133120 rss: 38920192 rss_rlim: 4294967295 CPU usage: start_time: 1194893726 rtime: 108 utime: 94 stime: 14 cutime:2 cstime: 4 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 -1208838432 (LWP 3165)] [New Thread -1275462768 (LWP 3238)] [New Thread -1225917552 (LWP 3214)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 177241
Thread 1 (Thread -1208838432 (LWP 3165))
----------- .xsession-errors --------------------- ** (evolution:3165): 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: BadMatch (invalid parameter attributes) 8 Major opcode: 158 Minor opcode: 6 Resource id: 0x4d X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 158 Minor opcode: 6 Resource id: 0x4d X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 158 Minor opcode: 6 Resource id: 0x4d --------------------------------------------------
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 ***