GNOME Bugzilla – Bug 486503
crash in Tasks:
Last modified: 2007-10-14 13:15:37 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: 136036352 vsize: 136036352 resident: 42160128 share: 33316864 rss: 42160128 rss_rlim: 4294967295 CPU usage: start_time: 1192348124 rtime: 135 utime: 122 stime: 13 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 -1209051424 (LWP 3392)] [New Thread -1291846768 (LWP 3663)] [New Thread -1228088432 (LWP 3661)] [New Thread -1261442160 (LWP 3442)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 170094
Thread 1 (Thread -1209051424 (LWP 3392))
----------- .xsession-errors --------------------- Xlib: extension "SHAPE" missing on display ":0.0". X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 143 Minor opcode: 6 Resource id: 0x164 Xlib: extension "DPMS" missing on display ":0.0". Xlib: extension "MIT-SCREEN-SAVER" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 143 Minor opcode: 6 Resource id: 0x164 Xlib: extension "SHAPE" missing on display ":0.0". --------------------------------------------------
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 364700 ***