GNOME Bugzilla – Bug 495891
crash in Tasks: clicked on junk folder
Last modified: 2008-03-25 14:22:05 UTC
Version: 2.10 What were you doing when the application crashed? clicked on junk folder 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.23.1-21.fc7 #1 SMP Thu Nov 1 20:28:15 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 127107072 vsize: 127107072 resident: 48762880 share: 33382400 rss: 48762880 rss_rlim: 18446744073709551615 CPU usage: start_time: 1194790018 rtime: 1854 utime: 1683 stime: 171 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 "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 4160497376 (LWP 6108)] [New Thread 4116245392 (LWP 6524)] [New Thread 4066311056 (LWP 6523)] [New Thread 4126935952 (LWP 6130)] [New Thread 4094278544 (LWP 6118)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 177019
Thread 1 (Thread 4160497376 (LWP 6108))
----------- .xsession-errors --------------------- Resource id: 0x1c08a32 X Error: BadPixmap (invalid Pixmap parameter) 4 Major opcode: 54 Minor opcode: 0 Resource id: 0x1400eb1 X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 158 Minor opcode: 6 Resource id: 0x1400eb1 X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 158 Minor opcode: 6 Resource id: 0x45 warning: Lowest section in system-supplied DSO at 0xffffe000 is .hash at ffffe0b4 --------------------------------------------------
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 ***