GNOME Bugzilla – Bug 503238
GLUError class called GLUerror on Gentoo
Last modified: 2008-07-27 22:33:32 UTC
Version: 2.20.2 What were you doing when the application crashed? Distribution: Gentoo Base System release 1.12.10 Gnome Release: 2.20.2 2007-12-11 (Gentoo) BugBuddy Version: 2.20.1 System: Linux 2.6.22-kamikaze9 #1 SMP Fri Sep 14 19:18:03 CEST 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10400000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0 CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 ----------- .xsession-errors (4483 sec old) --------------------- (evolution:4267): Gdk-CRITICAL **: gdk_window_get_origin: assertion `GDK_IS_WINDOW (window)' failed (evolution:4267): Gdk-CRITICAL **: gdk_window_get_origin: assertion `GDK_IS_WINDOW (window)' failed (evolution:4267): Gdk-CRITICAL **: gdk_window_get_origin: assertion `GDK_IS_WINDOW (window)' failed (evolution:4267): Gdk-CRITICAL **: gdk_window_get_origin: assertion `GDK_IS_WINDOW (window)' failed (evolution:4267): Gdk-CRITICAL **: gdk_window_get_origin: assertion `GDK_IS_WINDOW (window)' failed (evolution:4267): Gdk-CRITICAL **: gdk_window_get_origin: assertion `GDK_IS_WINDOW (window)' failed (evolution:4267): Gdk-CRITICAL **: gdk_window_get_origin: assertion `GDK_IS_WINDOW (window)' failed ...Too much output, ignoring rest... -------------------------------------------------- Traceback (most recent call last):
+ Trace 181649
self.view.feedback.renderGL()
self.scene.controller.render()
self.drawBoard()
self.whiteTexture.bind() #blackTexture
self.__texture = self.__generate()
except GLUError, e:
*** Bug 503478 has been marked as a duplicate of this bug. ***
*** Bug 503904 has been marked as a duplicate of this bug. ***
This only seems to affect Gentoo systems: Can you please try the following: $ python >>> import OpenGL.GLU >>> OpenGL.GLU.GLUError $ python >>> from OpenGL.GLU import * >>> GLUError (The above work for me in Ubuntu Gutsy).
*** Bug 507094 has been marked as a duplicate of this bug. ***
*** Bug 511704 has been marked as a duplicate of this bug. ***
*** Bug 513794 has been marked as a duplicate of this bug. ***
*** Bug 515893 has been marked as a duplicate of this bug. ***
*** Bug 518204 has been marked as a duplicate of this bug. ***
*** Bug 518130 has been marked as a duplicate of this bug. ***
*** Bug 518319 has been marked as a duplicate of this bug. ***
*** Bug 518320 has been marked as a duplicate of this bug. ***
*** Bug 518321 has been marked as a duplicate of this bug. ***
*** Bug 519117 has been marked as a duplicate of this bug. ***
I've asked upstream if it should be "GLUError" (on Ubuntu) or "GLUerror" (on Gentoo?): http://sourceforge.net/mailarchive/forum.php?thread_name=9a0b92c0802262155o284cdd5cg3fca87d6fcc5ffe6%40mail.gmail.com&forum_name=pyopengl-users
*** Bug 522013 has been marked as a duplicate of this bug. ***
I think they have change the name of the class from "GLUerror" in 2.0.x.xx to "GLUError" in 3.0.x (which is still beta). On Mandriva, which has PyOpenGL version 2.0.1.09, this bug is also happening.
*** Bug 522641 has been marked as a duplicate of this bug. ***
For info, I've renamed GLUError to GLUerror in glchess/scene/opengl/new_models.py. It fixes this particular problem, in particular glChess doesn't crash anymore. Now, this is opening a little Pandora's box: glChess will really display the opengl error. Every duplicate of this bug might come up as actually a different bug!
*** Bug 523845 has been marked as a duplicate of this bug. ***
Created attachment 107907 [details] [review] Handles error objects in pyopengl 2.0 and 3.0
Thanks Eric for confirming this one. I've patched 2.22.1 and the 2.23 head to support both names of the variables. I think you're right that this is only going to fix the initial problem - we still need to find out why this expcetion is occuring in Gentoo/PyOpenGL3.0. The best I can find on what the changes are from documentation/using.html in the PyOpenGL 3.0 release: """ # different error types * In a number of locations PyOpenGL 3.x will raise a different error type than PyOpenGL 2.x [XXX document which cases, at minimum every ctypes-level error is new (and should be eliminated, likely)] """
*** Bug 525222 has been marked as a duplicate of this bug. ***
*** Bug 527009 has been marked as a duplicate of this bug. ***
*** Bug 527647 has been marked as a duplicate of this bug. ***
*** Bug 528854 has been marked as a duplicate of this bug. ***
*** Bug 536770 has been marked as a duplicate of this bug. ***
*** Bug 537748 has been marked as a duplicate of this bug. ***
*** Bug 541940 has been marked as a duplicate of this bug. ***
*** Bug 544617 has been marked as a duplicate of this bug. ***