Errors out in RPM version of Animux at glColor4f function call.

[animux.org (mark)]

I have figured out how to run the debugger on shaderman.next trying to
figure out what needs to happen to fix the issues....
1. Edit /usr/local/bin/shaderman
pyhon prototype.py to python -m pdb prototype.py
2. Run the program /usr/local/bin/shaderman and it will run in debug
mode
3. Set a breakpoint at 755 using b 755
4. Problem line is 757.
> /usr/local/shaderman/prototype.py(757)OnDraw()
-> glColor4f(0.4, 0.4, 0.4, 0.4) # current view
(Pdb) s

Here is the error we see...

> /usr/local/shaderman/prototype.py(757)OnDraw()
-> glColor4f(0.4, 0.4, 0.4, 0.4) # current view
(Pdb) s

Gdk-ERROR **: The program 'python' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
(Details: serial 1111 error_code 8 request_code 73 minor_code 0)
(Note to programmers: normally, X errors are reported
asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error()
function.)
aborting...
/usr/local/bin/shaderman: line 3: 2880 Aborted python
-m pdb prototype.py

It failed when I tried to
export XLIB_SKIP_ARGB_VISUALS=1;
as we found out it works.
http://groups.google.com/group/shaderman/browse_thread/thread/bdc9a5ef6f730235

We will look through the forum notes if we are missing any libaries.
http://groups.google.com/group/shaderman/browse_thread/thread/c43c4244655a5bbb

If you can find out what is the missing library based on our error
with the function call glColor4f, I would appreciate it.

Mark

[animux.org (mark)]

Here are some of the packages
[animux@localhost ~]$ rpm -qa |grep wx
wxBase-2.8.11-1.fc12.x86_64
wxsvg-1.0.4-1.fc12.x86_64
wxGTK-gl-2.8.11-1.fc12.x86_64
wxGTK-media-2.8.11-1.fc12.x86_64
wxPython-2.8.11.0-1.fc12.x86_64
wxGTK-2.8.11-1.fc12.x86_64
PyOpenGL-3.0.0-2.fc12.noarch
freeglut-2.6.0-1.fc12.x86_64

[Alexei Puzikov]

Mark,

Most probably it's an incompatibility between PyOpenGL and wxGTK-gl.
Does any of the examples from PyOpenGL work? Specifically textured
ones?

O.

> --
> You received this message because you are subscribed to the Google Groups "shaderman" group.
> To post to this group, send email to shad...@googlegroups.com.
> To unsubscribe from this group, send email to shaderman+...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/shaderman?hl=en.
>
>

[animux.org (mark)]

Hi Alex,

Can you let us know how to run the --sync command?

We are currently trying to use print statements trying to figure out
which portion of the call is failing as the program is run
asynchronously, we do not know when it is actually failing?

Mark

[Alexei Puzikov]

Mark,

If inside the onDraw you'll comment everything down from line

# small preview of bricks

down to the end of the method - will it work?

Alexei

[Alexei Puzikov]

Oh, make sure

self.SwapBuffers()

is not commented, sorry.

A.

[animux.org (mark)]

tester@Desktop shaderman]$ shaderman

Gdk-ERROR **: The program 'python' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.

(Details: serial 841 error_code 8 request_code 70 minor_code 0)

(Note to programmers: normally, X errors are reported
asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error()
function.)
aborting...

/usr/local/bin/shaderman: line 3: 5574 Aborted python
prototype.py

I commented out lines 740 to 774 from small bricks to
self.SwapBuffers(). I still get the above error.

Mark

On Aug 28, 7:37 pm, Alexei Puzikov <puzi...@gmail.com> wrote:
> Oh, make sure
>
> self.SwapBuffers()
>
> is not commented, sorry.
>
> A.
>

[Alexei Puzikov]

Mark,

1st - what's your video card? Drivers?
2nd - well, the best and quickest solution would be to continue
commenting lines in the same method until you'll get it working. I
suspect the lines that causes this would be ones painting actual
bricks, but let's see.

A.