GNOME Bugzilla – Bug 463918
crash in Tasks: trying to open my email ...
Last modified: 2007-10-11 17:03:00 UTC
What were you doing when the application crashed? trying to open my email with Evolution Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:47:07 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: 549052416 vsize: 549052416 resident: 35643392 share: 26456064 rss: 35643392 rss_rlim: 18446744073709551615 CPU usage: start_time: 1186389027 rtime: 119 utime: 92 stime: 27 cutime:3 cstime: 14 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 46912496471600 (LWP 7733)] [New Thread 1094719824 (LWP 7781)] [New Thread 1115699536 (LWP 7779)] [New Thread 1084229968 (LWP 7754)] (no debugging symbols found) 0x000000310180d89f in waitpid () from /lib64/libpthread.so.0
+ Trace 153140
Thread 1 (Thread 46912496471600 (LWP 7733))
----------- .xsession-errors --------------------- ** (evolution:7733): 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: 0x64 X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 157 Minor opcode: 6 Resource id: 0x64 X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 157 Minor opcode: 6 Resource id: 0x64 --------------------------------------------------
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 ***