GNOME Bugzilla – Bug 451924
crash in Window Selector: spinning the cube
Last modified: 2007-06-28 15:55:16 UTC
Version: 2.18.2 What were you doing when the application crashed? spinning the cube Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 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: 37326848 vsize: 37326848 resident: 19255296 share: 15880192 rss: 19255296 rss_rlim: 4294967295 CPU usage: start_time: 1183042051 rtime: 706 utime: 636 stime: 70 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/libexec/wnck-applet' (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 -1208142112 (LWP 3347)] (no debugging symbols found) 0x00176402 in __kernel_vsyscall ()
+ Trace 144352
Thread 1 (Thread -1208142112 (LWP 3347))
----------- .xsession-errors (77 sec old) --------------------- Checking for XComposite extension : passed (v0.3) Checking for XDamage extension : passed Checking for RandR extension : passed Checking for XSync extension : passed Checking Screen 0 ... Checking for GLX_SGIX_fbconfig : passed Checking for GLX_EXT_texture_from_pixmap : passed Checking for non power of two texture support : passed Checking maximum texture size : passed (2048x2048) beryl: GLX_EXT_texture_from_pixmap is missing beryl: Using non-tfp mode beryl: No GLXFBConfig for default depth, falling back on visinfo. --------------------------------------------------
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 420713 ***