GNOME Bugzilla – Bug 446214
crash in Tasks: I had just clicked to se...
Last modified: 2007-06-11 11:47:08 UTC
What were you doing when the application crashed? I had just clicked to send and receive 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: 160980992 vsize: 160980992 resident: 27111424 share: 18165760 rss: 27111424 rss_rlim: 4294967295 CPU usage: start_time: 1181533480 rtime: 127 utime: 108 stime: 19 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 -1208707360 (LWP 3194)] [New Thread -1289319536 (LWP 3237)] [New Thread -1278829680 (LWP 3236)] [New Thread -1228096624 (LWP 3206)] (no debugging symbols found) 0x009be402 in __kernel_vsyscall ()
+ Trace 139930
Thread 1 (Thread -1208707360 (LWP 3194))
----------- .xsession-errors --------------------- X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 160 Minor opcode: 6 Resource id: 0x1a5 X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 160 Minor opcode: 6 Resource id: 0x1a5 (evolution:3194): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0 (evolution:3194): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0 (evolution:3194): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0 X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 160 Minor opcode: 6 Resource id: 0x1a5 --------------------------------------------------
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 373699 ***