Your message dated Tue, 06 May 2008 03:15:28 +0200
with message-id <[EMAIL PROTECTED]>
and subject line pymol and opengl
has caused the Debian Bug report #214026,
regarding pymol and opengl
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
214026: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=214026
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: pymol
Version: 0.90-1
Severity: normal
Hi,
On Fri, Oct 03, 2003 at 11:53:53AM +0200, Gabor E. Tusnady wrote:
> I would like to use pymol with python-opengl script. On my laptop I use
> pymol-0.86 width redhat 8.0. This package contains a lot of python
> example script, for example example/devel/gl01.py script. Running this
> script I have got a simple coordinate system displayed on the screen
> (the script is attached), while pymol reports:
>
> ----
> OpenGL based graphics front end:
> GL_VENDOR: Mesa project: www.mesa3d.org
> GL_RENDERER: Mesa GLX Indirect
> GL_VERSION: 1.3 Mesa 4.0.4
> Executive: object "gl01" created.
> ----
>
> Using the debianized version of pymol-0.90 with debian-sid on my
> workstation, I have got the following error message:
>
> ----
> OpenGL based graphics front end:
> GL_VENDOR: NVIDIA Corporation
> GL_RENDERER: GeForce2 MX/AGP/SSE
> GL_VERSION: 1.4.0 NVIDIA 44.96
> Adapting to GeForce hardware...
> Detected 2 CPUs. Enabled multithreaded rendering.
> Traceback (most recent call last):
> File "/usr/lib/python2.3/site-packages/pymol/parser.py", line 203, in parse
> execfile(args[nest][0],pymol_names,pymol_names)
> File "gl01.py", line 1, in ?
> from pymol.opengl.gl import *
> File "/usr/lib/python2.3/site-packages/pymol/opengl/gl/__init__.py", line
> 32,
> in ?
> import _opengl
> ImportError: /usr/lib/python2.3/site-packages/pymol/opengl/gl/_opengl.so:
> undefined symbol:
> glTexGeniv
> ----
>
> I don't know whether I have not installed something, or it is a bug in
> the debianized pymol-0.90, or this error come from the NVIDIA opengl
> driver.
> I'm really happy, if you can help me resolving this discrepancy.
>
> Gabor
>
> --
> Gabor E. Tusnady, PhD | e-mail: [EMAIL PROTECTED]
> Institute of Enzymology, BRC | www: http://www.enzim.hu/~tusi
> Hungarian Academy of Sciences | tel: (36-1) 279-3159
> H-1113 Budapest Karolina ut 29 | fax: (36-1) 466-5465
> *****************************************************************
> from pymol.opengl.gl import *
> from pymol.callback import Callback
> from pymol import cmd
>
> # this is a trivial example of creating a callback object which
> # makes OpenGL calls using the PyOpenGL bindings
>
> # define a callback object
>
> class myCallback(Callback):
>
> def __call__(self):
>
> glBegin(GL_LINES)
>
> glColor3f(1.0,1.0,1.0)
>
> glVertex3f(0.0,0.0,0.0)
> glVertex3f(1.0,0.0,0.0)
>
> glVertex3f(0.0,0.0,0.0)
> glVertex3f(0.0,2.0,0.0)
>
> glVertex3f(0.0,0.0,0.0)
> glVertex3f(0.0,0.0,3.0)
>
> glEnd()
>
> def get_extent(self):
> return [[0.0,0.0,0.0],[1.0,2.0,3.0]]
>
> # load it into PyMOL
>
> cmd.load_callback(myCallback(),'gl01')
>
Thanks for the report, I've confirmed this problem. Unfortunately, I
don't have much time right now, but I'll look at it as soon as possible.
In order to not forget, I've filed a bug for this issue in the Debian
Bug Tracking System. I'd like to encourage you to file bugs with the
'reportbug' utility in the future, at least I tend to forget about
mails, while I check the Bug pages regularly.
thanks,
Michael
--- End Message ---
--- Begin Message ---
The problem is not reproducible for me. The symbol is
in /usr/lib/libGL.so and pymol depends on the necessary libraries. It is
also possible, that the proprietary NVidia driver shipped some private
libGL.so (was it the proprietary driver?), that caused that problem.
nm -Dg /usr/lib/libGL.so | awk '$2 ~ /T/ { print $3; }' | grep glTexGeniv
should help here. However, the buildds (dpkg-shlibdeps) do not report
any symbol not being in the linked libraries. So I guess, this is not a
bug in pymol. So I'm closing the report.
Of course feel free to comment on this decision or reopen the report if
necessary.
(CCed the original reporter)
Regards, Daniel
--- End Message ---
