GNOME Bugzilla – Bug 426461
Exceptions from 'print' statements not caught
Last modified: 2008-02-10 12:56:54 UTC
What were you doing when the application crashed? I tried to enable 3d mode under the View menu, after I installed the necessary packages (python-gtkglext1, python-opengl etc). Then it crashed. I am using the open source ati drivers for my Radeon 7200 /r100; 3d works but this game crashes in 3d. Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.0 2007-03-13 (Ubuntu) BugBuddy Version: 2.18.0 System: Linux 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Human Icon Theme: Human 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 (127 sec old) --------------------- ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) /usr/lib/python2.5/site-packages/apt/__init__.py:18: FutureWarning: apt API not stable yet warnings.warn("apt API not stable yet", FutureWarning) /usr/lib/python2.5/site-packages/GDebi/GDebi.py:90: GtkWarning: gdk_window_set_cursor: assertion `GDK_IS_WINDOW (window)' failed self.window_main.set_sensitive(False) warnings.warn("apt API not stable yet", FutureWarning) /usr/lib/python2.5/site-packages/GDebi/GDebi.py:90: GtkWarning: gdk_window_set_cursor: assertion `GDK_IS_WINDOW (window)' failed self.window_main.set_sensitive(False) -------------------------------------------------- Traceback (most recent call last):
+ Trace 125126
self.__startGL()
print 'EXTENSIONS=' + OpenGL.GL.glGetString(OpenGL.GL.GL_EXTENSIONS)
*** Bug 431784 has been marked as a duplicate of this bug. ***
disgrunted.toaster, does this still occur for you? Frederick reported in Bug 431784 : <snip> I called glChess from the gimmie panel. That seems to be a bit unstable anyway, so maybe it was gimmie that caused the problem? The problem hasn't reoccured since then. </snip>
I've re-arranged the code in 2.18 so the bug will be clearer as to where the problem is.
*** Bug 457344 has been marked as a duplicate of this bug. ***
*** Bug 458765 has been marked as a duplicate of this bug. ***
*** Bug 464684 has been marked as a duplicate of this bug. ***
*** Bug 484725 has been marked as a duplicate of this bug. ***
*** Bug 488295 has been marked as a duplicate of this bug. ***
*** Bug 488662 has been marked as a duplicate of this bug. ***
This has nothing to do with the OpenGL.GL.glGetString... This is the print failing. The solution is to remove all print calls and replace with a print function that catches the exceptions. The bug reporters are running on systems where stdout is not present or closed for some reason.
Added an override in glchess.py to replace sys.stdout with a class that writes to stdout and catches and ignores all exceptions.
*** Bug 492182 has been marked as a duplicate of this bug. ***
*** Bug 502617 has been marked as a duplicate of this bug. ***
*** Bug 505063 has been marked as a duplicate of this bug. ***
*** Bug 508079 has been marked as a duplicate of this bug. ***
*** Bug 508080 has been marked as a duplicate of this bug. ***
*** Bug 509874 has been marked as a duplicate of this bug. ***
*** Bug 510077 has been marked as a duplicate of this bug. ***
*** Bug 510892 has been marked as a duplicate of this bug. ***
*** Bug 514213 has been marked as a duplicate of this bug. ***