GNOME Bugzilla – Bug 512496
crash in Tasks:
Last modified: 2008-01-29 18:22:14 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: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 167669760 vsize: 167669760 resident: 53534720 share: 34877440 rss: 53534720 rss_rlim: 4294967295 CPU usage: start_time: 1201498138 rtime: 476 utime: 417 stime: 59 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 -1208281376 (LWP 2397)] [New Thread -1258300528 (LWP 2446)] [New Thread -1237320816 (LWP 2437)] [New Thread -1224995952 (LWP 2434)] [New Thread -1247810672 (LWP 2403)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 187017
Thread 1 (Thread -1208281376 (LWP 2397))
----------- .xsession-errors --------------------- Major opcode: 158 Minor opcode: 6 Resource id: 0x50 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x2640180 X Error: BadPixmap (invalid Pixmap parameter) 4 Major opcode: 54 Minor opcode: 0 Resource id: 0x1402ff9 X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 158 Minor opcode: 6 Resource id: 0x50 --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
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 ***