GNOME Bugzilla – Bug 495756
crash in Tasks: Readind emails
Last modified: 2008-02-24 14:32:16 UTC
What were you doing when the application crashed? Readind emails 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.20-2925.9.fc7xen #1 SMP Tue May 22 08:53:03 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 147902464 vsize: 147902464 resident: 49676288 share: 22134784 rss: 49676288 rss_rlim: 4294967295 CPU usage: start_time: 1194741853 rtime: 7239 utime: 6171 stime: 1068 cutime:7752 cstime: 651 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/i686/nosegneg/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208883488 (LWP 21898)] [New Thread -1271927920 (LWP 22168)] [New Thread -1249821808 (LWP 22167)] [New Thread -1282417776 (LWP 21910)] [New Thread -1261438064 (LWP 21908)] [New Thread -1212134512 (LWP 21904)] (no debugging symbols found) 0x00c69402 in __kernel_vsyscall ()
+ Trace 176916
Thread 1 (Thread -1208883488 (LWP 21898))
----------- .xsession-errors (22 sec old) --------------------- Major opcode: 156 Minor opcode: 6 Resource id: 0x1412b91 X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 156 Minor opcode: 6 Resource id: 0x5d X Error: BadPixmap (invalid Pixmap parameter) 4 Major opcode: 54 Minor opcode: 0 Resource id: 0x1412924 X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 156 Minor opcode: 6 Resource id: 0x1412924 --------------------------------------------------
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 444866 ***