GNOME Bugzilla – Bug 466351
crash in Tasks: opening evolution email
Last modified: 2007-09-24 19:03:51 UTC
Version: 2.10 What were you doing when the application crashed? opening evolution email 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: Enforcing Accessibility: Disabled GTK+ Theme: Mist Icon Theme: Mist Memory status: size: 120471552 vsize: 120471552 resident: 36696064 share: 30081024 rss: 36696064 rss_rlim: 4294967295 CPU usage: start_time: 1187035005 rtime: 44 utime: 38 stime: 6 cutime:3 cstime: 11 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 -1208846624 (LWP 2936)] [New Thread -1267901552 (LWP 2981)] [New Thread -1257411696 (LWP 2980)] [New Thread -1222440048 (LWP 2958)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 154950
Thread 1 (Thread -1208846624 (LWP 2936))
----------- .xsession-errors --------------------- ** (evolution:2936): 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: 157 Minor opcode: 6 Resource id: 0x3f X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 157 Minor opcode: 6 Resource id: 0x3f X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 157 Minor opcode: 6 Resource id: 0x3f --------------------------------------------------
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 ***