GNOME Bugzilla – Bug 500799
crash in Tasks:
Last modified: 2007-12-04 04:23:11 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.23.1 #1 SMP Sun Oct 14 16:04:23 IST 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Enabled GTK+ Theme: Bluecurve Icon Theme: Bluecurve Memory status: size: 500641792 vsize: 500641792 resident: 42708992 share: 33280000 rss: 42708992 rss_rlim: 18446744073709551615 CPU usage: start_time: 1196482038 rtime: 63 utime: 53 stime: 10 cutime:1 cstime: 4 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 47777929254256 (LWP 3892)] [New Thread 1098918224 (LWP 3916)] [New Thread 1082132816 (LWP 3913)] (no debugging symbols found) 0x000000358b80d97f in waitpid () from /lib64/libpthread.so.0
+ Trace 180283
Thread 1 (Thread 47777929254256 (LWP 3892))
----------- .xsession-errors --------------------- (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: 159 Minor opcode: 6 Resource id: 0x1a5 Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 159 Minor opcode: 6 Resource id: 0x1a5 warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fff803fd000 --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 431342 ***