GNOME Bugzilla – Bug 517864
crash in Tasks:
Last modified: 2008-02-21 16:37:10 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: 138129408 vsize: 138129408 resident: 54071296 share: 41340928 rss: 54071296 rss_rlim: 4294967295 CPU usage: start_time: 1203600170 rtime: 482 utime: 421 stime: 61 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 -1208895776 (LWP 3107)] [New Thread -1290626160 (LWP 3227)] [New Thread -1237320816 (LWP 3112)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 189981
Thread 1 (Thread -1208895776 (LWP 3107))
----------- .xsession-errors --------------------- ** (evolution:3107): 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 (evolution:3107): evolution-mail-WARNING **: Failed to refresh folders: No such folder Pastas_Publicas (evolution:3107): evolution-mail-WARNING **: Failed to refresh folders: No such folder Pastas_Publicas 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 ***