GNOME Bugzilla – Bug 475760
crash in Tasks: Just started evolution a...
Last modified: 2007-09-24 17:48:40 UTC
Version: 2.10 What were you doing when the application crashed? Just started evolution and it was fetching mail 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.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 127717376 vsize: 127717376 resident: 39280640 share: 31797248 rss: 39280640 rss_rlim: 4294967295 CPU usage: start_time: 1189499880 rtime: 86 utime: 78 stime: 8 cutime:2 cstime: 5 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 -1208461600 (LWP 13438)] [New Thread -1268790384 (LWP 13463)] [New Thread -1247810672 (LWP 13460)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 162009
Thread 1 (Thread -1208461600 (LWP 13438))
----------- .xsession-errors --------------------- Resource id: 0x0 CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:13438): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:13438): 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: 0x252 X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 158 Minor opcode: 6 Resource id: 0x252 --------------------------------------------------
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 ***