GNOME Bugzilla – Bug 495592
crash in Tasks: Opening Evolution.
Last modified: 2007-11-11 12:12:33 UTC
Version: 2.10 What were you doing when the application crashed? Opening Evolution. 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.23.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Clearlooks Memory status: size: 134193152 vsize: 134193152 resident: 39956480 share: 32813056 rss: 39956480 rss_rlim: 4294967295 CPU usage: start_time: 1194702356 rtime: 71 utime: 62 stime: 9 cutime:0 cstime: 1 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 -1208932640 (LWP 3225)] [New Thread -1252004976 (LWP 3245)] [New Thread -1229341808 (LWP 3242)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 176797
Thread 1 (Thread -1208932640 (LWP 3225))
----------- .xsession-errors --------------------- Minor opcode: 0 Resource id: 0x180074c CalDAV Eplugin starting up ... ** (evolution:3225): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3225): 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 --------------------------------------------------
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 ***