GNOME Bugzilla – Bug 490513
crash in Tasks:
Last modified: 2007-10-26 14:48:25 UTC
Version: 2.10 What were you doing when the application crashed? 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: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 181534720 vsize: 181534720 resident: 45883392 share: 34148352 rss: 45883392 rss_rlim: 4294967295 CPU usage: start_time: 1193405103 rtime: 147 utime: 134 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 -1208613152 (LWP 2273)] [New Thread -1305764976 (LWP 2316)] [New Thread -1247810672 (LWP 2304)] [New Thread -1237320816 (LWP 2302)] [New Thread -1225327728 (LWP 2301)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 173028
Thread 1 (Thread -1208613152 (LWP 2273))
----------- .xsession-errors --------------------- CalDAV Eplugin starting up ... CalDAV Eplugin starting up ... CalDAV Eplugin starting up ... ** (evolution:2273): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:2273): 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: 0x50 X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 158 Minor opcode: 6 Resource id: 0x50 --------------------------------------------------
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 431459 ***