GNOME Bugzilla – Bug 469299
crash in Tasks: I was reading a new mail...
Last modified: 2007-08-23 07:17:55 UTC
Version: 2.10 What were you doing when the application crashed? I was reading a new mail. When it shifted to the next mail, i closed my mail window. 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.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 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: 155799552 vsize: 155799552 resident: 57077760 share: 45408256 rss: 57077760 rss_rlim: 4294967295 CPU usage: start_time: 1187783889 rtime: 12367 utime: 11431 stime: 936 cutime:25 cstime: 48 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 -1209120016 (LWP 3295)] [New Thread -1255814256 (LWP 6878)] [New Thread -1304634480 (LWP 3424)] [New Thread -1237320816 (LWP 3383)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 157161
Thread 1 (Thread -1209120016 (LWP 3295))
----------- .xsession-errors --------------------- Resource id: 0x140567a X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 157 Minor opcode: 6 Resource id: 0x45 warning: .dynamic section for "/lib/libasound.so.2" is not at the expected address (wrong library or version mismatch?) X Error: BadPixmap (invalid Pixmap parameter) 4 Major opcode: 54 Minor opcode: 0 Resource id: 0x1405717 X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 157 Minor opcode: 6 Resource id: 0x1405717 --------------------------------------------------
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 426496 ***