Problems launching shaderman.next on 64bit

[animux.org (mark)]

Hi,

We have been trying to port WhiteRabbit's entire Blender to Renderman
pipeline to Animux (an animator distribution of linux). In that
effort we have been compiling all the required packages. We have been
following his work for quite sometime now! :-)

I get the following error when I launch shaderman.next.
animux@Five00:~$ shaderman-next
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 403 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.)
Locking assertion failure. Backtrace:
#0 /usr/lib/libxcb-xlib.so.0 [0x2aae1c67197c]
#1 /usr/lib/libxcb-xlib.so.0(xcb_xlib_lock+0x15) [0x2aae1c671a15]
#2 /usr/lib/libX11.so.6 [0x2aae1a4cd420]
#3 /usr/lib/libGL.so.1 [0x2aae1e3f95c6]

When I start shaderman-next --sync it does bring up the the UI where
all I can do is pick the menu options. When I pick anything in the
"mode" menu or even about, it just hangs.

animux@Five00:~$ shaderman-next --sync
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 108214 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.)
Locking assertion failure. Backtrace:
#0 /usr/lib/libxcb-xlib.so.0 [0x2b6fdd07d97c]
#1 /usr/lib/libxcb-xlib.so.0(xcb_xlib_lock+0x15) [0x2b6fdd07da15]
#2 /usr/lib/libX11.so.6 [0x2b6fdaed9420]
#3 /usr/lib/libGL.so.1 [0x2b6fdee055c6]

Can you please help us by guiding us?

Thank You,
Mark
(www.animux.org)

[animate1978]

I would assume that you have both wxPython 2.6 and PyOpenGL?

I had errors of my own using Shaderman.next with wxPython 2.4 but from
what I see it's more of an OpenGL problem, and an X problem. I have no
idea unless I see a list of your OpenGL and X11 packages, there is a
conflict there. That is all I can say for now.

Ted

[Alexei Puzikov]

Indeed, it's a OpenGL misconfiguration and/or missing OpenGL 1.2/2.0 drivers.

ShaderMan.Next requires Non-power-of-two textures support.

A.

[animux.org (mark)]

Hi Alexei,

We will check to see if we have the proper packages installed. I will
also post the packages OpenGL & X11 packages. On the test machine, we
are currently using the NVIDIA drivers which support OpenGL.

Here is the strace output : http://www.pasteall.org/5910
OpenGL Settings: http://www.pasteall.org/5913
Xorg.conf : http://www.pasteall.org/5914
List of all animux pacakges: http://www.pasteall.org/5915

Thank you for your help.

Mark

On Jun 3, 9:48 pm, Alexei Puzikov <puzi...@gmail.com> wrote:
> Indeed, it's a OpenGL misconfiguration and/or missing OpenGL 1.2/2.0 drivers.
>
> ShaderMan.Next requires Non-power-of-two textures support.
>
> A.
>

[animux.org (mark)]

Hi Alexei, Ted,
Here is the list of pacakges with version numbers in animux
http://www.pasteall.org/5920
Mark

[animux.org (mark)]

Hi Alexei,

Found a work around...
$export XLIB_SKIP_ARGB_VISUALS=1;
$shaderman-next

Brings up the shaderman-next .

Do you think this is good enough?

Mark

[Alexei Puzikov]

Ah. So you're using Composite-enabled desktop, and my application (or
WxPython, whatever) tried to use it only to crash immediately.

And this patch will disable it.

Good idea.

Thanks. I'll probably need to make a shaderman.sh file or something :)

A.

[animux.org (mark)]

Hi Alexei,
The strange thing is I disabled it using the windows manager, but it
still kept failing. We use XFCE for our desktop with composite turned
on by default. Ted is testing it out for us. He is awesome!.
Mark.

On Jun 8, 9:24 pm, Alexei Puzikov <puzi...@gmail.com> wrote:
> Ah. So you're using Composite-enabled desktop, and my application (or
> WxPython, whatever) tried to use it only to crash immediately.
>
> And this patch will disable it.
>
> Good idea.
>
> Thanks. I'll probably need to make a shaderman.sh file or something :)
>
> A.
>