GNOME Bugzilla – Bug 466888
crash in Tasks: browsing through my pers...
Last modified: 2008-04-10 13:20:51 UTC
Version: 2.10 What were you doing when the application crashed? browsing through my personal folders 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.20-2925.13.fc7xen #1 SMP Tue Jul 17 10:38:19 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 691417088 vsize: 691417088 resident: 87662592 share: 58028032 rss: 87662592 rss_rlim: 18446744073709551615 CPU usage: start_time: 1187167397 rtime: 1215 utime: 981 stime: 234 cutime:30 cstime: 22 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 46912496492688 (LWP 5019)] [New Thread 1094986064 (LWP 5085)] [New Thread 1084229968 (LWP 5083)] [New Thread 1094719824 (LWP 5071)] (no debugging symbols found) 0x00000039b220d97f in waitpid () from /lib64/libpthread.so.0
+ Trace 155345
Thread 1 (Thread 46912496492688 (LWP 5019))
----------- .xsession-errors --------------------- Major opcode: 157 Minor opcode: 6 Resource id: 0x64 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x1c07d53 X Error: BadPixmap (invalid Pixmap parameter) 4 Major opcode: 54 Minor opcode: 0 Resource id: 0x140185e X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 157 Minor opcode: 6 Resource id: 0x64 --------------------------------------------------
*** Bug 468330 has been marked as a duplicate of this bug. ***
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 447591 ***