GNOME Bugzilla – Bug 495197
crash in Tasks:
Last modified: 2007-11-11 12:09:06 UTC
Version: 2.10 What were you doing when the application crashed? Distribution: Fedora release 8 (Werewolf) 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 21:09:24 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: 145604608 vsize: 145604608 resident: 44331008 share: 34721792 rss: 44331008 rss_rlim: 4294967295 CPU usage: start_time: 1194585536 rtime: 244 utime: 212 stime: 32 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 -1208199456 (LWP 13310)] [New Thread -1275475056 (LWP 13344)] [New Thread -1243612272 (LWP 13324)] [New Thread -1254102128 (LWP 13323)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 176493
Thread 1 (Thread -1208199456 (LWP 13310))
----------- .xsession-errors (72243 sec old) --------------------- Resource id: 0x320000c A: 0.7 V: 0.0 A-V: 0.652 ct: 0.004 2/ 2 ??% ??% ??,?% 1 0 A: 0.7 V: 0.1 A-V: 0.649 ct: 0.008 3/ 3 ??% ??% ??,?% 2 0 A: 0.7 V: 0.1 A-V: 0.615 ct: 0.0 Major opcode: 54 Minor opcode: 0 Resource id: 0x1434895 X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 158 Minor opcode: 6 Resource id: 0x1434895 A: 1.6 V: 1.6 A-V: 0.001 ct: 0.053 41/ 41 79% 5% 2.2% 14 0 A: 1.6 V: 1.6 A-V: 0.001 ct: 0.054 42/ 42 77% 5% 2.2% 14 0 A: 1.7 V: 1.7 A-V: 0.001 ct: 0.0 Major opcode: 19 Minor opcode: 0 Resource id: 0x3200029 A: 2.1 V: 2.1 A-V: 0.000 ct: 0.054 54/ 54 60% 4% 2.1% 14 0 A: 2.2 V: 2.2 A-V: 0.001 ct: 0.054 55/ 55 59% 5% 2.2% 14 0 A: 2.2 V: 2.2 A-V: -0.000 ct: 0.0 ...Too much output, ignoring rest... --------------------------------------------------
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 ***