GNOME Bugzilla – Bug 485904
crash in Tasks: opened evolution email f...
Last modified: 2007-10-12 10:20:41 UTC
Version: 2.10 What were you doing when the application crashed? opened evolution email from icon 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.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 158392320 vsize: 158392320 resident: 41013248 share: 34713600 rss: 41013248 rss_rlim: 4294967295 CPU usage: start_time: 1192150269 rtime: 36 utime: 30 stime: 6 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 -1208944928 (LWP 31867)] [New Thread -1251959920 (LWP 31876)] [New Thread -1241470064 (LWP 31872)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 169640
Thread 1 (Thread -1208944928 (LWP 31867))
----------- .xsession-errors --------------------- Minor opcode: 0 Resource id: 0x14040b6 CalDAV Eplugin starting up ... ** (evolution:31867): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:31867): 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 --------------------------------------------------
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 ***