GNOME Bugzilla – Bug 503564
crash in Tasks:
Last modified: 2007-12-17 07:57:45 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: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 147415040 vsize: 147415040 resident: 39321600 share: 32010240 rss: 39321600 rss_rlim: 4294967295 CPU usage: start_time: 1197621676 rtime: 119 utime: 107 stime: 12 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 -1208297760 (LWP 2978)] [New Thread -1307972720 (LWP 3097)] [New Thread -1236272240 (LWP 3093)] [New Thread -1278624880 (LWP 3092)] [New Thread -1246762096 (LWP 3079)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 181850
Thread 1 (Thread -1208297760 (LWP 2978))
----------- .xsession-errors --------------------- to Fri Dec 14 00:00:00 2007 alarm-queue.c:522 (load_alarms) alarm-qu** (evolution:2978): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:2978): 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: 0x3f X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 157 Minor opcode: 6 Resource id: 0x3f --------------------------------------------------
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 ***