GNOME Bugzilla – Bug 479607
crash in Tasks: Just started evolution, ...
Last modified: 2007-09-24 17:31:01 UTC
Version: 2.10 What were you doing when the application crashed? Just started evolution, 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.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 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: 132661248 vsize: 132661248 resident: 38834176 share: 32284672 rss: 38834176 rss_rlim: 4294967295 CPU usage: start_time: 1190574443 rtime: 75 utime: 62 stime: 13 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 10255)] [New Thread -1271936112 (LWP 10263)] [New Thread -1240466544 (LWP 10259)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 164908
Thread 1 (Thread -1208944928 (LWP 10255))
----------- .xsession-errors --------------------- evolution-alarm-notify-Message: Mon Sep 24 00:00:00 2007 CalDAV Eplugin starting up ... ** (evolution:10255): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:10255): 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 ***