GNOME Bugzilla – Bug 490897
crash in Tasks: Distribution: Fedora rel...
Last modified: 2007-10-28 17:21:09 UTC
What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 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: 129794048 vsize: 129794048 resident: 23625728 share: 16875520 rss: 23625728 rss_rlim: 4294967295 CPU usage: start_time: 1193516492 rtime: 87 utime: 73 stime: 14 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 -1208674592 (LWP 3872)] [New Thread -1277265008 (LWP 3909)] [New Thread -1226818672 (LWP 3884)] (no debugging symbols found) 0x00354402 in __kernel_vsyscall ()
+ Trace 173305
Thread 1 (Thread -1208674592 (LWP 3872))
----------- .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: 158 Minor opcode: 6 Resource id: 0x4d X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 158 Minor opcode: 6 Resource id: 0x4d (evolution:3872): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0 (evolution:3872): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0 X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 158 Minor opcode: 6 Resource id: 0x4d --------------------------------------------------
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 ***