GNOME Bugzilla – Bug 478379
crash in Window List: Ich habe die Arbeitsfläc...
Last modified: 2007-10-11 16:21:38 UTC
Version: 2.18.0 What were you doing when the application crashed? Ich habe die Arbeitsfläche 2 mal nach links und rechts bewegt so das der würfel sich dreht und dann wieder zurück Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 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: 35090432 vsize: 35090432 resident: 11878400 share: 9142272 rss: 11878400 rss_rlim: 4294967295 CPU usage: start_time: 1190227511 rtime: 173 utime: 154 stime: 19 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 -1208711456 (LWP 2852)] (no debugging symbols found) 0x0092b402 in __kernel_vsyscall ()
+ Trace 164004
Thread 1 (Thread -1208711456 (LWP 2852))
----------- .xsession-errors (173 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) compiz: Screen 0 on display ":0.0" already has a window manager; try using the --replace option to replace the current window manager. compiz: No manageable screens found on display :0.0 beryl: water: GL_ARB_fragment_program is missing --------------------------------------------------
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 ***